RHAS3U3-SoftwareRAID-e2label

[Matthias Bayer]

Hi,

I have a software raid5 setup for a data partition consisting of 3 disks (sdb1,sdc1,sdd1). I labeled the device /dev/md0 with the command 'e2label /dev/md0 /data' and enterd the following entry into /etc/fstab 'LABEL=/data /data ext3 defaults 1 2'. Everything worked fine, the raid device started and was mounted correct after reboot BUT then I changed the disk label to /datavol and changed the entry in /etc/fstbab accordingly (with command e2label /dev/md0 /datavol)- since this time I cannot automatically mount the raid device during bootup, it fails with:
Starting up Raid device md0 (skipped) -
"A block group is missing an inode table while checking ext3 journal for /datavol".

If I mount with '/dev/md0 /data ext3 defaults 1 2' withinh the /etc/fstab everything works fine again after reboot.

any suggestions or ideas whats wrong ?

thanks for any help,
Matthias

[Vitaly Karasik_1]

did you re-check that you have *the same* label in fstab and in "e2label /dev/md0" output?

[Matthias Bayer]

yes, i re-checked and i also tried different and same names for the label as for the mountpoint but it is reproducable - as soon as i change the label the first time the system cannot automatically boot up anymore .....

Matthias

[Johannes Krackowizer_1]

hi matthias,

change the line in /etc/fstab from:
LABEL=/data /data ext3 defaults 1 2

to:
/dev/md0 /data ext3 defaults 1 2

so you don't need to label your volumes.

best regards,

johannes

[Jiangbo Lu]

Hi,

I am having the exact problem. Did you get it resolved other than use the device name instead of a LABEL?

Thanks,

Jiangbo

[Matthias Bayer]

Hi Jiangbo,

i had this problem only on one system (but there reproducable !!) .. i tried it several times with new installations but this exact problem never showed up again on any of this new installations !!!

i don't know what is corrupted or where and i didn't solve it other than just mounting the device directly instead of using labels :-(

sorry i have no good solution for you...

bye
Matthias

[Johannes Krackowizer_1]

Hi Matthias,

try fsck to rpair /dev/md0, perhaps something wents wrong with your configuration.

best regards,

johannes