Re: kernel-2.6.17-1.2145_FC5 still won't boot Promise Raid 0 LVM Set

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

Andrew Gray írta:
Under kernel-2.6.16-1.2133 my system boots a raid 0 volume on a Promise
PDC 20376 that looks like:-

[root@www ~]# dmraid -s
*** Active Set
name   : pdc_fiagfhab
size   : 625163264
stride : 128
type   : stripe
status : ok
subsets: 0
devs   : 2
spares : 0

All FC5 kernel-2.6.17's including 2145  won't boot on my system. The
boot volume is a raid
0 array on a Promise PDC20376 (FastTrak) :-

#Loading jbd.ko module
#Loading ext3.ko module
#Locading dm-mod.ko module
#device-mapper: 4.6.0-ioctl (2006-02-17) initialised:
dm-devel@xxxxxxxxxx
#Loading dm-mirror.ko module
#Loading dm-zero.ko module
#Loading dm-snapshot.ko module #Making device-mapper control mode
Kernel 2.6.17-2145_FC5 Then hangs !!

I am presuming kernel-2.6.17 kernels doesn't boot because it is not
recognising my LVM volume setup with 2.6.16 kernel
using /dev/mapper/pdc_fiagfhabp2 on the Promise PDC20376. Maybe it has
changed the device mapper name for this device? :-

I don't know, I may have the same problem.
I upgraded to RawHide from my FC5/x86-64
about the same time as kernel-2.6.17-1.2139_FC5
came out so I don't know which change caused it.
Problem is: I have a secondary SATA harddisk
hanging from the onboard Promise controller.
Not it doesn't mount under /home1. I straced
mount and the mount syscall returns EBUSY.
sata_promise has refcount=1 according to lsmod.
There is no suspicious message in the logs.
The primary PATA hdd still works, it's attached
to the VIA controller. MSI K8T Neo motherboard.

Best regards,
Zoltán Böszörményi

--
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list

[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]