fsck.ext3: Unable to resolve 'UUID=d073d821-427e-4aea-bd1f-53fcad4e0e81'
error and halting on boot, and found this bug report. I have a hotswap bay and sometimes drives are not in the bay during boot. I wanted boot to continue without checking these absent drives. The solution, as described in the fsck man page was to make sure that there was 0 in the 6th field of fstab, rather than non-zero. (The 6th field specified the order for boot-time filesystem check, with 0 being skip.) I'm not sure if this helps out with any of the situations described here, but basically what I did was change
OFFTOPIC
I've run into the
fsck.ext3: Unable to resolve 'UUID=d073d821- 427e-4aea- bd1f-53fcad4e0e 81'
error and halting on boot, and found this bug report. I have a hotswap bay and sometimes drives are not in the bay during boot. I wanted boot to continue without checking these absent drives. The solution, as described in the fsck man page was to make sure that there was 0 in the 6th field of fstab, rather than non-zero. (The 6th field specified the order for boot-time filesystem check, with 0 being skip.) I'm not sure if this helps out with any of the situations described here, but basically what I did was change
UUID=7855008b- 966e-4e4f- 85ca-21f84ff13a 03 /media/nearline ext3 noauto, rw,suid, dev,exec, nouser, async 0 1
to
UUID=7855008b- 966e-4e4f- 85ca-21f84ff13a 03 /media/nearline ext3 noauto, rw,suid, dev,exec, nouser, async 0 0