SW Raid1 Installation - boot problem
Herbert Straub
herbert at linuxhacker.at
Fri Apr 8 18:11:53 UTC 2005
The intallation go straight forward. After the first reboot, the boot
stop (details see below). With mount -a and CTRL-d the boot continue.
There are two error situations, one in /etc/fstab (doesn't find
/dev/md3) and the same error in /etc/mdadm/mdadm.conf.
The following two changes solve the problem:
- Using LABEL= statements in /etc/fstab::
LABEL=/ / ext3 defaults,errors=remount-ro 0 1
LABEL=/var /var ext3 defaults 0 2
Removing DEVICE statement and adding auto=md in /etc/mdadm/mdadm.conf::
ARRAY /dev/md3 level=raid1 num-devices=2
UUID=72950ff5:90036b68:5751e315:c2df18f8 auto=md
This is the boot error situation::
* Starting RAID devices...
mdadm: error opening /dev/md3: No such file or directory
mdadm: error opening /dev/md2: No such file or directory
mdadm: error opening /dev/md1: No such file or directory [fail]
* Setting up LVM Volume Management system... [ ok ]
md: md2: read array is not clean -- starting background reconstruction
* Checking all file systems...
fsck.ext3: No such file or directory whie trying to open /dev/md3
/dev/md3:
The superblock could not be read or does not describe a correcrt ext2
filesystem. If the device is valid and it really contains an ext2
fileystem (and not swap of ufs or someting else), then the superblock
is corrupt, and you might try running e2fsck with an alternate
superblock:
e2fsck -b 8193 <device>
* fsck failed. Please repair manually.
* CONTROL-D will exit from this shell and continue system startup.
root@(none): #
Best Regards
Herbert Straub
More information about the ubuntu-users
mailing list