[gentoo-user] raid autodetection uuid differences
Hello, I've got a new gentoo box with two drives that i'm using raid1 on. On boot the md raid autodetection is failing. Here's the error i'm getting: md: Waiting for all devices to be available before autodetect md: If you don't use raid, use raid=noautodetect md: Autodetecting RAID arrays. md: Scanned 4 and added 4 devices. md: autorun ... md: considering sda3 ... md: adding sda3 ... md: sda1 has different UUID to sda3 md: adding sdb3 ... md: sdb1 has different UUID to sda3 md: created md3 md: bindsdb3 md: bindsda3 md: running: sda3sdb3 md: personality for level 1 is not loaded! md: do_md_run() returned -22 md: md3 stopped. md: unbindsda3 md: export_rdev(sda3) md: unbindsdb3 md: export_rdev(sdb3) md: considering sda1 ... md: adding sda1 ... md: adding sdb1 ... md: created md1 md: bindsdb1 md: bindsda1 md: running: sda1sdb1 md: personality for level 1 is not loaded! md: do_md_run() returned -22 md: md1 stopped. md: unbindsda1 md: export_rdev(sda1) md: unbindsdb1 md: export_rdev(sdb1) md: ... autorun DONE. EXT3-fs: unable to read superblock FAT: unable to read boot sector VFS: Cannot open root device md3 or unknown-block(9,3) Please append a correct root= boot option; here are the available partitions: 1600 4194302 hdc driver: ide-cdrom 081020971520 sdb driver: sd 0811 40131 sdb1 0812 530145 sdb2 081320394517 sdb3 080020971520 sda driver: sd 0801 40131 sda1 0802 530145 sda2 080320394517 sda3 Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(9,3) Pid: 1, comm: swapper Not tainted 2.6.32-gentoo-r7 #1 Call Trace: [c12e4bd9] ? panic+0x38/0xd3 [c143fb34] ? mount_block_root+0x1e9/0x1fd [c143fb81] ? mount_root+0x39/0x4d [c143fcd7] ? prepare_namespace+0x142/0x168 [c143f31e] ? kernel_init+0x167/0x172 [c143f1b7] ? kernel_init+0x0/0x172 [c100344f] ? kernel_thread_helper+0x7/0x10 I've booted with a live CD and checked the arrays they look good, i'm not sure how to correct this UUID issue, any suggestions welcome. Thanks. Dave.
Re: [gentoo-user] raid autodetection uuid differences
On Samstag 17 April 2010, David Mehler wrote: Hello, I've got a new gentoo box with two drives that i'm using raid1 on. On boot the md raid autodetection is failing. Here's the error i'm getting: md: Waiting for all devices to be available before autodetect md: If you don't use raid, use raid=noautodetect md: Autodetecting RAID arrays. md: Scanned 4 and added 4 devices. md: autorun ... md: considering sda3 ... md: adding sda3 ... md: sda1 has different UUID to sda3 md: adding sdb3 ... md: sdb1 has different UUID to sda3 md: created md3 md: bindsdb3 md: bindsda3 md: running: sda3sdb3 md: personality for level 1 is not loaded! md: do_md_run() returned -22 md: md3 stopped. md: unbindsda3 md: export_rdev(sda3) md: unbindsdb3 md: export_rdev(sdb3) md: considering sda1 ... md: adding sda1 ... md: adding sdb1 ... md: created md1 md: bindsdb1 md: bindsda1 md: running: sda1sdb1 md: personality for level 1 is not loaded! md: do_md_run() returned -22 md: md1 stopped. md: unbindsda1 md: export_rdev(sda1) md: unbindsdb1 md: export_rdev(sdb1) md: ... autorun DONE. EXT3-fs: unable to read superblock FAT: unable to read boot sector VFS: Cannot open root device md3 or unknown-block(9,3) Please append a correct root= boot option; here are the available partitions: 1600 4194302 hdc driver: ide-cdrom 081020971520 sdb driver: sd 0811 40131 sdb1 0812 530145 sdb2 081320394517 sdb3 080020971520 sda driver: sd 0801 40131 sda1 0802 530145 sda2 080320394517 sda3 Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(9,3) Pid: 1, comm: swapper Not tainted 2.6.32-gentoo-r7 #1 Call Trace: [c12e4bd9] ? panic+0x38/0xd3 [c143fb34] ? mount_block_root+0x1e9/0x1fd [c143fb81] ? mount_root+0x39/0x4d [c143fcd7] ? prepare_namespace+0x142/0x168 [c143f31e] ? kernel_init+0x167/0x172 [c143f1b7] ? kernel_init+0x0/0x172 [c100344f] ? kernel_thread_helper+0x7/0x10 I've booted with a live CD and checked the arrays they look good, i'm not sure how to correct this UUID issue, any suggestions welcome. Thanks. Dave. well, don't make raid1 support a module. Put it into the kernel.
Re: [gentoo-user] raid autodetection uuid differences
On Sat, Apr 17, 2010 at 12:00 PM, David Mehler dave.meh...@gmail.com wrote: Hello, I've got a new gentoo box with two drives that i'm using raid1 on. On boot the md raid autodetection is failing. Here's the error i'm getting: SNIP I've booted with a live CD and checked the arrays they look good, i'm not sure how to correct this UUID issue, any suggestions welcome. Thanks. Dave. Dave, I suspect this is the same problem I had two weeks ago. Search for my thread called: How does grub assemble a RAID1 for / ?? and read that for background. If I'm correct this is a metadata issue. You have two choices: 1) What I think you've done is create the RAID1 without specifying --metadata=0.90. If that's correct then you __must__ use an initramfs to load mdadm. I'm studying how to do that myself. 2) Rebuild the RAID1 specifying --metadata=0.90 which is the only metadata type that the kernel can auto-assemble for you at boot time without an initramfs, and what I'm currently using here. Hope this helps, Mark
