Re: boot timeout and fsck.ext3

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

 



On 15/08/2009 Rainer Maier wrote:
> Hi,
> on my Debian installation I attached the noauto in /etc/crypttab:
> tresor  /dev/sda2       none    luks,check=ext2,retry=5,timeout=5,noauto
> 
> and in fstab I only left:
> /dev/mapper/tresor  /tresor         auto    defaults                   0       0
> # /dev/sda2           /tresor         ext3    defaults,errors=remount-ro 0
> 
> Since only the /dev/sdb system is encrypted and not the /dev/hda or
> /dev/sda everything starts ok.
> 
> When I then use cryptdisks_start is seems equal to:
> cryptsetup luksOpen /dev/sda2 tresor
> but I have to mount the system manually:
> mount /dev/mapper/tresor /tresor
> 
> Is that behaviour normal or do I have to change some settings to make
> cryptdisks_start even mount the disks ?

no, this is normal behaviour.

greetings,
 jonas

Attachment: signature.asc
Description: Digital signature

_______________________________________________
dm-crypt mailing list
dm-crypt@xxxxxxxx
http://www.saout.de/mailman/listinfo/dm-crypt

[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