Debian Installation :: Encrypted LVM Install - No Root File System Detected
Jun 1, 2013
I'm a long time user of Debian, but I'm having trouble with my partitioning process. Here is where I currently stand:
I am installing the latest Wheezy build. I am trying to install debian with an encrypted LVM that spans two hard disks.
My partitioning layout is as:
I then added partitions 1, 2 and 3 to a physical volume group. I then took that physical volume group and added it to a logical volume. Then I encrypted the logical volume, leaving the /boot partition untouched. I was under the assumption that the only partition the system needed free to reach the loading of the LVM is the /boot partition, as it holds the files necessary for booting. But when I attempt to finalize the disk, it gives an error stating, "No root file system detected". That would be an issue as it is currently sitting inside the encrypted LV. Am I wrong in including the root partition in the encrypted LV?
What is the best way of having as little of my file system non-encrypted as possible while still allowing a proper boot?
Centos 5.3 includes Ext4 and improved support for encrypted file systems but it appears to be aimed at laptop/desktop systems, in that a password must be entered at boot time.
Is it possible to have a server with an encrypted root file system boot up without entering a password?
Mandos will do it... http://wiki.fukt.bsnet.se/wiki/Mandos ...by serving up the password from another server... http://packages.debian.org/squeeze/mandos ...to a client loaded into the initial RAM disk environment... http://packages.debian.org/squeeze/mandos-client ...but it's not available on CentOS, and is only in Debian unstable.
Is there a similar (or any) solution for CentOS?
In particular, I'm envisaging encrypted virtual machines being served passwords from their virtual host.
Alternatively, the data that *really* needs to be protected could be encrypted while the system core remains unencrypted. But then the keys to decrypt the file system must be stored in the unencrypted portion, so this is not an effective method.
After a fresh install of Debian I came across an error Im hoping you guys can help me with. Ive searched for the error and it appears there are multiple reasons that could be causing it. To compound the problem, Im at work so I dont have the specific error messages....so I just installed Lenny (standard install, no desktop) using a USB installer and everything went very smooth. On first boot, the system paused while waiting for the root file system. After a minute or two it just errored out complaining it could not find the root file system and put me at a (vmlinuz) prompt?My guess is that I need to go into my bios and change my boot priority.. but again, thats just a guess.
I just installed 11.4 and I get an error when I try to boot, "fsck failed for at least one filesystem". It's referring to sdc2, which is my /. This drive is a 1.5gb SATA drive, and it may be that this drive is very slow to initialize. I used to have a problem in Windows where this same drive wouldn't be detected after waking from sleep, so I had to apply a hotfix patch.
I tried manually fsck-ing, but the drive isn't detected at all. Maybe some way I can make it wait longer for the drive?
The most confusing line is "Warning: cryptsetup is unavailable" - I took a look into the scripts, it checks if cryptsetup and askpass is executable if not this message. But:
I mounted the hdd-img file local and took a look: all binaries there.
So I tried a lot getting it working on boot time. I tried it with live-tools from testing, from wheezy and last but not least installed and pinned live-tools to unstable. Always the same. askpass isn't executable on boot time before mounting the persistence.
and yes, cryptsetup is inside package-list (otherwise live-persistence from within running machine with crypted partitions would not work). Live tools I used for last run is 4.0.3-1 from unstable, before tried with 4.0.2-1 from testing.
After my NVIDIA card died I decided it was time to buy an AMD card again (R9 270X), but I didn't think AMD drivers were such a pain in Linux as people said. Of course, in some distros anyway. On Arch, for example, there's no official release because Arch's developers would have to hold Xorg in order to make a closed-source driver available, because AMD's pace isn't in pair with Linux. So in order to install AMD's drivers on Arch I must rely on some guy's unnoficial repositories, but that isn't the whole problem. Even though I'm cool with adding repos and downgrading Xorg, I'm not cool with it not working for a lot of apps, so that's where I decided to try a few distros. Manjaro is a no-go because it installs Flash as default. openSUSE although is a very good distro, is a complete mess when it comes to repositories, specially multimedia ones. Ubuntu/Mint are also a no-go, Ubuntu because after 12.04 they have a spyware by default, and Mint because it contains non-free stuff by default.
So here I come! I ran Debian in the past for a long time (aside from a breaf period last year) and it was lovely, I could easily set up a custom encrypted install, but now I don't remember how to, and it's killing me. I don't like how the installer doesn't show the partitions size as they actually are, and I don't like how the automated encrypted LVM setup doesn't let me chose the encryption algorithm or the timeframe between each passphrase attempt. That's why I must create my install, and here's what I used to do on Arch (the part that really matters), converted to what I use on Debian:
Code: Select all# modprobe dm-mod
(create one 1GB partition for /boot, unencrypted ; create another big 930 GB formatted as "8e" - LVM - on dev/sda2) Code: Select all# fdisk /dev/sda (chose my ciphers and iter time) Code: Select all# cryptsetup -c twofish-xts-plain64 -y-s 512 --iter-time 5000 luksFormat /dev/sda2 (open the luks container on "sda2_crypt")
After this is done, I go to the "partition disks" page where I select each partition/volume to it's correct destination. I then proceed to installing the base system, configuring apt, and all that. Now, before I install Grub I used to execute the following commands on shell:
Code: Select all # nano /etc/crypttab
I used to put something there, but I don't remember what exactly. It's been a long time since I used Debian for long! But here's what I put there:
I just installed Debian Testing on an encrypted partition (using the encryption feature in the installer). Problem is when I boot I enter the passphrase and then Debian starts to load a bit and then it stops and won't move again. During a normal boot the boot stops after : EDAC sbridge : Couldn't find mci handler Then do a recovery mode boot from grub loader so more information is displayed during the boot time and it stops after : [12.513770] fb: switching to nouveaufb from simple it stops there I can't type anything, I can reboot the computer with ctrl+alt+del tho
I was booting just fine in a previous installation on a MBR-partitioned disk (now it's GPT-partitioned). I have to add that during installation I added a second encrypted volume on a HDD (while / is on a SSD) that mounts to /data. When few days ago I installed it on the MBR-partitioned disk it asked me for the /data passphrase pretty fast, now it just seems to boot and asks me only one passphrase until it freezes.
I have built a kernel with a ramdisk(ramdisk.image.gz) included. Also in the kernel command line I specified root=/dev/ram0. I am trying to use this ramdisk to load a loopback file as the root filesystem off a fat partition. This is /sbin/init from the ramdisk.
#!/bin/sh mount -n -t msdos /dev/mmcblk0p1 /mnt losetup /dev/loop0 /mnt/linux/linuxdsk.img mount -t ext2 /dev/loop0 /mnt2
The problem is both umount and blockdev report "device is busy". I want to free up this RAM any suggestions?
For my project, it's absolutely necessary to have a read-only root partition system. I have a writable /opt/project partition.But, I also need to start x server. startx This tries to write to some temporary files and fails as / is readonly. Is there any how-to on how to move this temporary files to the writable portions of the file system.
I would like to start off by saying this: I am very new to Linux, and this is my first time installing it, therefor I am having some very newb-like issues. Please bear with me.I am currently at step five of the installation process of Ubuntu, and I clicked on the partition which I have set aside to install Ubuntu onto, but when I proceed by hitting forward, I get the following error message:"No root file system is defined.Please correct this from the partitioning menu."My question to the community is, how would I correct that? How do I turn my 20GB partition into the root file system?P.S. I searched the forum for this issue, and being that it sounds so simple, yet I found nothing about it being previously asked, I feel sort of dumb....
When I tried to install 10.10 'side by side' with 10.04 and OpenArtist for triple booting I get the messageQuote:No root file system is defined. Please correct this from the partitioning menu.I don't have the screen in front of me now but what5 does it want me to do and how do I do it?
Recently set up root encryption with a couple of LVM volumes inside one LUKS volume, and I am just a little confused as to how I would go about getting it to automatically unlock using a keyfile stored on a USB flash drive, I presume I would have to put the drive in the fstab inside my initramfs (if there is one), and add a hook for USB device support.
But I digress, essentially, I want to know what I have to do to enable my LUKS volume (containing all of my partitions sans /boot) to unlock using a keyfile stored on a USB flash drive, rather than a manually entered passphrase.
I tried to install Debian 3 at my pc, and while it worked, it only installed the basic system. When it goes trying to install the "everyday-use" packages it cames with this message:Some error ocurred while unpacking. I am going tp configure the packages that were installed. This may result in duplicate errors or erros caused by missing dependencies. This is ok, only the erros above this message are important. Please fix them and Install again
I am pondering a reinstall of a freshly installed Ubuntu; I may or may not take that drastic step.However, I have partitioned my drive to include a 16-GB partition labelled "Ubuntu-tmp", in my case /dev/sda7, with the intent of mounting that file system as /tmp. Depending on how I decide to go about the reinstall I need an answer to these questions:If I reinstall: Is it possible to designate /dev/sda7 to mount as /tmp during the installation process?If I cannot designate the mounts at install time, or if I opt not to reinstall: I can't really empty the /tmp directory in the root in order to properly use it as a mount point for [the file system on] /dev/sda7; many files in there are still in use by running processes. So how can I clear the /-mounted /tmp directory and assign it to /dev/sda7?
I have attached a screen shot of gparted to illustrate my layout scheme.The gparted manual suggests I select the partition, click [Partition]->[Mount]. Of course, my gparted drops a menu with [Mount] is absent and an [Unmount] option is greyed out.This raises a question of how I am going to mount /users and /var in their intended file systems (/dev/sda8 and /dev/sda9, respectively), because the [partition] menu looks the same for these partitions as well.
I was trying to install Ubuntu desktop and laptop edition on a Sony Vaio netbook from a USB drive, but after I select the entire disk to be used and hit enter I get this message No root file system is defined. correct this from the partitioning menu. If I try to start windows I just get s black screen.
When I get to installation step "Allocate drive space" I get this message, "No root file system is defined. correct this from the partitioning menu." What is the source of this error and what do I need to do to correct it? I don't see a partition menu other than a choice of using the whole drive or a partition? Below are the choices that I have made. Specify partitions manually (advanced) Allocate drive space Choice are device (/dev/sda4) Type ((ext3) size) Mount Point (no choices offered) Size (42088 mb) used (670 mb) boot looder is sda Windows 7 ext3 42088 MB I am installing Ubuntu 10.1 on a seperate partition. Windows 7 is on another partition. The machine is an ASUS A52F Laptop
i have one partition of 45 Gb...and other of 250 Gb in which windows 7 has been installed..i booted from ubuntu 10.10 CD and then i chose the installation option on desktop...but when i selected the partition of 45GB for installation..the error message said that "there is no root file system on the drive, set it from partition options"..
I've been trying to install ubuntu 11.04 64 bit on a partition next o windows 7 64 bit.When I use the default option (no matter how large I make the partition) I get the error message that not enough space could be created. I read this could e solved by defragmenting the hard drive which I did, but the problem persists.I next tried to partition manually but go the error message that there was "No root file system is de or something similar
standard Linux installation utilities split the root file-system and the home file-system on two separate but relatively equal-sized partitions? For example, when I put fedora on an 80GB disk, it automatically gave the root file-system 32GB and home 30GB and the swap 8GB of space. However, since my home file-system has a directory with 28GB of files in it, why is my root file-system reading 100% usage? Is the home FS overlaid on top of the root FS? Is there an advantage to doing this? I just made a boot partition (50mb or so), a root partition (90% of the disk space) and a swap (4%-5% disk space).
Everything works fine and the encryption works with no problem. However, as a friend pointed out to me, if you partition as follows:
Code: /boot - 100MB/ - Rest of filesystem - Encrypted You are not able to boot the system when doing a minimal install. Meaning: you get up to the point to where you need to enter your password to decrypt the filesystem, and then nothing but..., well, nothing. However, and here it gets interesting, if you use the same partition layout, and you install the "Graphical Desktop", everything works fine. As I can not understand why this happens, I am currently testing a partition setup like so:
Code: /boot - 100MB LVM - Encrypted - / - Rest of filesystem Just to see if that works.
Anyhow: to make a long story short: It seems that the minimal install "forgets" to add some packages which are needed to decrypt the filesystem. Does anyone know which package this could be or why this occurs, so it can be added as part of the minimal install?
I recently recieved Ubuntu 9.04 Desktop Edition CD-ROM through snail-mail after requesting a copy online and I want to install it on my laptop, although I wish to keep Vista which is on it now.
My laptop has a 250GB hard drive. Although when in Vista this is represented as two separate drives each of 110GB, (C or ACER and (D or DATA.
Using the CD, I start the installation and everything is straightforward and self explanatory, until I get stuck at step 4...
Where I am told by the ubuntu installer: "This computer has several operating systems on it." (I'm confused now, I thought it had one, Vista.)
Beneath I am shown a bar representing my disk space which is divided between...
I am given the option to use the entire disk: 'SCSI1 (0,0,0)(sda) - 250.1GB ATA WDC WD2500BEVT - 2', (and from the mention of 250BG in the name I'm assuming this is one disk and not the two separate drives named C: & D: in Vista.) ...along with a warning - "This will delete Windows Vista (loader), Windows Vista (loader), Microsoft Windows XP Embedded and install Ubuntu 9.04". (The aforementioned "several operating systems" obviously.)
But I wish to keep Vista, so I select the option to "specify partitions manually" and am brought to a screen named 'Prepare Partitions', where there is a table somewhat like this:
I am then given the option for "New partition table", and if I select any of the bottom four devices I can 'edit partition' or 'delete partition'.
Selecting the device /dev/sda3 (because it is the one that I'm guessing has no operating system data on it, judging by the previous screen) and choosing 'edit partition', allows me the following options...to create a new partition size, to select what I want to use the partition as. (There are also two options for formating a partition, which is a checkbox, and Mount point. These are both greyed out.)
When I look at the 'Use as:' option, within 'edit partition', the drop down box allows me to use the partition in the following ways: - do not use the partition - swap area - NTFS - FAT 32 file system - FAT16 file system - XFS journaling file system - ReiserFS journaling file system - Ext2 file system - Ext4 journaling file system - Ext3 journaling file system
I am getting an error message at step 5 of 8 in the installation process. I am using Ubuntu LiveCD. The caption of the error is 'No root file system' and the message itself says 'No root file system is defined.Please correct this from the partitioning menu.' I enclose a screenshot of this. I had also problems with booting Ubuntu and Windows after installing Ubuntu to an external hard disk so I probably have to also create a new boot menu (may be it is differently called, 'grub' possibly, I am not really sure).
if this is an error that has already been solved, but I am running Windows 7, and when I finish installing Wubi in Windows, it asks me to reboot. I select Ubuntu and it gives me the error: "No root file system is defined. Please correct this list from the partition menu." I can't get past this error.