Re: Re: cryptsetup: Source device /dev/sda7 not found

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

 



On Wed, Jul 15, 2009 at 07:01:52PM +0200, davide wrote:
> Il Mon, 13 Jul 2009 18:27:40 +0200, Arno Wagner ha scritto:
> 
> > It may be
> > possible to force the USB device to be sda with a kernel option.
> 
> Arno, do you mean the map option for the GRUB bootloader?
> I tried it and it doesn't work.
> If you have any hint...

No. There are two (atually three) different mappings her.
1. What grub uses
   - Bios numbering
   - ... possiblu overidden by /boot/grub/devices.map
     which is for installation only, as far as I understand this
2. What your booted kernel does.  
   In order to find the assignment, you neet to read the 
   boot messages.
   This is relatively constant from one kernel to the next in
   my experience, but better not depend on it.

You need to understand that Gurb really passes nothing of its
own disk detection to the kernel. It just loads the kernel,
gives it the configured kernel parameters (i.e. those stated
in /boot/grub/menu.lst) and then starts the kernel. The kernel
does its own, fresh  hardware detection after this.

Here is an example from my desktop with two disks:

...
scsi 0:0:0:0: Direct-Access     ATA      Hitachi HDP72502 GM2O PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 488397168 512-byte hardware sectors: (250 GB/232 GiB)
...
scsi 1:0:0:0: Direct-Access     ATA      SAMSUNG SP2504C  VT10 PQ: 0 ANSI: 5
sd 1:0:0:0: [sdb] 488397168 512-byte hardware sectors: (250 GB/232 GiB)
...

This is with libata as SATA driver (the standard today). As you can
see the Hitachi gets sda and the Samsung gets sdb. Looking for something
like this in your bootup messages (scroll up with shift-pgup) should
tell you what device is assigned to your disk.


If you look into the kernel sources documentation in (typically)
/usr/src/linux/Documentation/ and consult the file
kernel-parameters.txt you find the possible "boot options"
for the kernel. Grub can pass these along. However I admit
I did never try to rename a disk this way and I did not find
a matching parameter.

Better find the assigned device and change your setup script.

Arno



-- 
Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@xxxxxxxxxxx 
GnuPG:  ID: 1E25338F  FP: 0C30 5782 9D93 F785 E79C  0296 797F 6B50 1E25 338F
----
Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans

If it's in the news, don't worry about it.  The very definition of 
"news" is "something that hardly ever happens." -- Bruce Schneier 

---------------------------------------------------------------------
dm-crypt mailing list - http://www.saout.de/misc/dm-crypt/
To unsubscribe, e-mail: dm-crypt-unsubscribe@xxxxxxxx
For additional commands, e-mail: dm-crypt-help@xxxxxxxx


[Index of Archives]     [Device Mapper Devel]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux