-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 В Tue, 26 Nov 2013 20:12:01 +0100 (CET) "Carlos E. R." <robin.listas@telefonica.net> пишет:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Content-ID: <alpine.LNX.2.00.1311262010350.12194@Telcontar.valinor>
On Tuesday, 2013-11-26 at 14:41 +0100, Carlos E. R. wrote:
On 2013-11-26 14:00, Fr David Ousley wrote:
kernel (hd0,4)/vmlinuz-3.7.10-1.1-desktop root=/dev/disk/by-id/raid/pdc_djiegecc_part7 resume=/dev/disk/by-id/raid/pdc_djiegecc_part6 splash=silent quiet showopts
I did not notice before that raid was involved. In that case, View this thread: <http://forums.opensuse.org/showthread.php?t=492403>
You replied in private. Please reply to the list. I'm copying your post here so that others can comment.
El 2013-11-26 a las 09:02 -0500, Fr David Ousley escribió:
On Tue, 26 Nov 2013 08:41:11 -0500, Carlos E. R. <> wrote:
I did not notice before that raid was involved. In that case, View this thread: <http://forums.opensuse.org/showthread.php?t=492403>
This thread seems to deal with LVM (which is not involved here -- the partitions are ex4), and software RAID -- my set up is hardware (BIOS). Unless I'm missing something (entirely p;ossible!)
It is about LVM on top of raid, and it is the raid that is the problem.
What makes you think so? Even if this is raid, error comes from grub which happens way before anything described in above thread.
It also points to a pair of bugzillas you should read.
Another similar thread:
View this thread: http://forums.opensuse.org/showthread.php?t=491264
fdisk -l output:
Disk /dev/sda: 30.0 GB, 30016659456 bytes 255 heads, 63 sectors/track, 3649 cylinders, total 58626288 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x10ce7af1
Device Boot Start End Blocks Id System /dev/sda1 * 2048 206847 102400 7 HPFS/NTFS/exFAT /dev/sda2 206848 58621951 29207552 7 HPFS/NTFS/exFAT
If what is /dev/sda in OS is indeed hd0 in grub it perfectly explains why partition 5 is not found during boot ...
I notice that no partition is marked as autoraid type, thus the initial booter might not activate it soon enough.
This is fake raid which has nothing to do with Linux MD (and it is assembled using dmraid). Now I do expect problems if kernel is loaded as mdadm has priority over dmraid by default and there was at least one report that this caused failure during boot. But again, this all happens after kernel is booted - OP is not as far. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlKU9XsACgkQR6LMutpd94xq2wCfTUvGYjoPMpgQ6MfNPpGQ9dM3 /84AoKFrJr281sr+WHgXEWZPHnpYEmOw =hWdc -----END PGP SIGNATURE----- N�����r��y隊Z)z{.�ﮞ˛���m�)z{.��+�: �{Zr�az�'z��j)h���Ǿ� ޮ�^�ˬz��