Under the hood, the DL4100 is mostly Linux and the MD multiple-disk software raid driver.
They’ve done some strange things on top of it and there’s partitions with extra XML files that have proprietary volume descriptions and stuff.
Having said that, I’m not sure whether what I’m about to try will work or not.
I started with 4 drives in a RAID10 configuration. (3.96 TB usable space). The operating system appears to occupy a 2G partition on each drive in a RAID-1 configuration.
I’m waiting for the third rebuild (of 4) to complete now on the 6TB drives I’m installing. One more to go after this rebuild completes.
I’ve verified that the following are true:
- The filesystem is an ext4 filesystem.
- the resize2fs command is present on the system
I haven’t yet found a way to modify the partition tables in the box. However, it appears they are standard partition labels. There appears to be an internal USB storage device (/dev/sde) which appears to contain the images for installing the OS onto the hard disks when they are installed and also stores backup copies of the personality files for the device (IP addresses, settings, etc.)
It appears to use EFI booting based on the contents of /dev/sde1.
It does not appear to use grub or lilo or any boot loader I could recognize. I’m guessing they built some sort of custom EFI loader that loads the kernel directly.
So my plan is to continue searching for a way to alter the partition tables in the box via the shell. If I can’t find one, I’ll resort to shutting down the box and repartitioning the drives on an external linux system and then reinstalling them.
Once the drives have the expanded partitions, it should be possible to use mdadm in --grow mode to expand the raid10 array to fill the enlarged partitions and then use resize2fs to grow the filesystem to fill the expanded raid10 array.
The open question is whether that will allow cause problems with the proprietary XML files not getting updated, etc.