On 2009/03/03 03:25 (GMT+0100) Carlos E. R. composed:

On Monday, 2009-03-02 at 17:14 -0500, Felix Miata wrote:

...

...

During 11.1 devel via https://bugzilla.novell.com/show_bug.cgi?id=397816 I setup device mapper on one system in order to access all actual partitions while using ata_piix driver. Now on that system I have a 2.6.29 kernel, so no longer need dm_linear. So far, I've had no luck reversing the process. Neither subject command seems to produce any impact. I ran both kpartx -d /dev/sda and activate_device_mapper -d /dev/sda before running mkinitrd, and still the resulting initrd features dm_linear and kpartx. /etc/udev/rules.d/dm_linear.rules did get a fresh write, while /etc/udev/rules.d/70-kpartx.rules did not. I blacklisted dm_linear & kpartx in /etc/modprobe.conf.local too, but that didn't help either. Short of a fresh install, how do I eliminate them, and go back to mounting directly to /dev/sda* devices instead of /dev/dm-* devices?

I have no idea, but you could test renaming those modules, so that they can not be loaded. The blacklist does not work if another module explicitly wants to load a blacklisted module.

Renaming didn't result in any progress. :-(

At least you should get an error, and that error might point to what wants to load them :-?

Another idea. How about checking your fstab does refer to /dev/sdX?

All native partitions are LABEL=. I've made a lot of progress. I'm now running 2.6.29-rc5-1 on the ata_piix driver, but I still get "waiting for device /dev/root to appear ... could not find /dev/root ... want to fall back to /dev/hda10" during booting if I used my traditional Grub stanza with root=LABEL= instead of root=/dev/Xda10. While booted to an old kernel using piix instead of device mapper, I did: activate_device_mapper -d /dev/sda kpartx -d /dev/sda rpm -e --nodeps kpartx rpm -e --nodeps dmraid rm /dev/device-mapper rm /dev/mapper/control mv /etc/udev/rules.d/dm_linear.rules dm0_linear.rule0s mv /lib/modules/....29...-pae/kernel/drivers/md to m000d mkinitrd -v -k -i on .29 kernel Booting that got me again "waiting for device /dev/root to appear ... could not find /dev/root ... want to fall back to /dev/hda10", but then it couldn't find /dev/hda10. Next I updated to 2.6.27.19-3.2-pae on a different 11.1 system running on ata_piix, installed that kernel on this system, copied the initrd from the other system, and tried again. Again on the freshly generated initrd I got "waiting for device /dev/root to appear ... could not find /dev/root ... want to fall back to /dev/hda10", which it couldn't find. Then I tried the copied initrd, which got me "waiting for device /dev/root to appear ... could not find /dev/root ... want to fall back to /dev/sda10". That succeeded. After I did that, I did mkinitrd on the .29 kernel, which got me "waiting for device /dev/root to appear ... could not find /dev/root ... want to fall back to /dev/dev/disk/by-id/...part10", which succeeded. I tried zypper rm dmraid kpartx before doing rpm -e on kpartx and dmraid, but zypper then wanted to remove: autoyast2-installation multipath-tools yast2-add-on yast2-backup yast2-bootloader yast2-installation yast2-repair yast2-restore yast2-storage yast2-tune yast2-update in addition to dmraid and kpartx. After 'zypper in kpartx dmraid', activate_dm_linear -d /dev/sda returned nothing, and kpartx -d /dev/sda returned: /proc/misc: No entry for device-mapper found Is device-mapper driver missing from kernel? device-mapper: version ioctl failed: Inappropriate ioctl for device device-mapper-prerequisites not met Then I tried on Grub kernel line replacing root=LABEL=S16A-10factory with root=/dev/sda10, and booting proceeded normally. This looks like https://bugzilla.novell.com/show_bug.cgi?id=300550 has resurfaced. AFAICT, I might still need to get dm_linear & kpartx left out of the initrd for .29. Is this true? Any other suggestions? -- "The plans of the diligent lead to profit as surely as haste leads to poverty." Proverbs 21:5 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org