| View previous topic :: View next topic |
| Author |
Message |
nl0pvm
n00b
Joined: 08 Nov 2004
Posts: 46
Location: Netherlands
|
 Posted: Tue Jan 31, 2006 3:45 pm Post subject: RAID problem Not starting at boot but does start man[solved] |
 |
|
Hi,
I have a sparc running raid 5 which does not auto start its software raid5 anymore. It still does start its raid1 root disk and swap....
from dmesg:
| Code: |
md: raid0 personality registered as nr 2
md: raid1 personality registered as nr 3
md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
NET: Registered protocol family 2
IP: routing cache hash table of 4096 buckets, 64Kbytes
TCP established hash table entries: 32768 (order: 6, 524288 bytes)
TCP bind hash table entries: 32768 (order: 6, 524288 bytes)
TCP: Hash tables configured (established 32768 bind 32768)
NET: Registered protocol family 1
NET: Registered protocol family 17
NET: Registered protocol family 8
NET: Registered protocol family 20
devfs_mk_dev: could not append to parent for md/0
md: Autodetecting RAID arrays.
md: autorun ...
md: considering sdf1 ...
md: adding sdf1 ...
md: adding sde1 ...
md: adding sdd1 ...
md: adding sdc1 ...
md: sdb4 has different UUID to sdf1
md: sdb2 has different UUID to sdf1
md: sdb1 has different UUID to sdf1
md: sda4 has different UUID to sdf1
md: sda2 has different UUID to sdf1
md: sda1 has different UUID to sdf1
devfs_mk_dev: could not append to parent for md/4
md: created md4
md: bind<sdc1>
md: bind<sdd1>
md: bind<sde1>
md: bind<sdf1>
md: running: <sdf1><sde1><sdd1><sdc1>
md: personality 4 is not loaded!
md: do_md_run() returned -22
md: md4 stopped.
md: unbind<sdf1>
md: export_rdev(sdf1)
md: unbind<sde1>
md: export_rdev(sde1)
md: unbind<sdd1>
md: export_rdev(sdd1)
md: unbind<sdc1>
md: export_rdev(sdc1)
md: considering sdb4 ...
md: adding sdb4 ...
md: sdb2 has different UUID to sdb4
md: sdb1 has different UUID to sdb4
md: adding sda4 ...
md: sda2 has different UUID to sdb4
md: sda1 has different UUID to sdb4
devfs_mk_dev: could not append to parent for md/2
md: created md2
md: bind<sda4>
md: bind<sdb4>
md: running: <sdb4><sda4>
raid1: raid set md2 active with 2 out of 2 mirrors
md: considering sdb2 ...
md: adding sdb2 ...
md: sdb1 has different UUID to sdb2
md: adding sda2 ...
md: sda1 has different UUID to sdb2
devfs_mk_dev: could not append to parent for md/1
md: created md1
md: bind<sda2>
md: bind<sdb2>
md: running: <sdb2><sda2>
md1: setting max_sectors to 128, segment boundary to 32767
raid0: looking at sdb2
raid0: comparing sdb2(499072) with sdb2(499072)
raid0: END
raid0: ==> UNIQUE
raid0: 1 zones
raid0: looking at sda2
raid0: comparing sda2(499072) with sdb2(499072)
raid0: EQUAL
raid0: FINAL 1 zones
raid0: done.
raid0 : md_size is 998144 blocks.
raid0 : conf->hash_spacing is 998144 blocks.
raid0 : nb_zone is 1.
raid0 : Allocating 8 bytes for hash.
md: considering sdb1 ...
md: adding sdb1 ...
md: adding sda1 ...
md: created md0
md: bind<sda1>
md: bind<sdb1>
md: running: <sdb1><sda1>
raid1: raid set md0 active with 2 out of 2 mirrors
md: ... autorun DONE.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Mounted devfs on /dev
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS on md2, internal journal
md: md4 stopped.
kjournald starting. Commit interval 5 seconds
EXT3 FS on md0, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
ReiserFS: md4: warning: sh-2006: read_super_block: bread failed (dev md4, block
1, size 8192)
ReiserFS: md4: warning: sh-2006: read_super_block: bread failed (dev md4, block
8, size 8192)
ReiserFS: md4: warning: sh-2021: reiserfs_fill_super: can not find reiserfs on m
d4
|
after starting at Jan 31 16:29:26 md4 successful manually with mdadm -A /dev/md4
in /var/log/messages:
| Code: |
Jan 31 18:26:00 dory kernel: md: considering sdb1 ...
Jan 31 18:26:00 dory kernel: md: adding sdb1 ...
Jan 31 18:26:00 dory kernel: md: adding sda1 ...
Jan 31 18:26:00 dory kernel: md: created md0
Jan 31 18:26:00 dory kernel: md: bind<sda1>
Jan 31 18:26:00 dory kernel: md: bind<sdb1>
Jan 31 18:26:00 dory kernel: md: running: <sdb1><sda1>
Jan 31 18:26:00 dory kernel: raid1: raid set md0 active with 2 out of 2 mirrors
Jan 31 18:26:00 dory kernel: md: ... autorun DONE.
Jan 31 18:26:00 dory kernel: kjournald starting. Commit interval 5 seconds
Jan 31 18:26:00 dory kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jan 31 18:26:00 dory kernel: VFS: Mounted root (ext3 filesystem) readonly.
Jan 31 18:26:00 dory kernel: Mounted devfs on /dev
Jan 31 18:26:00 dory kernel: EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
Jan 31 18:26:00 dory kernel: EXT3 FS on md2, internal journal
Jan 31 18:26:00 dory kernel: md: md4 stopped.
Jan 31 18:26:00 dory kernel: kjournald starting. Commit interval 5 seconds
Jan 31 18:26:00 dory kernel: EXT3 FS on md0, internal journal
Jan 31 18:26:00 dory kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jan 31 18:26:00 dory kernel: ReiserFS: md4: warning: sh-2006: read_super_block: bread failed (dev md4, block 1, size 8192)
Jan 31 18:26:00 dory kernel: ReiserFS: md4: warning: sh-2006: read_super_block: bread failed (dev md4, block 8, size 8192)
Jan 31 18:26:00 dory kernel: ReiserFS: md4: warning: sh-2021: reiserfs_fill_super: can not find reiserfs on md4
Jan 31 18:26:00 dory kernel: Adding 998128k swap on /dev/md1. Priority:-1 extents:1
Jan 31 18:26:08 dory kernel: eth0: Link is up using internal transceiver at 100Mb/s, Full Duplex.
Jan 31 16:27:02 dory kernel: ip_tables: (C) 2000-2002 Netfilter core team
Jan 31 16:27:02 dory kernel: ip_conntrack version 2.1 (2005 buckets, 16040 max) - 344 bytes per conntrack
Jan 31 16:29:26 dory kernel: md: md4 stopped.
Jan 31 16:29:26 dory kernel: md: bind<sdd1>
Jan 31 16:29:26 dory kernel: md: bind<sde1>
Jan 31 16:29:26 dory kernel: md: bind<sdf1>
Jan 31 16:29:26 dory kernel: md: bind<sdc1>
Jan 31 16:29:26 dory kernel: raid5: measuring checksumming speed
Jan 31 16:29:26 dory kernel: VIS : 96.000 MB/sec
Jan 31 16:29:26 dory kernel: raid5: using function: VIS (96.000 MB/sec)
Jan 31 16:29:26 dory kernel: md: raid5 personality registered as nr 4
Jan 31 16:29:26 dory kernel: raid5: device sdc1 operational as raid disk 0
Jan 31 16:29:26 dory kernel: raid5: device sdf1 operational as raid disk 3
Jan 31 16:29:26 dory kernel: raid5: device sde1 operational as raid disk 2
Jan 31 16:29:26 dory kernel: raid5: device sdd1 operational as raid disk 1
Jan 31 16:29:26 dory kernel: raid5: allocated 8356kB for md4
Jan 31 16:29:26 dory kernel: raid5: raid level 5 set md4 active with 4 out of 4 devices, algorithm 2
Jan 31 16:29:26 dory kernel: RAID5 conf printout:
Jan 31 16:29:26 dory kernel: --- rd:4 wd:4 fd:0
Jan 31 16:29:26 dory kernel: disk 0, o:1, dev:sdc1
Jan 31 16:29:26 dory kernel: disk 1, o:1, dev:sdd1
Jan 31 16:29:26 dory kernel: disk 2, o:1, dev:sde1
Jan 31 16:29:26 dory kernel: disk 3, o:1, dev:sdf1
|
my /proc/mdstat looks like this:
| Code: |
Personalities : [raid0] [raid1] [raid5]
md1 : active raid0 sdb2[1] sda2[0]
998144 blocks 64k chunks
md2 : active raid1 sdb4[1] sda4[0]
8244864 blocks [2/2] [UU]
md4 : active raid5 sdc1[0] sdf1[3] sde1[2] sdd1[1]
26496000 blocks level 5, 64k chunk, algorithm 2 [4/4] [UUUU]
md0 : active raid1 sdb1[1] sda1[0]
96832 blocks [2/2] [UU]
unused devices: <none>
|
As you can see there's no real error but still it is not mounted at root.
before this update i installed the following packages that could relate???
- sys-apps/hotplug-base-20040401
- sys-fs/udev-079-r1
_________________
SUN E250 2 x UltrasparcII@400Mhz 512MB RAM 6 x 9GB Kernel 2.6.8 (SMP)
SUN E250 UltrasparcII@400Mhz 512MB RAM 2 x 9GB Kernel 2.6.11
SUN E250 UltrasparcII@400Mhz 1024MB RAM 2 x 9GB
SPARCstation 10 MP 2 x 390Z55@40Mhz 512MB RAM Kernel 2.4.30 4GB & 9GB
Last edited by nl0pvm on Tue Jan 31, 2006 8:11 pm; edited 1 time in total |
|
| Back to top |
|
 |
