#SOFTRAID ERROR 32 BIT#
#SOFTRAID ERROR FULL#

I would understand this way of problem handling if the RAID contained essential data and was needed, but it will never be mounted during bootup and also is not contained in fstab, it is as if a broken device just prevents your system from bootup (in fact any USBthumbdrive with a Superblock describing it as part of a large RAID will do that) It also does not matter if the RAID is included in nf or if it is completely empty This is really annoying and can by far not be an intended feature… So far I have found no way to boot my system.Īs long as a disk which is part of an incomplete RAID is connected I will always end up in a BusyBox recovery shell, one way or another. Passing 'bootdegraded=true' is no solution I am attaching a screencap right after it drops into the shell and will also attach the complete dmesg from this error in a separate comment. The second issue can be worked around if #1 does not exist since the disks are there and by the time the system is fully up all the disks have reported in. (2) the point at which the system checks whether this is the case or not happens way too early (for me it happens right after the 4 second mark) and misses disks that might take a while to get up and running (on a clean boot the last of my disks show up around the 5-6 second mark) (1) if you have a part of an old array or a severely degraded array connected to the system, it is not possible to boot So it looks like there are really 2 separate issues: It looks like there is no way to boot a system if it has one disk that reads as being part of a 3+ disk array connected to it. I tried dropping the array from nf and that made no difference. I had forgotten to set the boot degraded option so I had to manually select y when prompted, the system tried to create the array, creation failed and it dropped into the shell.

I shut down the system and disconnected 2 of the 3 drives and booted again. I set up a file system added the array to fstab and nf, rebooted to make sure everything worked as it should and it did. Once up in installed mdadm and created an array from the 3 small drives. I set up a system with on system drive and 3 small drives. Desktop may work as well but I have seen several reports of the initiramfs shell getting blocked by the desktop UI so I through it was simpler to just start without anything graphical.

#SOFTRAID ERROR 32 BIT#

I am using ubuntu 11.10 server both 64 and 32 bit work fine. I was able to reproduce one of the issues in a vmware instance. I will also post an example of a 'clean' boot once I get the degraded array from my last error rebuilt. It brings up the question to me of why there is not a middle ground option between don't boot at all and boot degraded to just boot and not assemble the array? The current options kind of force someone without physical system access to risk the array just to get the system up. if one of the arrays has made it to 4/5 and one has not, it assembles the 4/5 array and now I need to do a resync once I get my system up cleanly. if neither array had made it to 4/5 by the time the check is run and it drops to the shell creating neither array I am fine If the boot is allowed to go through all 10 disks are found and everything comes up cleanly in spite of the errors

I will post dmesg of this in a bit, but triggering these errors, if it can actually create one of the arrays, but halts the boot is now causing problems:

#SOFTRAID ERROR FULL#

A follow-up on that comment I am using the bootdegraded=true parameter and each of the two arrays has 5 disks, if I get a full boot all 5 disks come up, it seems like all 10 have just not responded by the time this test comes in and decides it is tired of waiting.

Softraid error