Summary: | Install error "No free space left on device." on Dell T610 w/H700 RAID 10 with 11.1TB | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Base System | Reporter: | rallenh | ||||||
Component: | kern | Assignee: | freebsd-bugs (Nobody) <bugs> | ||||||
Status: | New --- | ||||||||
Severity: | Affects Some People | CC: | vvd | ||||||
Priority: | --- | ||||||||
Version: | 12.2-STABLE | ||||||||
Hardware: | amd64 | ||||||||
OS: | Any | ||||||||
Attachments: |
|
Description
rallenh
2021-02-23 07:06:20 UTC
Created attachment 222747 [details]
6 x 2.8TB RAID 10 (8.3TB) EFI serial console boot log
Created attachment 222748 [details]
8 x 2.8TB RAID 10 (11.1TB) EFI serial console boot log
Can you try install with EFI boot mode off? I have the same outcome: Failed to load kernel 'kernel' when I use all 8 spindles (11.1TB). BIOS boot configuration worked fine with 6 x 2.8TB RAID 10 (8.3TB, two hot spares). The only hardware "configuration" I changed was going from 6 x 2.8TB RAID 10 to 8 x 2.8TB RAID 10 (and re-init) and then re-install and re-boot. I did this for both BIOS boot configuration and UEFI boot configuration with the same results. I have left it in UEFI mode because I now have a USB flash drive loaded with FreeBSD to rescue the box if it doesn't reboot on me. The flash is plugged into an internal connector. It's easier to boot from this in UEFI mode vs BIOS mode and I get a serial console, I just have to hit F11 and choose the flash drive. I originally thought this was an EFI issue and I had created a ticket with that working assumption, it's here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249045. I was using an 8 x 2.8TB RAID 6 (16TB) configuration then. I didn't really experiment with RAID configurations with the premise that the size of the RAID was the issue. The reason why I now don't think this EFI related, it does the same thing in BIOS boot mode and I get an error _during_ install with 12.2-STABLE (r369250). In the previous ticket, I used 12.1-RELEASE and I didn't get any errors during install. As workaround: try to install system and boot from other disk. It's "best practice" to use for system small disks in RAID1 and big RAID for data only. And why not ZFS stripe of 4 mirrors (pass-through or JBOD mode HDDs)? I have a workaround now: 6 (instead of 8) spindles in RAID 10 with two hot spares for 8.3TB. Use "best practices" vs taking the defaults from the FreeBSD Installer? Isn't that a best practice of sorts? It seems "Auto (UFS) Guided Disk Setup" doesn't work in all use cases? There are SATA drives bigger than 11.1TB these days. This isn't a big RAID setup. I am not a fan of ZFS. I'll pass, thank you. AFAIK, the controller I am using doesn't support JBOD, pass-through or a reflash to IT firmware. There are other Dell controllers that do support those features, the H700/H800 do not. The error I get from bsdinstall (calling autopart) is here: https://github.com/freebsd/freebsd-src/blob/master/usr.sbin/bsdinstall/partedit/gpart_ops.c#L1064 It looks like geom is valid (there's a few guards) but the pointer to &firstfree could be the issue? Or something in gpart_max_free()? This commit seems sensible and maybe this is somewhere for me to start looking? https://github.com/freebsd/freebsd-src/commit/4af559e39b295c6950e25663f638d1737808a205 I wonder if the H700 is doing some funny business with sector sizes when the volume is over a specific size? Btw, I would say that there's a bug in bsdinstall here: https://github.com/freebsd/freebsd-src/blob/de1aa3dab23c06fec962a14da3e7b4755c5880cf/usr.sbin/bsdinstall/scripts/auto#L328 bsdinstall autopart || error "Partitioning error" is failing in my case. Perhaps the error isn't making it back to the parent shell? I should be getting the error "Partitioning error" but I am not. I am getting the error from partedit/autopart. |