[I'm putting this back on list] On Mon,13.Jul.09, 13:46:15, Raphael Bossek wrote: > Hi Andrei, > > Is this also the case where hdparm -z force the kernel to reload the > partition table ? In my case the device nodes did not changen. Fdisk -l > confirm that all partitions are where they are expected. > > What a sence makes the /proc/partitions entry makes if it's not compleate > for fixed drives ? For a dynamicaly attached USB drive the partitions are > there. Will UUID really solve this issue ? I do not thing so, but where to > start searching ? Ok, scrap that idea. > What about udev who is responsible for the device nodes within the initrd > environment ? Who is really responsible to load the partitipn tables ? For > me it seams to be the kernel driver. Dmsg confirm that asumption. Why do I > get an "Devise or reasource is busy" ? Could you check if your initrd contains the correct module for your SATA chipset? If not adding it might solve your issue. > Regards, > Raphael [snip full quote of my mail] Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein)
Attachment:
signature.asc
Description: Digital signature