You are not logged in.
Have prepared a two -drive raid0 bootable Compact Flash system.
When first assembled it was in Kernel26v39 and booted into operating system and performed well.
I have upgraded a pair of CF cards to linux 3.1.5-1 and they no longer can boot into an operating system.
The boot sequence performs :
decompressing linux ...parsingELF....done
Booting the kernel...
starting udevd
running HOOK [udevd]
Triggering uevents....done
Running HOOK [mdadm]
Waiting 10 seconds for /dev/disk/byuuid...................................................
ERROR: unable to determine major-minor..............................................
ramfs/#So the root device, which is /dev/md0, is not recognized.
I have performed ls dev at the ramfs prompt and /dev/md0 is not listed.
I have performed blkid at the ramfs prompt and the /dev/md0 UUID is not listed.
However, I can boot into HDD linux3.1.5-1 and find /dev/md0 in ls dev and also find /dev/md0 listed in blkid.
Perhaps the Linux kernel is missing a parameter which enables mdadm via /etc/mdadm.conf or mdadm does not correctly generate the uuid for /dev/md0.
Since the device /dev/md0 is actually present in linux3.1.5-1 when booted in HDD, it is obviously valid.
The grub in use for the failed boot is grub1.99. Partitioned boot is utilized and may be part of the problem although it seems not since the system begins loading after the grub prompt of ARCH LINUX...ARCH LINUX_FALLBACK.
Therefore the difficulty is inherent in the kernel/udev/mdadm interface.
I enjoy very much the raid0 bootable system performance with CF cards and would like to stay up to latest kernel if that be possible.
Modern arch linux can do anything?
The initramfs items have been included in the grub area. Perhaps other items need attention as well?
Last edited by lilsirecho (2012-01-04 07:52:57)
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
Attempting to find a solution, I proceeded to modify grub at the prompt.
Changed :
set root = (hd0,1)....changed to (hd1,1)
linux ....added ....root=/dev/md0The system booted into linux3.1.6-1 xfce4 Desktop.
Success!
EDIT: hdparm results.......
sh-4.2# hdparm -t /dev/md0
/dev/md0:
Timing buffered disk reads: 534 MB in 3.01 seconds = 177.61 MB/sec
sh-4.2# hdparm -t /dev/md0
/dev/md0:
Timing buffered disk reads: 542 MB in 3.00 seconds = 180.46 MB/sec
sh-4.2# hdparm -t /dev/md0
/dev/md0:
Timing buffered disk reads: 540 MB in 3.01 seconds = 179.46 MB/sec
sh-4.2# System is x86_64 and boots to xfce4 Desktop in nine seconds.......
CF cards are maxell 400x 16GB and /dev/md0 is 29GB , root ext3 fs.
Last edited by lilsirecho (2012-01-04 09:40:14)
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
Now I need a method of changing grub to reflect the changes I pasted into the prompt.
I am advised not to edit the grub.cfg file as it is auto-generated.
Any advice on this point?
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
No mistake...
sh-4.2# uname -a
Linux n6re 3.1.6-1-ARCH #1 SMP PREEMPT Thu Dec 22 09:11:48 CET 2011 x86_64 Intel(R) Pentium(R) D CPU 2.80GHz GenuineIntel GNU/Linux
sh-4.2# Need to correct grub.cfg in partition.
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
Despite running e2fsck on the raid0 /dev/md0 with no errors, it contained a corrupted /etc/fstab file.
After correcting that problem, the raid0 is able to reach desktop booting from ...set root=(hd0,1) and it recognizes the /dev/md0. This is in latest 3.1.8-1 linux kernel.
Why e2fsck would pass on a defective fstab is a mystery.
I am hopeful this closes the postings on raid0 with a successful boot in the next upgrade.
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