Debian encrypted LVM disappears every time on sda when I install any other also encrypted Linux distro on sdb.
How can I set up Debian that way that it wouldn't disappear or how can I recover it form UEFI?
On a new Lenovo Thinkpad T450s, I encounter the following issue: The USB drive containing live CD image ("burned" to the USB using mkusb tool --> which in turn uses dd) cannot be booted from the UEFI boot loader. I have to reconfigure the hardware (BIOS) setup to support both UEFI & legacy system, and with first boot priority given to legacy (BIOS-style) booting. But if I do this, I don't see the UEFI system in the /sys/firmware/uefi directory. I am using the 64-bit live CD image (debian-live-8.0.0-amd64-xfce-desktop.iso).
This is my goal: to boot the live USB from UEFI, so that I can install it in a form that is UEFI-bootable.
I have a Debian testing system on a laptop that used to have Windows 8 on it. I kept the EFI boatloader and its partition, but now every time the system boots, it first tries to boot into Windows (which isn't there anymore). Removing /boot/efi/EFI/Microsoft just leads to an error message when booting, with some component of Windows still trying to load and not finding those files.
The workaround for now is to go into the UEFI boot menu on every boot and selecting the "debian" entry, which works but is a bit cumbersome.How can I get rid of the Microsoft loader completely? I find a lot about repairing or re-adding the Windows bootloader, but nothing about removing it.
My version of Squeeze was about half a year old when I updated/upgraded it just now. As part of the (longish) process I was advised to run apt-get autoremove, which removed what looked like a stunning amount of material. As another part I noticed a huge number of error messages about nonexistent locale files (I think) whizzing by.
Well, the result has various cosmetic changes and no doubt fewer bugs, but it doesn't have WLAN. I used to see an icon at the top right like two tadpoles chasing each other, turning into a set of green (if I was lucky) or grey (if not) bars. No longer. No tadpoles, no bars, no error message, nothing.
This very recent thread ("Just isntall debian 6.0, wired networking ok but no wireless") looks helpful. However, I don't know what WLAN hardware I've got or how to get a text dump of this kind of thing. 4D696B65 kindly points the person who asked to wiki.debian.org/ipw2200. I don't know whether I have any of these "Intel PRO/Wireless 2100, 2200 and 2915 devices" but I'm encouraged to read there that [the file] is now also available in the nonfree-firmware tarball which we build regularly on cdimage.debian.org. Supply this blob on a CD/floppy/USB drive etc. and d-i will do the right thing. I don't know what either "blob" or "d-i" means, but I was rather hoping that some software or other would look at the hardware, look at the available firmware, and install accordingly (as happened months ago). So got the (small) file; I opened it up; I copied the contents to a CD (even though it's not an ISO). But apt-cdrom add is not interested.
I have a fresh install of squeeze without a desktop environment. I then installed a basic gnome environment so I can choose my own apps ('apt-get install gdm3' pulls in enough for that). I then had to install some packages to get mobile broadband working:It all works fine until I disconnect it via Gnome network manager. I cannot reconnect using Gnome network manager because it doesn't show in the menu, but it does show while I'm connected. If I pull the dongle out and plug it in again, it reconnects without issue.I think I may be missing some packages, but I don't know what. I tried usb-modeswitch, but no change
View 10 Replies View RelatedI have Debian and Virtual Box with another Debian. I have resized max size of vdi file with VBoxManage modifyhd but now I need to resize partition on virtual machine's system. I've downloaded GParted and I can run machine from this ISO as CD. Partition is encrypted on machine.Unfortunately GParted doesn't start with X so I have to use it in terminal. I can see partitions:
Code: Select allroot@debian:/# fdisk -l
Disk /dev/sda: 80 GiB, 85899345920 bytes, 167772610 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x3914....
[code]....
So I though maybe I need to use this (URL...). I couldn't find similar tutorial about Debian or GParted but OK, it's just executing these commands, not modifying its source.list.But I cannot even do the update:
Code: Select allroot@debian:/# sudo apt-get update
Err: http://free.nchc.org.tw/debian sid InRelease
Temporary failure resolving 'free.nchc.org.tw'
Err2: http://free.nchc.org.tw/drbl-core drbl InRelease
Temporary failure resolving 'free.nchc.org.tw'
Reading package lists... Done
W: Failed to fetch http://free.nchc.org.tw/debian/dists/sid/InRelease Teporary failure resolving 'free.nchc.org.tw'
W: Failed to fetch http://free.nchc.org.tw/drbl-core/dists/drbl/InRelease Temporary failure resolving 'free.nchc.org.tw'
W: Some index files failed to download. They have been ignored, or old ones used instead.
So I check my internet connection. VirtualBox has 'attached to NAT' and before I run out of space on virtual machine, Debian could access internet. So it's only something about this GParted. I have modified /etc/resolv.conf with vi (even vim is not available). And it has two valid nameservers. I haven't restarted anything, as I'm not sure if I need to, after modifying resolv.conf file.But even in that case I cannot ping anything from GParted:
Code: Select allroot@debian:/# ping www.google.com
ping: unknown host www.google.com
How can I access internet from GParted and resize encrypted partition?
When I installed Debian on this machine, I went with guided partitioning, encrypted lvm, and Debian defaulted to a 10GB / partition. I figured, hey, defaults are there for a reason, so left it alone.
Now that I need to shrink my /home and extend /, I'd like to do so as easily as possible. I installed system-config-lvm, read its man page ( which is really just a long description of the program, not much instruction ) and fired it up. Won't let me resize ( shrink ) /home, said files are in use.
Is there a way to use the nice pretty graphical tool, or do I need to boot to a non-X-using runlevel and log in as root, then muck about with CLI tools like lvresize and resize2fs?
I want to move my old system to a new drive. Currently I have Debian installed with following configuration:
I have an encrypted system where everything is encrypted except /boot. Currently I've /boot and / installed on a 16 GB mSata SSD and /home on a regulard HDD. I've got a 500GB SSD for Christmas and want to move the whole system to the new SSD.
I just wanted to ask if I've got the process required to to this down:
1. backup root-directory (/) without and /boot /home using tar keeping file-permissions and owners to ext. hard drive
2. backup /boot and /home separately using the same method
2. replace HDD with SSD remove mSATA SDD.
3. boot via live-usb
4. create appropriate volume groups, partitions, setup encryption etc.
5. extract backups to appropriate partitions
6. chroot to old /.
7. edit fstab
8. reinstall grub
9. create new init ram img.
I'm pretty sure I've got steps 1.-6. down but I'm very shaky on what to do next.
Is it better to install LUKS to raw disk (/dev/sdb) or disk partition (/dev/sdb1)? What are best LUKS options?
"cryptsetup benchmark" output
Code: Select allPBKDF2-sha1 1310720 iterations per second
PBKDF2-sha256 862315 iterations per second
PBKDF2-sha512 590414 iterations per second
[Code] ....
Is slow hash better or how to choose it? It is clear that aes-xts is best choise. Is 265 bit key good?
is it possible to mount a truecrypt file container as a home directory before login, if so how to do that?
View 3 Replies View RelatedI use a static compiled kernel and a fully encrypted disk apart from a boot partition. I have recompiled and installed kernels many times. When I tried with the latest kernel from Testing, 4.2.6, the system will not boot. Not only that but the previous kernel now does not boot. However, a stock modular kernel does boot. The static kernel hangs at:
Code: Select allVolume group "dk" not found
Cannot process volume group dk
/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
Reading all physical volumes. This may take a while...
/run/lvm/lvmetad.socket: connect failed: No such file or directory
[Code] ....
And after giving the password the boot continues successfully. How to diagnose it further?
I am trying to create an encrypted file and later mount it as a filesystem.
KEY=`tr -cd [:graph:] < /dev/urandom | head -c 79`
echo $KEY | openssl aes-256-cbc > container.key
dd if=/dev/urandom of=~/container.img bs=1G count=10
losetup /dev/loop0 ~/container.img
[code]....
The luksOpen command asks me for my passphrase, but always rejects it. I have retried this several times and written down the passphrase - and even tried with a very simple one just to check. And I never can make it work.
My partitions are set up as follows:
[code]...
I installed Ubuntu successfully using rescue mode on the alternate cd, and let Ubuntu use an internal boot and home. At the final stage grub refused to install to the MBR, and then refused to install to my /boot partition on /dev/sda2. It said: No boot loader has been installed, either because you chose not to or because your specific architecture doesn't support a boot loader yet. You will need to boot manually with the /vmlinuz kernel on partition /dev/mapper/volumegroup-natty and root=/dev/mapper/volumegroup-natty passed as a kernel argument. Returning to debian, I did a update-grub, which detects Windows and Ubuntu:
[code]...
How do I make grub decrypt the LUKS partition before attempting to load the Ubuntu kernel?
how can I set the keyboard layout used by Debian to enter the password of my encrypted filesystem?
After my recent "aptitude upgrade", I have not been able to mount my encrypted filesystem anymore. I have discovered that the keyboard layout used to enter the password has changed. Problem is that with such layout I can't enter some of the characters composing the password. The encrypted filesystem looks intact, since I have been able to mount it and backup my files by means of a live CD. That means that I can edit any system file, if needed.
Every technique I have found to change layout cannot be employed in this case, since they rely on the system being up and running. I've tried editing /etc/default/keyboard, but that does not work.
I have this new computer (MSI Ge70 2PE Apache Pro) that came with Windows 8 and UEFI. I freed space to make a partition to install Debian testing 64bits on the same HD where Windows is. I had no problem making the partition but after that I tried making a bootable usb to install Debian using the dd command and it didn't work. So I tried with an install dvd and even when I changed the boot order in the bios it didn't work.
After reading some more I realized that there could be a problem trying to boot a normal installation dvd with UEFi so I disabled Secure Boot and then switched the boot mode on my Bios to UEFI with CSM. Again it didn't work and it booted directly into Windows. So I switched the boot mode to Legacy. This time Windows didn't boot directly but I get a "Reboot and Select proper Boot device" message on a black screen.
I now realize that I need to install a UEFI "version" of Debian along the UEFI version of Windows 8. I guess that's why it didn't work with the Legacy boot mode. URL...The installer does not provide a convenient way to install an UEFI boot loader, so you are going to install a regular BIOS boot loader at first, and switch to UEFI later.
Use the expert mode and format your hard drive with a GUID Partition Table (GPT). Create a small partition (1 MiB would be far enough), type it as a BIOS Boot Partition (this is the untitled flag above the “bootable” one in Partman), do not format it and do not mount it: this will be needed for BIOS booting. Create another small partition (same kind of size), type it as an EFI System Partition (this is the“bootable” flag), format it as FAT and mount it on /boot/efi: this will be needed for UEFI booting.
I tried to install the latest version of Debian from a Live USB on my new laptop (UEFI). Everything goes well during installation (EFI partition, grub-efi, etc), but after restart, my computer does not boot into HDD.
How to debug the problem or fix the boot loader. What is the problem in standard installation? and how can I fix the boot loader?
I have Acer Aspire S7-392. It has two 128GB SSD drives. They are using RAID 0. Currently there is Windows 8.1 installed on the RAID 0 drive.I am trying to install Debian 7.6 (wheezy) alongside Win 8.1 (dual boot). Actually I have already created linux partitions and installed mentioned Debian on my computer. I had to skip grub installation due to fatal error that had occurred. (Everything on existing RAID 0 volume).Now I am looking the way to install grub and boot Debian. I have disabled UEFI Secure Boot. It didn't work.
My question is:
1. Is it possible to have Win 8.1 and Debian dual-bootable on the same RAID 0 volume? How to install grub and boot debian?
2. If not, what am I supposed to do to achieve what I want (these two systems on one computer)? Delete old one RAID 0 and create two new: one for windows and one for linux partitions?
I have a server in which I'm trying to install Debian into. There's no BIOS, only EFI boot. The vendor locked it down so there's no way to see it or get into it.
The Wheezy 7.8 netinst CD has EFI boot parameters and works on everything I throw it in, except this one server. Booting it up, the code doesn't see the EFI and boots into normal mode, negating every chance to install it (dozens upon dozens of failed installs).
During boot, I press the [TAB] at the Debian Linux installer menu and get the load parameters (/install.amd/vmlinuz vga=788 etc). What parameter can I add to this line to get it to run in UEFI mode so we can install it?
I have Debian installed but I need to dual boot with distribution based on Ubuntu 14.04. This is my first UEFI dual boot install attempt. And I must do it right. I must not lose my Debian !
Code: Select allDisk /dev/sdb: 232,9 GiB, 250059350016 bytes, 488397168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
[Code] ....
Ubuntu will go to /dev/sdb5 but I don`t no for sure what to do when installing Ubuntu. How to select during install existing UEFI partition(/dev/sdb1) so Debian and Ubuntu can use it. Can I select existing UEFI partition like I would do for /home or /swap ? Will this work ?
And what will happen with Grub if I select install grub ? I want to manage grub from Debian, it is my main OS. Can I skip Grub install and just update grub on my debian after ubuntu install ? Or I just install grub, then after completed Ubuntu install I install it again from Debian. Will this work ?
Is procedure of installing dual boot trivial like before or UEFI hide`s some unpleasant surprise.
I'll start off with stating my problem and summarize how I got to it.
I installed Windows 10 on an SSD. I installed Debian 8.2 after it. The SSD was/is a GPT disk. I installed both installations from a UEFI booted device (DVD for Windows, and USB drive with Live CD for Debian).
I tested it after each installation making sure I could boot via UEFI into Windows, then Debian, then Windows, to make sure nothing broke.
I rebooted the machine. Suddenly, no more UEFI. Nothing. I didn't change any BIOS/UEFI setup menu settings. Not even my USB drive with Live CD will boot through UEFI anymore. Even when nothing else is plugged into the system.
My situation is actually a bit more complicated than that, but I think that will suffice for now. I can still boot into the Live CD on the USB drive, just in Legacy mode only. I mounted the EFI partition on /mnt/boot after I mounted the file system for Debian on /mnt. It is identical, as far as I can tell, to as it was before when it was working.
My motherboard has CSM and Secure Boot, both have been set up how they need to be to boot UEFI into Debian. Tinkering with them further after things broke did not fix it. I tried all variations of options/settings.
The GRUB Reinstall guide says to be in EFI mode before starting it, so I can't do that.
My motherboard is an ASUS X99 Deluxe, and I've heard ASUS has special "features" (read: bugs) that come with their boards. Searching hasn't brought up any other people with this issue. I believe the firmware is updated to it's most current one.
I've tried dd-ing my backup of my old system, from before trying to migrate to a Dual Boot system, to the SSD (after backing up the dual boot setup with dd -> <name>.img via the Live CD USB). However, that won't boot either as it is a UEFI install as well.
The layout of my EFI partition is as such:
/boot/EFI/Boot/bootx64.efi
/boot/EFI/Microsoft/<Microsoft-naming>.efi
/boot/EFI/debian/grubx64.efi
I've heard that the standards on how that's supposed to be set up isn't a standard. However, since it worked booting into the OS' the first time, I don't see how that could be the issue (a bad hierarchy layout leading to the UEFI not being able to see the OS installs).
I've seen that I can boot to an EFI shell (called Shell.efi, apparently) via an option in my UEFI BIOS setup menu on my motherboard. Is that an option here to somehow bypass this strange issue?
All I can think to try is burn it all and start over. But not knowing what caused it means I could just make it happen again. Plus, I can't boot into UEFI install media, so I can't install UEFI boot OS'. :/
As you probably know Debian LIVE ISOs is not (U)EFI bootable since there is no EFI bootloader on them. I need to boot usb for uefi mode...
View 3 Replies View RelatedMy computer's recent history in chronological order:
1. debian jessie is installed using netinstall iso to sda.
2. windows 8.1 is installed to sdc.
Now "lsblk" returns:
Code: Select allNAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 111.8G 0 disk
├─sda1 8:1 0 512M 0 part /boot/efi
├─sda2 8:2 0 244M 0 part /boot
└─sda3 8:3 0 111.1G 0 part
└─sda3_crypt 254:0 0 111.1G 0 crypt
[code]....
Result: My computer boots directly to Windows 8.1. If I press F7 during first seconds of boot and choose "debian" as the boot device (via blue bios screen, not grub), debian boots.
My purpose:
1. To use debian grub screen to choose between debian and Windows. (To avoid pressing F7 during boot to use debian)
2. Set debian as default OS in grub and boot to debian unless I choose otherwise in for example 10 seconds.
I guess that I should update grub to fix this but I don't want to take risk.
My Toshiba Satellite C870-198 has Debian 7.7 installed in UEFI mode alongside Windows 8.1. The GRUB menu no longer displays, but the machine boots straight into Windows.
I can boot into Debian or Windows from rEFInd installed on a USB stick. The rEFInd menu has the following entries:
The Debian entry actually launches the GRUB menu which was installed with Debian.
Code: Select allBoot Microsoft EFI boot (Boot Repair backup) from Basic data partition.
Boot supposed Microsoft EFI boot (probably GRUB) from Basic data partition.
Boot EFIubuntugrubx64.efi from Basic data partition.
Boot EFIdebiangrubx64.efi from Basic data partition.
Boot bootootx64.efi from Basic data partition.
Boot vmlinuz-3.2.0-4-amd64 from boot.
In an attempt to fix GRUB I executed the commands in the 'Reinstalling grub-efi on your hard drive' section of: [URL] ....
Code: Select allmount /dev/sda1 /boot/efi
... surprisingly returned:
Code: Select all$LogFile version 2.0 is not supported. (This driver supports version 1.1 only.)
$LogFile version 2.0 is not supported. (This driver supports version 1.1 only.)
Did not find any restart pages in $LogFile and it was not empty.
The file system wasn't safely closed on Windows. Fixing.
Code: Select all[ -d /sys/firmware/efi ] && echo "EFI boot on HDD" || echo "Legacy boot on HDD"
... returned "EFI boot on HDD".
[Code] ....
... Where is Debian?
FULL HISTORY ....
=============================
The laptop came with Windows 8 preinstalled. I switched off Secure Boot and installed Ubuntu for UEFI dual boot. I recall having to use Boot Repair to get the GRUB boot manager working properly for both systems.
Recently I decided to replace Ubuntu with Debian 7.7 and first cloned the entire hard drive to a USB drive (The Clone Drive). This drive successfully boots into Ubuntu in UEFI mode.
Following this I took the opportunity to update Windows to 8.1, which broke GRUB as expected, so that the machine would only boot straight into Windows.
I installed Debian from a live USB stick in the mistaken belief that it would be bootable in UEFI mode. It did boot OK in legacy mode.
I then burned the full Debian 'DVD' image to a USB stick, booted it in UEFI mode and reinstalled Debian. In UEFI mode GRUB allowed me to boot into both Debian and Windows.
At this point I tested The Clone Drive. It was still able to boot into Ubuntu as previously, but after powering down, unplugging The Clone Drive and rebooting, the GRUB menu failed to appear and the machine booted straight into Windows. This is its current state.
I'm trying to install debian and when the installer starts it UEFI at the top, instlal completes however on reboot it says 'no operating system found' i've read it can be because of UEFI but I have tried different bios options but to no avail.
Bios options
Sata mode: AHCI/IDE (haven't tried IDE yet)
Tried various combinations of the below
CSM: enable/disable
Boot Priority: Auto/legancy first/uefi first
Quick Boot: enable/disable
Boot up Num-lock Status: on/off
Debian-live-8.2.0-amd64-xfce-desktop.iso do not boot in uefi mode. I would like to know if live image can boot uefi mode? If not how can I do later from bios to install grub efi?
View 1 Replies View RelatedOn Windows OS, I can create Debian UEFI USB boot by mount Debian ISO and directly copy content of ISO to USB FAT32. On Debian OS, When I mount the debian iso and directly copy content of iso to usb fat32, I keep getting this error: "Filesystem does not support symbolic links".I choose to skip all, the copy operation continue but USB can't boot.
Question: How to create Debian USB UEFI boot by copying content of iso file directly to fat32 usb on Debian OS?My OS: Debian Jessie RC1.The ISO file: debian-jessie-DI-rc1-amd64-DVD-1.iso URL....
I installed Debian Jessie (netinst, daily snapshot) on my Acer Aspire V5-123 laptop in the UEFI mode with the secure boot turned off. everything (network, hardware, partitioning, ...) went smoothly to the last step, but after removing the boot media (USB stick) and rebooting, the firmware could not find the boot device ! The only thing I can think of, is that the EFI boot is not set up properly by Debian installer, but I don't know how to fix it.
View 11 Replies View RelatedI've set up a dual boot system with Debian and Windows 8, both installed on their own drive, with their own boot partition. I installed eveything in UEFI-Mode with fast- and secure boot turned off. Both installations are working, as I can access them by changing the boot priority in the Bios. What I cannot achieve is to let grub boot my windows installation.
This is the output of parted -l:
Code: Select allModel: ATA Samsung SSD 840 (scsi)
Disk /dev/sda: 128GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 1049kB 512MB 511MB fat32 boot
2 512MB 111GB 111GB ext4
3 111GB 128GB 17,0GB linux-swap(v1)
[Code] ....
As you can see, my linux install is on sda, my windows install on sdc (sdb beeing a data disk). This is the entry I made in the 40_custom file in etc/grub.d:
Code: Select allmenuentry "Windows 8.1" {
insmod part_gpt
insmod chain
set root='(hd2,gpt2)'
chainloader /EFI/Microsoft/Boot/bootmgfw.efi
boot
}
I think this should be fine, but if I choose the windows entry wehen grub is booting, it says: error: no such partition. It's my first debian installation, and I am stuck here. Not too much of Linux experience in general.
I just installed Debian jessie on my Dell Latitude E6410 using the UEFI install. No everything went well during the install, but after the install the first boot i ran into an issue that the laptop will not boot.
When I go in to the boot menu of the Dell Latitude E6410, I see that debian has created a uefi name (Debian)
When I select this, it boots without any issues. After again a reboot again, no luck still a black screen during the boot.
Seems that the only option to get my laptop booting is by pressing F12 and select Debian in the UEFI boot of the laptop.
Is there any way i can get my laptop to boot Debian directly from UEFI, without having to press F12?? (Also disabled all legacy devices to start up but no luck)...
- Debian Jessie X64 (Using 32/64 network install, via USB)
- Dell Latitude E6410 i5 (1280x800 intel graphics) latest bios A16
- SSD drive (Samsung 470 series)
- Debian is the only OS installed
I have installed Debian Jessie 8.0.3 64-bit net install on an IBM ThinkCentre. I have earlier had a dual boot Win 8 and Ubuntu 14.04 installed on the computer. When I installed Debian Jessie, I deleted the Ubuntu partitions and created new partitions from the free space. The install went fine and the Debian EFI/UEFI version of Grub was installed, but clearly at some other place, as when I boot the system, the old Ubuntu Grub pops up and of course cannot find the necessary files that it is looking for.
View 9 Replies View Related