Help Request- converting Raid root drives for 2.6.8+ boot
Hi all, Since 2.6.8.1 + kernels, the kernel is unable to find my raid arrays. I have searched and found that riadstart is deprecated and broken. (raidstart is what suse uses by default), I have since installed upto date mdadm tools, and tried setting up a /etc/mdadm/mdadm.conf with my raid drives, and also reruning mkinitrd for my new kernels with root specified. But the kernel still refuses to boot my root partition. I boot off a non raided partition sda1 and also have swap on a non raided partition sdb1. My raid setup is as bellow: ARRAY /dev/md1 level=raid0 num-devices=2 UUID=da49e3b8:d0b65de4:7817e388:54c4980d devices=/dev/sda3,/dev/sdb3 ARRAY /dev/md0 level=raid1 num-devices=2 UUID=3702dbfc:1572856f:4f673190:fc5212c4 devices=/dev/sda2,/dev/sdb2 Now I've tried using a number of howto's with sata raid root etc, but nothing seems to work. This is what the last functioning kernel that boots, boot process looks like: ata1: SATA max UDMA/133 cmd 0x9800 ctl 0x9C02 bmdma 0xA800 irq 20 ata2: SATA max UDMA/133 cmd 0xA000 ctl 0xA402 bmdma 0xA808 irq 20 ata1: dev 0 cfg 49:2f00 82:74eb 83:7fea 84:4023 85:74e9 86:3e02 87:4023 88:203f ata1: dev 0 ATA, max UDMA/100, 321672960 sectors: lba48 ata1: dev 0 configured for UDMA/100 scsi0 : sata_via ata2: dev 0 cfg 49:2f00 82:74eb 83:7fea 84:4023 85:74e9 86:3e02 87:4023 88:203f ata2: dev 0 ATA, max UDMA/100, 321672960 sectors: lba48 ata2: dev 0 configured for UDMA/100 scsi1 : sata_via Vendor: ATA Model: HDS722516VLSA80 Rev: V34O Type: Direct-Access ANSI SCSI revision: 05 Vendor: ATA Model: HDS722516VLSA80 Rev: V34O Type: Direct-Access ANSI SCSI revision: 05 SCSI device sda: 321672960 512-byte hdwr sectors (164697 MB) SCSI device sda: drive cache: write back sda: sda1 sda2 sda3 Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 SCSI device sdb: 321672960 512-byte hdwr sectors (164697 MB) SCSI device sdb: drive cache: write back sdb: sdb1 sdb2 sdb3 Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0 mice: PS/2 mouse device common for all mice gameport: pci0000:00:08.1 speed 1187 kHz serio: i8042 AUX port at 0x60,0x64 irq 12 input: ImExPS/2 Generic Explorer Mouse on isa0060/serio1 serio: i8042 KBD port at 0x60,0x64 irq 1 input: AT Translated Set 2 keyboard on isa0060/serio0 i2c /dev entries driver md: raid0 personality registered as nr 2 md: raid1 personality registered as nr 3 md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27 device-mapper: 4.1.0-ioctl (2003-12-10) initialised: dm@uk.sistina.com Advanced Linux Sound Architecture Driver Version 1.0.4 (Mon May 17 14:31:44 2004 UTC). ACPI: PCI interrupt 0000:00:08.0[A] -> GSI 19 (level, low) -> IRQ 19 ALSA device list: #0: Sound Blaster Audigy2 (rev.4) at 0x9000, irq 19 oprofile: using NMI interrupt. NET: Registered protocol family 2 IP: routing cache hash table of 16384 buckets, 128Kbytes TCP: Hash tables configured (established 524288 bind 65536) NET: Registered protocol family 1 md: Autodetecting RAID arrays. md: autorun ... md: considering sdb3 ... md: adding sdb3 ... md: sdb2 has different UUID to sdb3 md: adding sda3 ... md: sda2 has different UUID to sdb3 md: created md1 md: bind<sda3> md: bind<sdb3> md: running: <sdb3><sda3> md1: setting max_sectors to 64, segment boundary to 16383 raid0: looking at sdb3 raid0: comparing sdb3(128841216) with sdb3(128841216) raid0: END raid0: ==> UNIQUE raid0: 1 zones raid0: looking at sda3 raid0: comparing sda3(128849216) with sdb3(128841216) raid0: NOT EQUAL raid0: comparing sda3(128849216) with sda3(128849216) raid0: END raid0: ==> UNIQUE raid0: 2 zones raid0: FINAL 2 zones raid0: zone 1 raid0: checking sda3 ... contained as device 0 (128849216) is smallest!. raid0: checking sdb3 ... nope. raid0: zone->nb_dev: 1, size: 8000 raid0: current zone offset: 128849216 raid0: done. raid0 : md_size is 257690432 blocks. raid0 : conf->hash_spacing is 257682432 blocks. raid0 : nb_zone is 2. raid0 : Allocating 16 bytes for hash. md: considering sdb2 ... md: adding sdb2 ... md: adding sda2 ... md: created md0 md: bind<sda2> md: bind<sdb2> md: running: <sdb2><sda2> raid1: raid set md0 active with 2 out of 2 mirrors md: ... autorun DONE. VFS: Mounted root (reiserfs filesystem) readonly. Freeing unused kernel memory: 188k freed md: raidstart(pid 473) used deprecated START_ARRAY ioctl. This will not be supported beyond 2.6 md: could not lock unknown-block(8,2). md: could not import unknown-block(8,2)! md: autostart unknown-block(0,2050) failed! md: raidstart(pid 473) used deprecated START_ARRAY ioctl. This will not be supported beyond 2.6 md: could not lock unknown-block(8,3). md: could not import unknown-block(8,3)! md: autostart unknown-block(0,2051) failed! md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. ReiserFS: sda1: found reiserfs format "3.6" with standard journal ReiserFS: sda1: using ordered data mode ReiserFS: sda1: journal params: device sda1, size 8192, journal first block 18,max trans len 1024, max batch 900, max commit age 30, max trans age 30 ReiserFS: sda1: checking transaction log (sda1) ReiserFS: sda1: Using r5 hash to sort names ReiserFS: md0: found reiserfs format "3.6" with standard journal ReiserFS: md0: using ordered data mode ReiserFS: md0: journal params: device md0, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 ReiserFS: md0: checking transaction log (md0) ReiserFS: md0: Using r5 hash to sort names Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0 Attached scsi generic sg1 at scsi1, channel 0, id 0, lun 0, type 0 hdb: CHECK for good STATUS hdc: CHECK for good STATUS But newer kernels stop at the autodetection part with an unable to find specified root device please specifiy with root= but it is correctly specified on the kernel command line as root=/dev/md1 (md0 is my home dir which is raid 1, md1 is root which is raid0) Kernels have raid 0 and 1 compiled in aswell as reiserfs which is what i'm using. Help! I need keep testing kernels but I can't continue with this fooked up raid.. BTW: This is related to this message: raidstart(pid 473) used deprecated START_ARRAY ioctl. This will not be supported beyond 2.6 Any help and comments are appreciated... A step by step howto do this would be helpfull. Kind regards Joel W New Zealand
Joel Wiramu Pauling <aenertia@aenertia.net> writes:
Hi all,
Since 2.6.8.1 + kernels, the kernel is unable to find my raid arrays. I
What kind of RAID is this? How was it setup?
have searched and found that riadstart is deprecated and broken. (raidstart is what suse uses by default), I have since installed upto date mdadm tools, and tried setting up a /etc/mdadm/mdadm.conf with my raid drives, and also reruning mkinitrd for my new kernels with root specified. But the kernel still refuses to boot my root partition.
I boot off a non raided partition sda1 and also have swap on a non raided partition sdb1.
My raid setup is as bellow:
ARRAY /dev/md1 level=raid0 num-devices=2 UUID=da49e3b8:d0b65de4:7817e388:54c4980d devices=/dev/sda3,/dev/sdb3 ARRAY /dev/md0 level=raid1 num-devices=2 UUID=3702dbfc:1572856f:4f673190:fc5212c4 devices=/dev/sda2,/dev/sdb2
Kernel 2.6.8 has renamed /dev/sd? to /dev/hd? :-(, you need to change the names. Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj SUSE Linux AG, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On Mon, 2004-10-25 at 15:30 +1300, Joel Wiramu Pauling wrote:
Hi all,
Since 2.6.8.1 + kernels, the kernel is unable to find my raid arrays. I have searched and found that riadstart is deprecated and broken. (raidstart is what suse uses by default), I have since installed upto date mdadm tools, and tried setting up a /etc/mdadm/mdadm.conf with my raid drives, and also reruning mkinitrd for my new kernels with root specified. But the kernel still refuses to boot my root partition.
I boot off a non raided partition sda1 and also have swap on a non raided partition sdb1.
My raid setup is as bellow:
ARRAY /dev/md1 level=raid0 num-devices=2 UUID=da49e3b8:d0b65de4:7817e388:54c4980d devices=/dev/sda3,/dev/sdb3 ARRAY /dev/md0 level=raid1 num-devices=2 UUID=3702dbfc:1572856f:4f673190:fc5212c4 devices=/dev/sda2,/dev/sdb2
Now I've tried using a number of howto's with sata raid root etc, but nothing seems to work. This is what the last functioning kernel that boots, boot process looks like: ata1: SATA max UDMA/133 cmd 0x9800 ctl 0x9C02 bmdma 0xA800 irq 20 ata2: SATA max UDMA/133 cmd 0xA000 ctl 0xA402 bmdma 0xA808 irq 20 ata1: dev 0 cfg 49:2f00 82:74eb 83:7fea 84:4023 85:74e9 86:3e02 87:4023 88:203f ata1: dev 0 ATA, max UDMA/100, 321672960 sectors: lba48 ata1: dev 0 configured for UDMA/100 scsi0 : sata_via ata2: dev 0 cfg 49:2f00 82:74eb 83:7fea 84:4023 85:74e9 86:3e02 87:4023 88:203f ata2: dev 0 ATA, max UDMA/100, 321672960 sectors: lba48 ata2: dev 0 configured for UDMA/100 scsi1 : sata_via Vendor: ATA Model: HDS722516VLSA80 Rev: V34O Type: Direct-Access ANSI SCSI revision: 05 Vendor: ATA Model: HDS722516VLSA80 Rev: V34O Type: Direct-Access ANSI SCSI revision: 05 SCSI device sda: 321672960 512-byte hdwr sectors (164697 MB) SCSI device sda: drive cache: write back sda: sda1 sda2 sda3 Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 SCSI device sdb: 321672960 512-byte hdwr sectors (164697 MB) SCSI device sdb: drive cache: write back sdb: sdb1 sdb2 sdb3 Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0 mice: PS/2 mouse device common for all mice gameport: pci0000:00:08.1 speed 1187 kHz serio: i8042 AUX port at 0x60,0x64 irq 12 input: ImExPS/2 Generic Explorer Mouse on isa0060/serio1 serio: i8042 KBD port at 0x60,0x64 irq 1 input: AT Translated Set 2 keyboard on isa0060/serio0 i2c /dev entries driver md: raid0 personality registered as nr 2 md: raid1 personality registered as nr 3 md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27 device-mapper: 4.1.0-ioctl (2003-12-10) initialised: dm@uk.sistina.com Advanced Linux Sound Architecture Driver Version 1.0.4 (Mon May 17 14:31:44 2004 UTC). ACPI: PCI interrupt 0000:00:08.0[A] -> GSI 19 (level, low) -> IRQ 19 ALSA device list: #0: Sound Blaster Audigy2 (rev.4) at 0x9000, irq 19 oprofile: using NMI interrupt. NET: Registered protocol family 2 IP: routing cache hash table of 16384 buckets, 128Kbytes TCP: Hash tables configured (established 524288 bind 65536) NET: Registered protocol family 1 md: Autodetecting RAID arrays. md: autorun ... md: considering sdb3 ... md: adding sdb3 ... md: sdb2 has different UUID to sdb3 md: adding sda3 ... md: sda2 has different UUID to sdb3 md: created md1 md: bind<sda3> md: bind<sdb3> md: running: <sdb3><sda3> md1: setting max_sectors to 64, segment boundary to 16383 raid0: looking at sdb3 raid0: comparing sdb3(128841216) with sdb3(128841216) raid0: END raid0: ==> UNIQUE raid0: 1 zones raid0: looking at sda3 raid0: comparing sda3(128849216) with sdb3(128841216) raid0: NOT EQUAL raid0: comparing sda3(128849216) with sda3(128849216) raid0: END raid0: ==> UNIQUE raid0: 2 zones raid0: FINAL 2 zones raid0: zone 1 raid0: checking sda3 ... contained as device 0 (128849216) is smallest!. raid0: checking sdb3 ... nope. raid0: zone->nb_dev: 1, size: 8000 raid0: current zone offset: 128849216 raid0: done. raid0 : md_size is 257690432 blocks. raid0 : conf->hash_spacing is 257682432 blocks. raid0 : nb_zone is 2. raid0 : Allocating 16 bytes for hash. md: considering sdb2 ... md: adding sdb2 ... md: adding sda2 ... md: created md0 md: bind<sda2> md: bind<sdb2> md: running: <sdb2><sda2> raid1: raid set md0 active with 2 out of 2 mirrors md: ... autorun DONE. VFS: Mounted root (reiserfs filesystem) readonly. Freeing unused kernel memory: 188k freed md: raidstart(pid 473) used deprecated START_ARRAY ioctl. This will not be supported beyond 2.6 md: could not lock unknown-block(8,2). md: could not import unknown-block(8,2)! md: autostart unknown-block(0,2050) failed! md: raidstart(pid 473) used deprecated START_ARRAY ioctl. This will not be supported beyond 2.6 md: could not lock unknown-block(8,3). md: could not import unknown-block(8,3)! md: autostart unknown-block(0,2051) failed! md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. ReiserFS: sda1: found reiserfs format "3.6" with standard journal ReiserFS: sda1: using ordered data mode ReiserFS: sda1: journal params: device sda1, size 8192, journal first block 18,max trans len 1024, max batch 900, max commit age 30, max trans age 30 ReiserFS: sda1: checking transaction log (sda1) ReiserFS: sda1: Using r5 hash to sort names ReiserFS: md0: found reiserfs format "3.6" with standard journal ReiserFS: md0: using ordered data mode ReiserFS: md0: journal params: device md0, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 ReiserFS: md0: checking transaction log (md0) ReiserFS: md0: Using r5 hash to sort names Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0 Attached scsi generic sg1 at scsi1, channel 0, id 0, lun 0, type 0 hdb: CHECK for good STATUS hdc: CHECK for good STATUS
But newer kernels stop at the autodetection part with an unable to find specified root device please specifiy with root= but it is correctly specified on the kernel command line as root=/dev/md1 (md0 is my home dir which is raid 1, md1 is root which is raid0)
Kernels have raid 0 and 1 compiled in aswell as reiserfs which is what i'm using.
Help! I need keep testing kernels but I can't continue with this fooked up raid..
BTW: This is related to this message: raidstart(pid 473) used deprecated START_ARRAY ioctl. This will not be supported beyond 2.6
Any help and comments are appreciated... A step by step howto do this would be helpfull.
Kind regards
Joel W
New Zealand
On Mon, 2004-10-25 at 15:30 +1300, Joel Wiramu Pauling wrote:
Since 2.6.8.1 + kernels, the kernel is unable to find my raid arrays.
On my system, my sata controller (I don't have any drives connected)
Joel Wiramu Pauling wrote: pre-2.6.8 took hda-hdd, so my pri-mas ide drive was hde. After 2.6.8, the sata would be sda-sdd I guess, and my ide drive is now hda. I suspect that is what happened to your drives.
I have searched and found that riadstart is deprecated and broken. (raidstart is what suse uses by default),
Not the problem here.
I have since installed upto date mdadm tools, and tried setting up a /etc/mdadm/mdadm.conf with my raid drives, and also reruning mkinitrd for my new kernels with root specified. But the kernel still refuses to boot my root partition.
Because I suspect your drive devices have changed.
I boot off a non raided partition sda1 and also have swap on a non raided partition sdb1.
Are these scsi disks? If they are sata, then before 2.6.8 they may have been hda1 and hdb1.
My raid setup is as bellow:
ARRAY /dev/md1 level=raid0 num-devices=2 UUID=da49e3b8:d0b65de4:7817e388:54c4980d devices=/dev/sda3,/dev/sdb3
I suspect this is the problem. With the new kernel, is the array STILL on sda3 and sdb3?
ARRAY /dev/md0 level=raid1 num-devices=2 UUID=3702dbfc:1572856f:4f673190:fc5212c4 devices=/dev/sda2,/dev/sdb2
Ditto
But newer kernels stop at the autodetection part with an unable to find specified root device please specifiy with root= but it is correctly specified on the kernel command line as root=/dev/md1 (md0 is my home dir which is raid 1, md1 is root which is raid0)
I suspect these are correct, but it is the config for your raid.
BTW: This is related to this message: raidstart(pid 473) used deprecated START_ARRAY ioctl. This will not be supported beyond 2.6
This is a warning message, not a failure message. Hope this helps you to track it down.
BTW, on mine I had to change fstab, meaning once you reconfig for 2.6.8 and >, you can't go back 'easily'. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
Devices are correct.. Trust me... I've been down this road before the change to sd device naming for sata devices came in the 2.6.7 and 2.6.8- pre series long ago... I've been getting that warning message for a long time. I'm guessing new kernels now don't allow deprecated behaviour... Why don't you try out 2.6.9(it's worth it for the atapi cd/dvd writing fixes alone) and you will encounter the same problem i'm guessing. On Mon, 2004-10-25 at 22:17 -0500, Joe Morris (NTM) wrote:
Joel Wiramu Pauling wrote:
On Mon, 2004-10-25 at 15:30 +1300, Joel Wiramu Pauling wrote:
Since 2.6.8.1 + kernels, the kernel is unable to find my raid arrays.
On my system, my sata controller (I don't have any drives connected) pre-2.6.8 took hda-hdd, so my pri-mas ide drive was hde. After 2.6.8, the sata would be sda-sdd I guess, and my ide drive is now hda. I suspect that is what happened to your drives.
I have searched and found that riadstart is deprecated and broken. (raidstart is what suse uses by default),
Not the problem here.
I have since installed upto date mdadm tools, and tried setting up a /etc/mdadm/mdadm.conf with my raid drives, and also reruning mkinitrd for my new kernels with root specified. But the kernel still refuses to boot my root partition.
Because I suspect your drive devices have changed.
I boot off a non raided partition sda1 and also have swap on a non raided partition sdb1.
Are these scsi disks? If they are sata, then before 2.6.8 they may have been hda1 and hdb1.
My raid setup is as bellow:
ARRAY /dev/md1 level=raid0 num-devices=2 UUID=da49e3b8:d0b65de4:7817e388:54c4980d devices=/dev/sda3,/dev/sdb3
I suspect this is the problem. With the new kernel, is the array STILL on sda3 and sdb3?
ARRAY /dev/md0 level=raid1 num-devices=2 UUID=3702dbfc:1572856f:4f673190:fc5212c4 devices=/dev/sda2,/dev/sdb2
Ditto
But newer kernels stop at the autodetection part with an unable to find specified root device please specifiy with root= but it is correctly specified on the kernel command line as root=/dev/md1 (md0 is my home dir which is raid 1, md1 is root which is raid0)
I suspect these are correct, but it is the config for your raid.
BTW: This is related to this message: raidstart(pid 473) used deprecated START_ARRAY ioctl. This will not be supported beyond 2.6
This is a warning message, not a failure message. Hope this helps you to track it down.
BTW, on mine I had to change fstab, meaning once you reconfig for 2.6.8 and >, you can't go back 'easily'.
-- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
participants (3)
-
Andreas Jaeger
-
Joe Morris (NTM)
-
Joel Wiramu Pauling