Changes between Version 3 and Version 4 of Linux/Ubuntu/HardyRAID5EncryptedLVM

07/07/08 18:31:05 (10 years ago)



  • Linux/Ubuntu/HardyRAID5EncryptedLVM

    v3 v4  
    512512Insert the stick into a USB port and let the system start. 
     514If using usplash you should see a message similar to "Success loading key-file from sde (casper-rw)" early in the boot process when `` locates the key-file. If it fails you'll see "FAILED to find suitable USB key-file ..." followed by "Try to enter the LUKS password:". At this point, if the device has a pass-phrase as well as a key-file you can type it instead of using the key-file. 
     516=== Debugging === 
     518If that fails you'll need to enable debugging within the script by changing: 
     527To do this the initial RAM disk image needs updating. That means the encrypted volume must be opened and mounted and the chroot environment recreated from the Live CD. Because that involves a lot of steps I put all the commands into a script. The script is attached to this article []. It will install the packages, configure and unlock the devices, recreate the chroot environment, download and install the latest version of `` attached to this article, then update the initial RAM disk image. 
     529Restart the system using the Live CD and open a terminal, then: 
     531sudo su 
     533chmod a+x 
     535The script requires the key-file name be assigned to the environmental variable KEYFILE: 
     540Now make the changes and update the initial RAM disk image: 
     542sed -i 's/^\(DEBUG=\)$FALSE/\1$TRUE/' /mnt/target/usr/local/sbin/ 
     543update-initramfs -u all 
     546You might also want to remove the "splash" option from the kernel command-line in the GRUB configuration (either in the file /boot/grub/menu.lst or by pressing Escape when GRUB is starting after a reboot to edit the menu directly). This will ensure that the large number of debug messages from the script are easily readable on the console, rather than scrolling up too fast in usplash. 
     548Now the system can be restarted and hopefully the messages will help identify the cause of the problem, and suggest a solution. 
     550Once the problem is fixed don't forget to change the debug setting back to $FALSE and update the initial RAM disk image. 
    514552== References ==