Mailinglist Archive: opensuse (1473 mails)

< Previous Next >
Re: [opensuse] UUID=>0x and LVM
  • From: "Boyd Stephen Smith Jr." <bss@xxxxxxxxxxxxxxxxx>
  • Date: Fri, 19 Jun 2009 11:46:21 -0500
  • Message-id: <200906191146.31297.bss@xxxxxxxxxxxxxxxxx>
In <7DEBCCBF-A797-45BD-B953-CCD82E03C2CE@xxxxxxxxxxxxx>, Philip Mötteli
wrote:
Am 18.06.2009 um 17:15 schrieb Boyd Stephen Smith Jr.:
If the device shows up when booting from the GParted LiveCD and does
show up
when the system boots normally, you are most likely missing a kernel
module.

Boot into each and get a list of loaded modules. (Either lsmod or cat
/proc/modules.)

RescueCD:

[125 modules]

A lot of those are disk-oriented. Anything with "ide", "ata", "sas", or
"scsi" in the name should be the first ones you look for. You might also
need ones with "raid" in the name.

Boot-system:

[21 modules]

This is definitely not enough. You are missing a *lot* of modules. 'lsmod
| wc -l' on my laptop gives 128 modules. 'modprobe -l | wc -l' on that same
laptop shows 2085 modules available.

You should have at least one loaded during the GParted
LiveCD boot that is not loaded in the normal boot.

Many, many: 125 in the RescueCD and 21 in the system boot.
In addition to that, most of the modules, loaded by the system boot,
are not loaded by the RescueCD:

Don't worry about modules that are loaded by the real system but not by the
RescueCD. You aren't missing things in the RescueCD, so what it is not
loading doesn't matter.

I did a 'modprobe -l' and loaded all those available, that haven't
been loaded so far:

modprobe -l does actually load any modules.

ohci-hcd
usbhid

Neither one of these will make ide/pata/sata/sas/scsi devices appear.

No sdc appears in '/dev'. Is there a way to force this?

How do you propose to "force" the kernel to talk to a device it cannot
detect? You can create /dev/sdc with mknod, but it won't *work* unless the
kernel detects the device. Once the kernel detects the device, it will
communicate with udev, and udev will perform the mknod automatically.

Make sure you have all the modules you need installed. On my laptop, they
are coming from 3 packages: kernel-default, kernel-default-base, and kernel-
default-extra.

Once you have that done, you could simply write a shell loop to load each
module looking from one that makes /dev/sdc appear. Something like this (as
root) might work:
modprobe -l |
grep -E '(ide|ata|sas|scsi|raid)' |
while read ko; do
kof=$(basename "$ko") &&
module=${kof%%.ko} &&
modprobe "$module" &&
if [ -r /dev/sdc ]; then
echo "Winner! Module is: $module"
break
else
modprobe -r "$module" ||
echo "Sorry, couldn't remove module $module."
fi
done
--
Boyd Stephen Smith Jr. ,= ,-_-. =.
bss@xxxxxxxxxxxxxxxxx ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.net/ \_/

< Previous Next >
Follow Ups