HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials

HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials (http://www.howtoforge.com/forums/index.php)
-   HOWTO-Related Questions (http://www.howtoforge.com/forums/forumdisplay.php?f=2)
-   -   CentOS 6.2 boot problem running software Raid1 (http://www.howtoforge.com/forums/showthread.php?t=56141)

bzzik 11th February 2012 22:42

CentOS 6.2 boot problem running software Raid1
 
Hi!

I followed this tutorial to setup Raid1 on running just installed CentOS 6.2. The system boots nice from RAID arrays using either first or second HDD when both HDDs are connected. But when I remove one of HDD the system hangs during boot showing error multiple times:
Quote:

mount: you must specify the filesystem type
And after that:
Quote:

kernel panic - not syncing attempted to kill init
I found an issue in CentOS bug tracker and it looks like mine, but slightly different.

Here is my system info:
Quote:

[root@s1 ~]# fdisk -l

Disk /dev/sdb: 500.1 GB, 500106780160 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x28383579

Device Boot Start End Blocks Id System
/dev/sdb1 * 1 26 204800 fd Linux raid autodetect
Partition 1 does not end on cylinder boundary.
/dev/sdb2 26 12774 102400000 fd Linux raid autodetect
/dev/sdb3 12774 58668 368640000 fd Linux raid autodetect
/dev/sdb4 58668 60802 17138688 5 Extended
/dev/sdb5 58668 59943 10240000 fd Linux raid autodetect
/dev/sdb6 59943 60204 2097152 fd Linux raid autodetect

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00034d17

Device Boot Start End Blocks Id System
/dev/sda1 * 1 26 204800 fd Linux raid autodetect
Partition 1 does not end on cylinder boundary.
/dev/sda2 26 12774 102400000 fd Linux raid autodetect
/dev/sda3 12774 58668 368640000 fd Linux raid autodetect
/dev/sda4 58668 60802 17138688 5 Extended
/dev/sda5 58668 59943 10240000 fd Linux raid autodetect
/dev/sda6 59943 60204 2097152 fd Linux raid autodetect

Disk /dev/md0: 209 MB, 209649664 bytes
2 heads, 4 sectors/track, 51184 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/md0 doesn't contain a valid partition table

Disk /dev/md4: 2146 MB, 2146422784 bytes
2 heads, 4 sectors/track, 524029 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/md4 doesn't contain a valid partition table

Disk /dev/md2: 377.5 GB, 377486172160 bytes
2 heads, 4 sectors/track, 92159710 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/md2 doesn't contain a valid partition table

Disk /dev/md3: 10.5 GB, 10484637696 bytes
2 heads, 4 sectors/track, 2559726 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/md3 doesn't contain a valid partition table

Disk /dev/md1: 104.9 GB, 104856477696 bytes
2 heads, 4 sectors/track, 25599726 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/md1 doesn't contain a valid partition table
Quote:

[root@s1 ~]# cat /proc/mdstat
Personalities : [raid1]
md1 : active raid1 sda2[1] sdb2[2]
102398904 blocks super 1.2 [2/2] [UU]

md3 : active raid1 sda5[1] sdb5[2]
10238904 blocks super 1.2 [2/2] [UU]

md2 : active raid1 sda3[1] sdb3[2]
368638840 blocks super 1.2 [2/2] [UU]

md4 : active raid1 sda6[1] sdb6[2]
2096116 blocks super 1.2 [2/2] [UU]

md0 : active raid1 sda1[1] sdb1[0]
204736 blocks [2/2] [UU]

unused devices: <none>
Quote:

[root@s1 ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/md3 9.7G 1.6G 7.6G 17% /
tmpfs 1.9G 0 1.9G 0% /dev/shm
/dev/md0 194M 42M 142M 23% /boot
/dev/md2 347G 195M 329G 1% /home
/dev/md1 97G 259M 91G 1% /var
FSTAB
Quote:

#UUID=58a78759-6476-4221-a705-bb73f43930f0 / ext4 defaults 1 1
/dev/md3 / ext4 defaults 1 1
#UUID=794bd78e-b860-4acd-8017-8e0b44e709f1 /boot ext2 defaults 1 2
/dev/md0 /boot ext2 defaults 1 2
#UUID=f5665c1c-c71b-43c9-8eb7-fedd4c70f841 /home ext4 defaults 1 2
/dev/md2 /home ext4 defaults 1 2
#UUID=8cf9e085-fcc6-4369-81cb-a1e6531b31a4 /var ext4 defaults 1 2
/dev/md1 /var ext4 defaults 1 2
#UUID=aab8f4f9-b897-4315-abf2-ba1b52be8d3b swap swap defaults 0 0
/dev/md4 swap swap defaults 0 0
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
Quote:

[root@s1 ~]# uname -r
2.6.32-220.el6.x86_64

bzzik 16th February 2012 11:56

Ok, i fixed it only installing 6.1. Did it following How to Setup a Software RAID on CentOS 5.

Then I added to yum.conf line:
Quote:

exclude=dracut*
and did:
Quote:

yum update
CentOS has updated to latest 6.2 kernel and after that I have tested fail of both hard drives. System boots as it should! That's it!


All times are GMT +2. The time now is 14:45.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.