May 30May 30 Went through onboarding wizard. Chose 2 drives, rebooted, failed to boot. So I disabled secure boot and it booted past grub. Now its in a boot loop with the last log message, waiting for boot drive to come online.
May 31May 31 Community Expert What controller are the HDDs connected to? Not all are supported for internal boot.
May 31May 31 Author 6 hours ago, JorgeB said:What controller are the HDDs connected to? Not all are supported for internal boot.LSI MegaRAID SAS 2008
June 1Jun 1 Community Expert 18 hours ago, jmztaylor said:LSI MegaRAID SAS 2008That one is currently not supported; LSI in IT mode is (MPT2SAS driver)
June 13Jun 13 Author On the same topic. Another unraid server I have I needed to reconfigure and reinstall. I have to booting from the ssd without usb just fine. But I can't assign shares to the device. Shares tab says no array or pool devices.The docs say It lets you choose a dedicated boot pool for boot-only devices, or a boot + data pool when you want to reserve part of a larger device for boot and use the remaining capacity as a normal pool.https://docs.unraid.net/unraid-os/getting-started/set-up-unraid/internal-boot-faq/#internal-boot-benefits
June 13Jun 13 Community Expert Did you select the boot + data option in the wizard? If you did you end up with a small boot partition at the start and a larger data partition covering the remainder. You then format the data partition to get it ready to receive data.Post the system’s diagnostics.zip file for more informed feedback.
June 13Jun 13 Author 1 hour ago, itimpi said:Did you select the boot + data option in the wizard? If you did you end up with a small boot partition at the start and a larger data partition covering the remainder. You then format the data partition to get it ready to receive data.Post the system’s diagnostics.zip file for more informed feedback.Attached. According to fdisk it has 4 partitions on it. tower-diagnostics-20260613-1421.zip
June 13Jun 13 Community Expert Looking at the diagnostics it seems you specified the whole drive was to be used for boot purposes. I think that means you need to wipe the drive and start over again setting it up for boot purposes making sure you select the boot+data option in the wizard.
June 13Jun 13 Author Just now, itimpi said:Looking at the diagnostics it seems you specified the whole drive was to be used for boot purposes. I think that means you need to wipe the drive and start over again setting it up for boot purposes making sure you select the boot+data option in the wizard.Yeah thats the thing. I know without a doubt I chose that boot+data option. I will wipe and try it again.
June 13Jun 13 Community Expert 1 hour ago, jmztaylor said:Yeah thats the thing. I know without a doubt I chose that boot+data option. I will wipe and try it again.It was also strange that you said there were 4 partitions on the disk - I wold have thought there should only be 1 or 2 depending on the option chosen. Was it by any chance used somewhere else previously and you did not erase all partitions on the drive before using it in Unraid?
June 13Jun 13 Author 1 hour ago, itimpi said:It was also strange that you said there were 4 partitions on the disk - I wold have thought there should only be 1 or 2 depending on the option chosen. Was it by any chance used somewhere else previously and you did not erase all partitions on the drive before using it in Unraid?Well I made sure to choose the right option and it seemed to have worked. Somehow there was a cache pool created and it wouldn't let me remove it. So I deleted the pool.cfg and rebooted. Was able to get back up after a weird license issue also.
June 15Jun 15 Community Expert On 6/13/2026 at 5:38 PM, itimpi said:It was also strange that you said there were 4 partitions on the disk - I wold have thought there should only be 1 or 2 depending on the option chosen. Was it by any chance used somewhere else previously and you did not erase all partitions on the drive before using it in Unraid?4 partitions would be correct for a disk formatted for internal boot. Partitions 3 and 4 are the boot partition and data partition respectively. Partition 1 is the EFI which is separate from the boot partition. I cant remember what the 2nd partition is but it's small.My boot disk:NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS nvme0n1 259:0 0 13.4G 0 disk ├─nvme0n1p1 259:2 0 1M 0 part (Legacy/BIOS) ├─nvme0n1p2 259:3 0 510M 0 part (EFI) ├─nvme0n1p3 259:4 0 12.9G 0 part (BOOT) └─nvme0n1p4 259:5 0 1007.5K 0 part (DATA) Edited June 15Jun 15 by MowMdown
June 15Jun 15 Community Expert 43 minutes ago, MowMdown said:I cant remember what the 2nd partition is but it's small.Partition #1 is used for legacy (BIOS) boot, the smaller #2 is the EFI system partition.
June 15Jun 15 Community Expert 9 minutes ago, JorgeB said:Partition #1 is used for legacy (BIOS) boot, the smaller #2 is the EFI system partition.Yeah 1M is too small, I see that now. Thanks for the catch. I just knew it existed somewhere.
June 15Jun 15 Community Expert Also, and just for competition, partition #4 always exists, even for a dedicated pool, but in those cases it will be very small, around 1MB. I believe this was done mostly for code simplification.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.