New answers tagged

0

zfs writes aren't really fast but not bad. zfs reads are extremely slow take a look by your own: 1) #Preparation: cd /mytestpool/mytestzfs;for f in urf{0..9};do dd if=/dev/urandom of=$f bs=1M count=102400;done; #Get a directory path with lots of subdirs and files (of ~50GB) and check size with eg: du -sh /mytestpool/mytestzfs/appsdir 2) reboot 3) time cat /...


1

Yes, this is possible and often used approach. It is best to take the images with dd utility, so that full hard disk contents are in the image. After you have the images, for example diskN.img, we'll use the losetup to create loop device for each disk image, which makes the image appear as a device on the system. losetup /dev/loop0 disk1.img losetup /dev/...


0

You know you're in a good Job when there aren't many Stack Exchange Solutions for what you're attempting to accomplish. All of the preseeding files I've seen simply work with Disk Drives because technology was pervasively Spinning Disks and not SSD. Aye-Aye-Aye Zordon! How do we do this?!


0

I'm the OP. My key questions were: considering all of the above: Is it safe to assume that these are symptoms of the RAID controller itself dying? It's neither the physical HDDs nor any other system components causing the problems? Yo get the current problems solved: Would the best option be to get the current RAID controller replaced with an identical one?...


0

This probably is an artifact on how DELL introduced, and removed, eHBA mode. In short, it is a "lightweight" RAID mode (with no support for parity arrays), useful when dealing with fast SSDs which can be slowed down from "full" RAID processing. It also supports disk pass-through for non-RAID setup. From DELL 10th gen PERC controller: In ...


0

My bet would be - seen the same on other controllers: Numbers: Start physical real discs at the bottom, then the virtual non-physical discs at the highest ID. Why? Because this way you can have more physical discs added (like when adding another cabinet). Remember, especially when using NAS, you can always route a cable to a JBOD cabinet and you want to have ...


1

Since RAID 6 stripes data over multiple devices, this looks like one of the devices is missing from the array, and the RAID controller doesn't realize it is missing a device. This means every continuous stream of data has missing data in it. Running chkdsk can only make things worse, since the issues are below the actual filesystem. You would somehow need to ...


10

Your guess is only partially right: MDRAID does not store a backup superblock on the same disk, but the superblock on the other disks describe the same array geometry, effectively serving as a backup in the case a disk fails. You can examine each disk superblock via mdadm -E /dev/your_disk, while an array-wide description can be dumped via mdadm -D /dev/...


2

Unfortunatly, Intel drops RST support for Windows Server 2019. The driver you have downloaded is only for 2016. Look closer https://www.intel.com/content/www/us/en/download/15667/intel-rapid-storage-technology-intel-rst-user-interface-and-driver.html Windows 10, 64-bit*, Windows Server 2016 family* Size: 3.7 MB SHA1: EF7FAE2C67B5586F951E33C97B2B37D0AC75D485


1

Since you are using lvm you have to do multiple steps: Resize lvm-disk with pvresize /dev/md1 If you want to resize /tmp too, then lvextend -L +1G /dev/mapper/vg0-tmp If you dont want to keep some space for future extensions of /tmp or new volumes, assign the rest to root-volume with lvextend -l +100%FREE /dev/mapper/vg0-root Resize filesystem(s) resize2fs /...


0

Just a bit of info, adding to the confusion: If You are planning to deploy S2D - now or some time in the future - You can NOT, I repeat NOT use consumer SSD´s! MS decided (wise enough), that S2D should always ensure, that every bit is written correctly AND SECURELY, before the next is sent. So S2D will only use any on disk cache, if it is fully protected ...


Top 50 recent answers are included