SnakeByte
Apprentice
Joined: 04 Oct 2002
Posts: 177
Location: Europe - Germany
|
| Posted: Tue Jan 31, 2006 8:07 pm Post subject: |
|
|
Hi nl0pvm,
is it possible that you also changed the kernel?
From your dmesg:
| Quote: |
md: raid0 personality registered as nr 2
md: raid1 personality registered as nr 3
md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
|
There should also be a line for the raid5 personality.
If it is configured to be a loadable kernel module it would explain why you can start it later on.
| Quote: |
Jan 31 16:29:26 dory kernel: raid5: measuring checksumming speed
Jan 31 16:29:26 dory kernel: VIS : 96.000 MB/sec
Jan 31 16:29:26 dory kernel: raid5: using function: VIS (96.000 MB/sec)
Jan 31 16:29:26 dory kernel: md: raid5 personality registered as nr 4
Jan 31 16:29:26 dory kernel: raid5: device sdc1 operational as raid disk 0
Jan 31 16:29:26 dory kernel: raid5: device sdf1 operational as raid disk 3
Jan 31 16:29:26 dory kernel: raid5: device sde1 operational as raid disk 2
Jan 31 16:29:26 dory kernel: raid5: device sdd1 operational as raid disk 1
Jan 31 16:29:26 dory kernel: raid5: allocated 8356kB for md4
Jan 31 16:29:26 dory kernel: raid5: raid level 5 set md4 active with 4 out of 4 devices, algorithm 2
Jan 31 16:29:26 dory kernel: RAID5 conf printout:
|
If there is a problem with otplug ( should not ) or udev ( more likely )
you can check the contents of /dev/ right after rebooting.
When /dev/md4 is missing think about blaming udev and/or its configuration.
Just for information, is coldplug ( managing already connected stuff at boot ) also installed?
regards |
|
| Back to top |
|
|
nl0pvm
n00b
Joined: 08 Nov 2004
Posts: 46
Location: Netherlands
|
| Posted: Tue Jan 31, 2006 8:19 pm Post subject: |
|
|
Hi, thank you very much for your reaction... after all.. it had something todo with /dev and kernel too
what was the problem?
well... a baselayout crippled my complete system... really bad if you ask me......
I haven't been warned for this discontinous change like postfix en apache does.....
what happened... baselayout included for me a discontinous upgrade from devfs to udevfs...
this crippeled my system as at boot /dev/ was not working good enough so my raid5 array could not be started with mdadm during init..
In the startpost of me was talking about the module that was not compiled into the kernel but HEY... i knew it wasn't in the kernel and it never has been in the kernel as well... and that error has always been there at automount time........
the realproblem was that mdadm was not able to create the raid devices including my raid5 array ... (way later in the bootprocess than automount) .....because /dev/ was not available..but how did i know.. ... until 1 read ONE post on this great forum with all helpfull people like you SnakeByte that was talking about baselayout and raid problems........
if you like a more complete answer than i have provided already please let me know as i'm always willing to contribute/help you.
_________________
SUN E250 2 x UltrasparcII@400Mhz 512MB RAM 6 x 9GB Kernel 2.6.8 (SMP)
SUN E250 UltrasparcII@400Mhz 512MB RAM 2 x 9GB Kernel 2.6.11
SUN E250 UltrasparcII@400Mhz 1024MB RAM 2 x 9GB
SPARCstation 10 MP 2 x 390Z55@40Mhz 512MB RAM Kernel 2.4.30 4GB & 9GB |
|
| Back to top |
|
|
nl0pvm
n00b
Joined: 08 Nov 2004
Posts: 46
Location: Netherlands
|
| Posted: Thu Mar 23, 2006 6:01 pm Post subject: |
|
|
I've filed a bug for this complete baselayout hell 
https://bugs.gentoo.org/show_bug.cgi?id=127331
_________________
SUN E250 2 x UltrasparcII@400Mhz 512MB RAM 6 x 9GB Kernel 2.6.8 (SMP)
SUN E250 UltrasparcII@400Mhz 512MB RAM 2 x 9GB Kernel 2.6.11
SUN E250 UltrasparcII@400Mhz 1024MB RAM 2 x 9GB
SPARCstation 10 MP 2 x 390Z55@40Mhz 512MB RAM Kernel 2.4.30 4GB & 9GB |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
