You are not logged in.
So I updated my kernel, and then when I rebooted the system didn't start at all.
initramfs gives error that mdadm can't find the devices for my 2 lvm raids. /dev/md0 /dev/md1
/dev/md1 consists of /dev/sdb1 /dev/sdc1 and /dev/md1 of /dev/sdd1 /dev/sde1. The drives are formated as reiserfs and /dev/sda is ext4.
I get 2 optiones, where's one is to reboot or the other to exit and resume normal boot. And if I exit I get a kernel-panic.
I have dm-mod & raid1 loaded as modules in /etc/rc.conf
I have MODULES="ext4 reiserfs ahci raid1" in /etc/mkinitcpio.conf and I tried with these hooks: HOOKS="base udev autodetect pata scsi sata filesystems lvm2 mdadm"
here is how my mdadm.conf looks like: ARRAY /dev/md0 level=raid1 num-devices=2 metadata=0.90 #UUID=77a8c1c0:b3d7e2f8:af9795ab:03d0a1cd
ARRAY /dev/md1 level=raid1 num-devices=2 metadata=0.90 #UUID=88b0efc9:7cb295b4:2a479691:6ac48900
any ideas?
Lenovo ThinkPad x61
Core2Duo 2ghz, 4gig ram, 16gig SSD.
Archlinux x64 + Fluxbox!
Offline
Perhaps you don't have the file /etc/mdadm.conf in your /etc directory.
This is required for mkinitcpio to obtain the raid array data for inclusion in initramfs.
If the file is missing, the latest kernel and its mkinitcpio re-invoke will not find the array and the kernel will not boot.
If this is the problem, a LiveCD boot and chrrot will aid in re-establishing the /etc/mdadm.conf file.
My experience with this was not as severe as yours since my raid0 is not used for boot but I did lose the raid0 because the /etc/mdadm.conf file had been deleted.
Good luck.........
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
My system recognizes the drives with uuid in raid0.
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
there is a /etc/mdadm.conf file, and as I rememberd when the kernel was updating it said that it used a custom mdadm.conf file. I've been trying to chroot my arch-root from a ubuntu-live-cd to run:
rm /etc/mdadm.conf
mdadm –D –-scan >> /etc/mdadm.conf
Bit it seems I'm just to noob to figure out how chroot works.
I mounted my / (/dev/sda3) to /media/ in the ubuntu-live-cd. then I tried to run chroot /media/ /bin/bash and it didn't work.
This is the complete mdadm output:
:: Loading Initramfs
mdadm: no devices found for /dev/md0
mdadm: no devices found for /dev/md1
read_urandom: /dev/urandom: open failed: No such file or directory
read_urandom: /dev/urandom: open failed: No such file or directory
Waiting 10 seconds for device /dev/sda3 ...
ERROR: Faild to pare block device ids for '/dev/sda3'
ERROR: Unable to detect or create root device '/dev/sda3'
You are being dropped to a recovery shell
Type ´reboot´ to rebot
Type ´exit´to try and continue booting
NOTE: klibc contains no 'ls' binary, use ´echo *´ instead
If the device '/dev/sda3' gets created while you are here, try adding ´rootdelay=10´ or higher to the kernel command-line
Last edited by bredin (2009-10-14 20:18:21)
Lenovo ThinkPad x61
Core2Duo 2ghz, 4gig ram, 16gig SSD.
Archlinux x64 + Fluxbox!
Offline
Perhaps you will find a good reference for chroot in the wiki called "kernel panics".
I found it useful........
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
I chrooted my / with the arch installation cd, I ran:
mdadm --assemble /dev/md0 /dev/sdb1 /dev/sdc1
mdadm --assemble /dev/md1 /dev/sdd1 /dev/sde1
and then I ran the:
rm /etc/mdadm.conf
mdadm –D –-scan >> /etc/mdadm.conf
and A new /etc/mdadm.conf was created. And it still does not work!
Last edited by bredin (2009-10-14 20:47:13)
Lenovo ThinkPad x61
Core2Duo 2ghz, 4gig ram, 16gig SSD.
Archlinux x64 + Fluxbox!
Offline
I actually went as far as:
root@ubuntu:/mnt# cat etc/mdadm.conf
ARRAY /dev/md0 level=raid1 num-devices=2 devices=/dev/sdb1,/dev/sdc1 metadata=0.90 UUID=77a8c1c0:b3d7e2f8:af9795ab:03d0a1cd
ARRAY /dev/md1 level=raid1 num-devices=2 devices=/dev/sdd1,/dev/sde1 metadata=0.90 UUID=88b0efc9:7cb295b4:2a479691:6ac48900
DEVICE /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1
Guess what, it doesn't work! If nobody have posted a fix for this till tomorrow morning will I re-install Vista.
Lenovo ThinkPad x61
Core2Duo 2ghz, 4gig ram, 16gig SSD.
Archlinux x64 + Fluxbox!
Offline
If the info you posted is actual code, there is a typo in the first line:
@ubuntu:/mnt# cat etc/mdadm.conf
ARRAY /dev/md0 level=raid1 num-devices=2 devices=/dev/sdb1,/dev/sdc1 metadata=0.90 UUID=77a8c1c0:b3d7e2f8:af9795ab:03d0a1cd
ARRAY /dev/md1 level=raid1 num-devices=2 devices=/dev/sdd1,/dev/sde1 metadata=0.90 UUID=88b0efc9:7cb295b4:2a479691:6ac48900
DEVICE /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1
The first line should show /etc/mdadm.conf..............
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
If the info you posted is actual code, there is a typo in the first line:
@ubuntu:/mnt# cat etc/mdadm.conf
ARRAY /dev/md0 level=raid1 num-devices=2 devices=/dev/sdb1,/dev/sdc1 metadata=0.90 UUID=77a8c1c0:b3d7e2f8:af9795ab:03d0a1cd
ARRAY /dev/md1 level=raid1 num-devices=2 devices=/dev/sdd1,/dev/sde1 metadata=0.90 UUID=88b0efc9:7cb295b4:2a479691:6ac48900
DEVICE /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1The first line should show /etc/mdadm.conf..............
Actually not. The / drive was mounted in /mnt and I was standing in /mnt. so instead of /mnt/etc/mdadm.conf i just went etc/mdadm.conf as /etc was a folder in the folder I was standing in.
Anyway, I solved the problem by installing Vista <3
Lenovo ThinkPad x61
Core2Duo 2ghz, 4gig ram, 16gig SSD.
Archlinux x64 + Fluxbox!
Offline