Re: Can't boot following re-install to LVM on LUKS [was: can't login via gdm]

On Mon, Aug 16, 2021 at 03:46:51PM +0100, Morgan Read wrote: > On 11/08/2021 11:30 pm, David Christensen wrote: > > On 8/11/21 6:45 AM, Morgan Read wrote: > >> After having overcome a fairly fundamental bug with calamares as > >> described here: > >> https://github.com/ca

Re: Can't boot following re-install to LVM on LUKS [was: can't login via gdm]

On Mon, Aug 16, 2021 at 03:46:51PM +0100, Morgan Read wrote: > On 11/08/2021 11:30 pm, David Christensen wrote: > > On 8/11/21 6:45 AM, Morgan Read wrote: > >> After having overcome a fairly fundamental bug with calamares as > >> described here: > >> https://github.com/calamares/calamares/issues/15

Re: Can't boot following re-install to LVM on LUKS [was: can't login via gdm]

On 11/08/2021 11:30 pm, David Christensen wrote: > On 8/11/21 6:45 AM, Morgan Read wrote: >> After having overcome a fairly fundamental bug with calamares as >> described here: >> https://github.com/calamares/calamares/issues/1564#issuecomment-846321060 >> And, (unnecessarily as it turned out) re-i

Re: Can't boot following re-install to LVM on LUKS [was: can't login via gdm]

On 8/11/21 6:45 AM, Morgan Read wrote: Hi List, Since my cry for (fairly minor) help here: https://lists.debian.org/debian-user/2021/08/msg00461.html I think I've dug myself into a bit of a deep hole. After having overcome a fairly fundamental bug with calamares as described here: https://github

Can't boot following re-install to LVM on LUKS [was: can't login via gdm]

Hi List, Since my cry for (fairly minor) help here: https://lists.debian.org/debian-user/2021/08/msg00461.html I think I've dug myself into a bit of a deep hole. After having overcome a fairly fundamental bug with calamares as described here: https://github.com/calamares/calamares/issues/1564#issu

Re: can't boot to a graphical interface.

On Sat, 3 Oct 2020 13:39:22 -0400 Frank McCormick wrote: > On 10/3/20 11:20 AM, Kent West wrote: > > > > > > On Sat, Oct 3, 2020 at 8:01 AM songbird > > wrote: > > > > Frank McCormick wrote: > > > While compiling an application today my Debian bullseye

Re: can't boot to a graphical interface.

On 10/3/20 11:20 AM, Kent West wrote: On Sat, Oct 3, 2020 at 8:01 AM songbird > wrote: Frank McCormick wrote: > While compiling an application today my Debian bullseye system somehow > got messed up. It will boot to a CLI but no X, apparently

Re: can't boot to a graphical interface.

On Sat, Oct 3, 2020 at 8:01 AM songbird wrote: > Frank McCormick wrote: > > While compiling an application today my Debian bullseye system somehow > > got messed up. It will boot to a CLI but no X, apparently because for > > some reason the system is unable to access some files in > > /usr/share/

Re: can't boot to a graphical interface.

Frank McCormick wrote: > While compiling an application today my Debian bullseye system somehow > got messed up. It will boot to a CLI but no X, apparently because for > some reason the system is unable to access some files in > /usr/share/dbus-1. It keeps saying access denied. The directories a

Re: can't boot to a graphical interface.

On Sat, 3 Oct 2020 at 03:24, Frank McCormick wrote: > While compiling an application today my Debian bullseye system somehow > got messed up. It will boot to a CLI but no X, apparently because for > some reason the system is unable to access some files in > /usr/share/dbus-1. It keeps saying acce

Re: can't boot to a graphical interface.

Frank McCormick wrote: > While compiling an application today my Debian bullseye system somehow > got messed up. next time compile in chroot and as a dedicated user (not root)

can't boot to a graphical interface.

While compiling an application today my Debian bullseye system somehow got messed up. It will boot to a CLI but no X, apparently because for some reason the system is unable to access some files in /usr/share/dbus-1. It keeps saying access denied. The directories and files are owned by root, an

Re: can't boot a Debian on QEMU-mips virtual machine, could be initrd or root device problems

Hi, Reco wrote: > $ qemu-system-mips -m 2048 -nographic > -cdrom /tmp/debian-7.4.0-mips-netinst.iso -boot d > qemu-system-mips: Could not load MIPS bios 'mips_bios.bin', and no -kernel > argument was specified Oops. I did not expect it to die so early. > Also, that 'iso' is no way a conventiona

Re: can't boot a Debian on QEMU-mips virtual machine, could be initrd or root device problems

Hi. On Mon, Apr 30, 2018 at 06:58:13PM +0200, Thomas Schmitt wrote: > Hi, > > i wrote: > > > Shouldn't there be a bootloader installed in debian_mips32b.img ? > > Reco wrote: > > No. One of the oddities of QEMU's malta that nobody was able to > > write a > > working bootloader for it. OP i

Re: can't boot a Debian on QEMU-mips virtual machine, could be initrd or root device problems

Hi. In-Reply-To: <3824776101913512...@scdbackup.webframe.org> On Mon, Apr 30, 2018 at 06:58:13PM +0200, Thomas Schmitt wrote: > Hi, > > i wrote: > > > Shouldn't there be a bootloader installed in debian_mips32b.img ? > > Reco wrote: > > No. One of the oddities of QEMU's malta that nobod

Re: can't boot a Debian on QEMU-mips virtual machine, could be initrd or root device problems

Hi, i wrote: > > Shouldn't there be a bootloader installed in debian_mips32b.img ? Reco wrote: > No. One of the oddities of QEMU's malta that nobody was able to write a > working bootloader for it. OP is doing it the only way that's possible. And he has luck to already have found somebody who ha

Re: can't boot a Debian on QEMU-mips virtual machine, could be initrd or root device problems

Thanks Reco. The concept I missed is, I need to grab the initrd and kernel from the installed system, specifically from the /boot directory. I know that now for all future architectures I mess with! There are lots of ways to do the same thing, I'm just sharing. To mount a partition inside raw disk

Re: can't boot a Debian on QEMU-mips virtual machine, could be initrd or root device problems

Hi. On Mon, Apr 30, 2018 at 06:30:32PM +0200, Thomas Schmitt wrote: > > # qemu-system-mips -m 2048 -rtc base=localtime -boot order=c > > -nographic -hda debian_mips32b.img -kernel vmlinux-4.9.0-6-4kc-malta > > -append "root=/dev/sda1" > > Shouldn't there be a bootloader installed in debia

Re: can't boot a Debian on QEMU-mips virtual machine, could be initrd or root device problems

Hi. On Mon, Apr 30, 2018 at 07:54:56AM -0700, Alan Tu wrote: > Hi, I'm having trouble bootting Debian 9.4 on a QEMU-emulated MIPS > malta virtual machine. I know QEMU introduces some complexity, but I > think my problem is more of a misunderstanding of Linux boot concepts. > I've tried dif

Re: can't boot a Debian on QEMU-mips virtual machine, could be initrd or root device problems

Hi, Alan Tu wrote: > I installed Debian inside a virtual disk image. >From outside qemu ? That could be tricky because being unusual. Last time i installed a virtual Debian, i did something like this: # Create virtual disk as data file qemu-img create debian_vm_disk.qemu 32G # Start qem

can't boot a Debian on QEMU-mips virtual machine, could be initrd or root device problems

Hi, I'm having trouble bootting Debian 9.4 on a QEMU-emulated MIPS malta virtual machine. I know QEMU introduces some complexity, but I think my problem is more of a misunderstanding of Linux boot concepts. I've tried different permutations, and reading, but am stuck. I installed Debian inside a v

Re: Thinkpad R40e can't boot Debian 9.0.0 netinst image without acpi=off

Olivier F. R. Dierick wrote: > acpi=off I don't know about the kernel http://www.thinkwiki.org/wiki/Category:R40e but you better check if your ATI will be supported with the recent X server ;) regards

Thinkpad R40e can't boot Debian 9.0.0 netinst image without acpi=off

Hi, I wanted to file a bug report, but I don't know which package the issue belongs to. The computer is a IBM Thinkpad R40e. Currently Debian 8 is installed. Ever since Debian 8 was installed on the harddrive I had to add acpi=off to the kernel options, otherwise the computer does not boot. No o

Re: Debian Testing. Can't boot after apt-get dist-upgrade (28 March 2016)

Hello, El 29 de marzo de 2016 9:16:09 CEST, Sergei Petrunin escribió: >Thanks for response! > >Unfortunately, I have to report that doing > >sudo install-grub /dev/sda#/dev/sda is by device for hard-drive >with >lvm, may be I need some specific options here? >sudo upgrade-grub > >do not cure

Re: Debian Testing. Can't boot after apt-get dist-upgrade (28 March 2016)

Thanks for response! Unfortunately, I have to report that doing sudo install-grub /dev/sda#/dev/sda is by device for hard-drive with lvm, may be I need some specific options here? sudo upgrade-grub do not cure boot for 4.4.0 kernel - same problem persists, still 4.3.0 kernel (in "Advanced GR

Re: Debian Testing. Can't boot after apt-get dist-upgrade (28 March 2016)

On 2016-03-28 11:46:46 PM, Sergei Petrunin wrote: During the system boot I get the following message: Begin: Running /scripts/local-block ... lvmetad is not active yet sysinit Volume group "strog-vg" not found Cannot process volume group strog-vg done. --- several times message like this --- -

Debian Testing. Can't boot after apt-get dist-upgrade (28 March 2016)

Hello, Just execute update commands: sudo apt-get update sudo apt-get upgrade sudo apt-get dist-upgrade After that I no longer be able to boot on 4.4.0 kernel (I using it for some time already), so I boot now from 4.3.0. During the system boot I get the following message: Begin: Running /scrip

Re: can't boot Jessie since power drop-out (virtualbox on MacBook with SSD)

On Qua, 04 Nov 2015, Brendan Simon (eTRIX) wrote: I was going to do a reinstall but I couldn't find a way of doing that without repartitioning the disk (which I didn't want to do as I don't want to lose any of my data). It's certainly possible to resintall without repartitioning or formating.

Re: can't boot Jessie since power drop-out (virtualbox on MacBook with SSD)

On 5/11/2015 10:09 AM, Charlie Kravetz wrote: > On Thu, 5 Nov 2015 09:59:19 +1100 > "Brendan Simon (eTRIX)" wrote: > >> I was/am running Jessie 8.2 in a VirtualBox on my MacBook. The MacBook >> shutdown without warning while my Jessie VB was running, and now the VM >> wont boot properly. I get s

Re: can't boot Jessie since power drop-out (virtualbox on MacBook with SSD)

On Thu, 5 Nov 2015 09:59:19 +1100 "Brendan Simon (eTRIX)" wrote: >I was/am running Jessie 8.2 in a VirtualBox on my MacBook. The MacBook >shutdown without warning while my Jessie VB was running, and now the VM >wont boot properly. I get stuck in emergency mode. Ctrl-D does nothing >- just cycl

can't boot Jessie since power drop-out (virtualbox on MacBook with SSD)

I was/am running Jessie 8.2 in a VirtualBox on my MacBook. The MacBook shutdown without warning while my Jessie VB was running, and now the VM wont boot properly. I get stuck in emergency mode. Ctrl-D does nothing - just cycle back to same message. I googled a bit and found that if I comment ou

Re: [solved] Re: Can't boot from pendrive

On Sat 24 Jan 2015 at 16:51:20 +, Rodolfo Medina wrote: > But now, one more question: after using the pendrive for the installation, how > can I restore it as it was before, to use it to store files? dd if=/dev/zero of=/dev/sdX count=1 Then partition and put filesystems on the partitions

[solved] Re: Can't boot from pendrive

Rodolfo Medina writes: > Brian writes: > >> On Sat 24 Jan 2015 at 15:41:05 +, Rodolfo Medina wrote: >> >>> Brian writes: >>> >>> > On Sat 24 Jan 2015 at 15:18:28 +, Rodolfo Medina wrote: >>> > >>> >> Brian writes: >>> >> >>> >> > On Sat 24 Jan 2015 at 12:26:02 +, Rodolfo Medina w

Re: Can't boot from pendrive

On Sat 24 Jan 2015 at 16:12:52 +, Rodolfo Medina wrote: > Brian writes: > > > No restoring is needed. > > > >dd if=debian-7.8.0-i386-netinst.iso of=/dev/sdX bs=4M; sync > > > > will obliterate the drive's contents. > > > > Note it is /dev/sdX, not /dev/sdXN. Writing to partition number N

Re: Can't boot from pendrive

Brian writes: > On Sat 24 Jan 2015 at 15:41:05 +, Rodolfo Medina wrote: > >> Brian writes: >> >> > On Sat 24 Jan 2015 at 15:18:28 +, Rodolfo Medina wrote: >> > >> >> Brian writes: >> >> >> >> > On Sat 24 Jan 2015 at 12:26:02 +, Rodolfo Medina wrote: >> >> > >> >> >> From: >> >> >>

Re: Can't boot from pendrive

On 24/01/2015 16:10, Brian wrote: On Sat 24 Jan 2015 at 15:26:19 +0100, mrr wrote: On 24/01/2015 13:30, Rodolfo Medina wrote: Hi all. From: http://www.us.debian.org/CD/netinst/ I downloaded the file debian-7.8.0-i386-netinst.iso and copied it onto a pendrive with: $ dd if=debian-7.8.0-

Re: Can't boot from pendrive

On Sat 24 Jan 2015 at 15:41:05 +, Rodolfo Medina wrote: > Brian writes: > > > On Sat 24 Jan 2015 at 15:18:28 +, Rodolfo Medina wrote: > > > >> Brian writes: > >> > >> > On Sat 24 Jan 2015 at 12:26:02 +, Rodolfo Medina wrote: > >> > > >> >> From: > >> >> > >> >> http://www.us.debi

Re: Can't boot from pendrive

Brian writes: > On Sat 24 Jan 2015 at 15:18:28 +, Rodolfo Medina wrote: > >> Brian writes: >> >> > On Sat 24 Jan 2015 at 12:26:02 +, Rodolfo Medina wrote: >> > >> >> From: >> >> >> >> http://www.us.debian.org/CD/netinst/ >> >> >> >> I downloaded the file debian-7.8.0-i386-netinst.iso

Re: Can't boot from pendrive

On Sat 24 Jan 2015 at 15:18:28 +, Rodolfo Medina wrote: > Brian writes: > > > On Sat 24 Jan 2015 at 12:26:02 +, Rodolfo Medina wrote: > > > >> From: > >> > >> http://www.us.debian.org/CD/netinst/ > >> > >> I downloaded the file debian-7.8.0-i386-netinst.iso and copied it onto a > >> p

Re: Can't boot from pendrive

dd if=debian-7.8.0-i386-netinst.iso of=/dev/sdc bs=4M; sync That was actually `sdb1', not `sdc', sorry. > That's an ok command. > >> , but then can't boot from it even though the BIOS is - apparently - >> configured so to do that. Why? > > Assuming the

Re: Can't boot from pendrive

On Sat 24 Jan 2015 at 15:26:19 +0100, mrr wrote: > On 24/01/2015 13:30, Rodolfo Medina wrote: > >Hi all. > > > >From: > > > > http://www.us.debian.org/CD/netinst/ > > > >I downloaded the file debian-7.8.0-i386-netinst.iso and copied it onto a > >pendrive with: > > > > $ dd if=debian-7.8.0-i386-n

Re: Can't boot from pendrive

launch the dd on it, does it work? , but then can't boot from it even though the BIOS is - apparently - configured so to do that. Why? Thanks for any help, Rodolfo -- -- mrr -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". T

Re: Can't boot from pendrive

Rodolfo Medina wrote: > From: > > http://www.us.debian.org/CD/netinst/ > > I downloaded the file debian-7.8.0-i386-netinst.iso and copied it > onto a pendrive with: > > $ dd if=debian-7.8.0-i386-netinst.iso of=/dev/sdc bs=4M; sync > > , but then can't b

Re: Can't boot from pendrive

nc That's an ok command. > , but then can't boot from it even though the BIOS is - apparently - > configured > so to do that. Why? Assuming the machine can boot from USB, check the BIOS settings again. On a running system, please post the outputs of fdisk -l debian-7.8.0-i

Can't boot from pendrive

Hi all. From: http://www.us.debian.org/CD/netinst/ I downloaded the file debian-7.8.0-i386-netinst.iso and copied it onto a pendrive with: $ dd if=debian-7.8.0-i386-netinst.iso of=/dev/sdc bs=4M; sync , but then can't boot from it even though the BIOS is - apparently - configured so

Re: Can't boot after harddrive replacement

On Mon, 12 May 2014, Klaus wrote: Date: Mon, 12 May 2014 09:13:46 +0100 From: Klaus To: debian-user@lists.debian.org Subject: Re: Can't boot after harddrive replacement Resent-Date: Mon, 12 May 2014 08:14:07 + (UTC) Resent-From: debian-user@lists.debian.org On 11/05/14 09:46, Itay

Re: Can't boot after harddrive replacement

On Mon, 12 May 2014, Steve Litt wrote: Date: Mon, 12 May 2014 03:46:38 -0400 From: Steve Litt To: debian-user@lists.debian.org Subject: Re: Can't boot after harddrive replacement Resent-Date: Mon, 12 May 2014 07:46:54 + (UTC) Resent-From: debian-user@lists.debian.org On Mon, 12 May

Re: Can't boot after harddrive replacement

On Sun, 11 May 2014, Filip wrote: Date: Sun, 11 May 2014 22:25:35 +0200 From: Filip To: debian-user@lists.debian.org Subject: Re: Can't boot after harddrive replacement Resent-Date: Sun, 11 May 2014 20:25:58 + (UTC) Resent-From: debian-user@lists.debian.org On Sun, 11 May 2014 22:

Re: Can't boot after harddrive replacement

On Sun, 11 May 2014, Eduardo M KALINOWSKI wrote: Date: Sun, 11 May 2014 08:40:49 -0300 From: Eduardo M KALINOWSKI To: debian-user@lists.debian.org Subject: Re: Can't boot after harddrive replacement Resent-Date: Sun, 11 May 2014 11:57:44 + (UTC) Resent-From: debian-user@lists.debia

Re: Can't boot after harddrive replacement

On Sun, 11 May 2014, Hans-J. Ullrich wrote: Date: Sun, 11 May 2014 12:03:25 +0200 From: Hans-J. Ullrich To: debian-user@lists.debian.org Cc: Itay Subject: Re: Can't boot after harddrive replacement Resent-Date: Sun, 11 May 2014 10:04:18 + (UTC) Resent-From: debian-user@lists.debia

Re: Can't boot after harddrive replacement

On Sun, 11 May 2014, Itay Furman wrote: Date: Sun, 11 May 2014 14:08:51 +0300 From: Itay Furman To: debian-user@lists.debian.org Subject: Re: Can't boot after harddrive replacement Resent-Date: Sun, 11 May 2014 11:24:42 + (UTC) Resent-From: debian-user@lists.debian.org On Sun, M

Re: Can't boot after harddrive replacement

On 11/05/14 09:46, Itay wrote:> Hi > > > Summary of steps > > 1. Using rsync -aHq I backed up most of the file system (excluding > /proc, /sys, /run, /srv, and /tmp) On 11/05/14 20:38, Itay Furman wrote: > > > Well, right. Here is some of the output (manually typed) > > mount point

Re: Can't boot after harddrive replacement

On Mon, 12 May 2014 03:26:08 -0400 Steve Litt wrote: > On Sun, 11 May 2014 22:38:20 +0300 > Itay Furman wrote: > > > mount point /proc does not exist [Note: similar errors for few more > > missing mount points such as /usr/local, /cache] > > > > special device /dev/sda1 does not exist [Note:

Re: Can't boot after harddrive replacement

On Sun, 11 May 2014 22:38:20 +0300 Itay Furman wrote: > mount point /proc does not exist [Note: similar errors for few more > missing mount points such as /usr/local, /cache] > > special device /dev/sda1 does not exist [Note: that's the would be > /boot partition] > > special device /dev/mappe

Re: Can't boot after harddrive replacement

On Sun, 11 May 2014 22:38:20 +0300 Itay Furman wrote: > > > I guess the output of mount above shows that there is a problem with > the file system(s) and devices. > > Nevertheless, I also believe that I have problems with the bootloader. When you boot the installation DVD, there is an option '

Re: Can't boot after harddrive replacement

On Sun, May 11, 2014, at 06:04 PM, Steve Litt wrote: > On Sun, 11 May 2014 11:46:25 +0300 > Itay wrote: > > > Hi > > > > > > > > Old disk was 300GB and failing. New is 1TB. > > > > I replaced the old harddrive and made few steps to copy the system > > back to the new drive (see belo

Re: Can't boot after harddrive replacement

On Sun, May 11, 2014, at 02:40 PM, Eduardo M KALINOWSKI wrote: On 05/11/2014 05:46 AM, Itay wrote: Old disk was 300GB and failing. New is 1TB. I replaced the old harddrive and made few steps to copy the system back to the new drive (see below). Obviously I missed something as the system does

Re: Can't boot after harddrive replacement

On Sun, 11 May 2014 11:46:25 +0300 Itay wrote: > Hi > > > > Old disk was 300GB and failing. New is 1TB. > > I replaced the old harddrive and made few steps to copy the system > back to the new drive (see below). > > Obviously I missed something as the system does not boot. BIOS comes > up

Re: Can't boot after harddrive replacement

On 05/11/2014 05:46 AM, Itay wrote: > Old disk was 300GB and failing. New is 1TB. > I replaced the old harddrive and made few steps to copy the system > back to the new drive (see below). > Obviously I missed something as the system does not boot. BIOS comes > up alright. > > > I guess that I o

Re: Can't boot after harddrive replacement

On Sun, May 11, 2014, at 01:39 PM, Joel Rees wrote: > On Sun, May 11, 2014 at 7:29 PM, Itay wrote: [snip] > > Indeed I had grub2 installed. > > Given that I repopulated the new disk manually, by a series of rsync > > commands, I suspect that I failed copying some of the critical boot > > data.

Re: Can't boot after harddrive replacement

On Sun, May 11, 2014 at 7:29 PM, Itay wrote: > > On Sun, May 11, 2014, at 01:03 PM, Hans-J. Ullrich wrote: >> Hi Itay, >> >> maybe it is a problem with the UUID. Just check on the new harddrive the >> file >> /etc/fstab, if there is an UUID set for the harddrive. >> > [snip] >> >> Comment ALL lin

Re: Can't boot after harddrive replacement

On Sun, May 11, 2014, at 01:03 PM, Hans-J. Ullrich wrote: > Hi Itay, > > maybe it is a problem with the UUID. Just check on the new harddrive the > file > /etc/fstab, if there is an UUID set for the harddrive. > [snip] > > Comment ALL lines beginning with UUID= and add the physical partition >

Re: Can't boot after harddrive replacement

Hi Itay, maybe it is a problem with the UUID. Just check on the new harddrive the file /etc/fstab, if there is an UUID set for the harddrive. If so, comment it out and set just an entry with /dev/sda1 (or whatever) fpor the required. Here is an example: # /dev/sda7 / ext3

Can't boot after harddrive replacement

Hi Old disk was 300GB and failing. New is 1TB. I replaced the old harddrive and made few steps to copy the system back to the new drive (see below). Obviously I missed something as the system does not boot. BIOS comes up alright. I'd appreciate any help in identifying what needs to be don

Re: Can't boot into MS Windows partition

On Tue, 17 Jul 2012 19:06:34 +0100 Brian wrote: ... > GRUB legacy, which is what you are using, was abandonned five years ago. 'Abandoned' is perhaps a bit strong: "GRUB Legacy is not actively developed any longer. Only bugfixes will be made so that GRUB Legacy can stil be used for older syste

Re: Can't boot into MS Windows partition

On 07/17/2012 02:06 PM, Brian wrote: On Tue 17 Jul 2012 at 15:21:42 +, Rodolfo Medina wrote: The first partition of my second hard disk (/dev/sdb1) is occupied by Windows XP. It is and old install and I haven't booted into it for a couple of years. A Lenny install? Older? (I seem to rem

[solved] Re: Can't boot into MS Windows partition

On 17 July 2012 16:21, Rodolfo Medina wrote: >> The first partition of my second hard disk (/dev/sdb1) is occupied by >> Windows XP. It is and old install and I haven't booted into it for a couple >> of years. (I seem to remember that, when I installed Debian on the actual >> first hd (/dev/sda

Re: Can't boot into MS Windows partition

On Tue 17 Jul 2012 at 15:21:42 +, Rodolfo Medina wrote: > The first partition of my second hard disk (/dev/sdb1) is occupied by Windows > XP. It is and old install and I haven't booted into it for a couple of years. A Lenny install? Older? > (I seem to remember that, when I installed Debian

Re: Can't boot into MS Windows partition

- Original Message - > From: Rodolfo Medina > To: debian-user@lists.debian.org > Cc: > Sent: Tuesday, July 17, 2012 8:21 AM > Subject: Can't boot into MS Windows partition > >T he first partition of my second hard disk (/dev/sdb1) is occupied by Windows > X

Re: Can't boot into MS Windows partition

On Tue, 17 Jul 2012 15:21:42 +, Rodolfo Medina wrote: > The first partition of my second hard disk (/dev/sdb1) is occupied by > Windows XP. It is and old install and I haven't booted into it for a > couple of years. (I seem to remember that, when I installed Debian on > the actual first hd (/

Can't boot into MS Windows partition

The first partition of my second hard disk (/dev/sdb1) is occupied by Windows XP. It is and old install and I haven't booted into it for a couple of years. (I seem to remember that, when I installed Debian on the actual first hd (/dev/sda1), I had momentarily put the other hd off, but am not sure.

Re: qemu KVM: can't boot a qemu machine with liveCD (system rescue)

Ekkard Gerlach writes: > How can I boot a qemu machine with liveCD (system rescue)? I think you can try: kvm -cdrom /dev/sr0 *without* mounting the CD before. Make sure you are root or in the ‘cdrom’ group. -- Alberto -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with

Re: qemu KVM: can't boot a qemu machine with liveCD (system rescue)

h the KVM lists:- http://www.linux-kvm.org/page/Lists%2C_IRC > > My problem is: I can't boot a qemu machine with liveCD (system rescue) > > > root@squeeze64:~# virsh start suse111 > error: failed to get domain 'suse111' > error: Domain not found: no domain

Re: qemu KVM: can't boot a qemu machine with liveCD (system rescue)

On Tue, Jan 03, 2012 at 11:09:06AM +0100, Ekkard Gerlach wrote: > Hi, > > there is no special forum/mailinglist existing for qemu-KVM, right? I do not know the answer but have you read: http://wiki.debian.org/KVM http://wiki.debian.org/QEMU and links from there. Good luck. Osamu --

qemu KVM: can't boot a qemu machine with liveCD (system rescue)

Hi, there is no special forum/mailinglist existing for qemu-KVM, right? My problem is: I can't boot a qemu machine with liveCD (system rescue) I inserted hvm into xml-File but the appearing menu at boot time: Press F12 for boot menu. (I presse

Re: Can't boot live DVD Debian 6, KDE, 1GB

On Mon, 21 Mar 2011 11:26 -0700, "Csaba Kormendy" wrote: > Dave, > > As a side note, I have no idea what your root problem might be. The > "without hard drive" suggestion came to mind as I have recently been > experimenting with Debian by booting from a USB thumb drive on a bare > motherboard

Re: Can't boot live DVD Debian 6, KDE, 1GB

On 03/21/2011 10:18 AM, dave boland wrote: > When I use a Debian based live cd (Debian, Ubuntu, Mepis, etc.) the cd > starts and displays the options for the cd. Thus, I would conclude that > initrd worked as designed. Am I correct on this? No. The boot loader works. The scripts contained within

Re: Can't boot live DVD Debian 6, KDE, 1GB

Daniel, When I use a Debian based live cd (Debian, Ubuntu, Mepis, etc.) the cd starts and displays the options for the cd. Thus, I would conclude that initrd worked as designed. Am I correct on this? Beyond that point is one about good programming. I do work for data acquisition systems, and w

Re: [SOLVED] Can't boot 2.6.32-3 after running 2.6.32-5 for a while

On Jo, 24 iun 10, 06:53:08, Stephen Powell wrote: [...] > device; and the boot process hung. The solution was to use a > direct specification of the UUID in /etc/lilo.conf instead of an > indirect one via a udev symbolic link. For example, instead of > specifying > >root=/dev/disk/by-uuid/

[SOLVED] Can't boot 2.6.32-3 after running 2.6.32-5 for a while

On Wed, 23 Jun 2010 18:05:49 -0400 (EDT), Camaleón wrote: > > I'm interested in seeing how your testing goes. OK, I found the problem. It's a user error, but not an obvious one. Here's the deal. At boot loader install time, lilo translates the root device specification into a number. In the ge

Re: Can't boot 2.6.32-3 after running 2.6.32-5 for a while

On Wed, 23 Jun 2010 15:42:42 -0400, Stephen Powell wrote: > On Wed, 23 Jun 2010 14:20:07 -0400 (EDT), Camaleón wrote: >> How is that? Can't LiLo manage a multiboot menu or is a personal >> configuration? :-? > > Of course it can. But the only thing that differs between the two > kernels is the

Re: Can't boot 2.6.32-3 after running 2.6.32-5 for a while

On Wed, 23 Jun 2010 14:20:07 -0400 (EDT), Camaleón wrote: > On Wed, 23 Jun 2010 14:04:53 -0400, Stephen Powell wrote: >> On Wed, 23 Jun 2010 13:33:16 -0400 (EDT), Camaleón wrote: >>> >>> So, all entries in "/etc/lilo.conf" are pointing to "uuid" devices or >>> just the ones loading the "-3" kernel

Re: Can't boot 2.6.32-3 after running 2.6.32-5 for a while

On Wed, Jun 23, 2010 at 2:36 PM, Tom H wrote: > On Wed, Jun 23, 2010 at 1:22 PM, Stephen Powell wrote: >> On Wed, 23 Jun 2010 12:35:50 -0400 (EDT), Tom H wrote: >>> On Wed, Jun 23, 2010 at 11:14 AM, Stephen Powell >>> wrote: ...  I then tried to boot my old kernel (the -3 kernel).

Re: Can't boot 2.6.32-3 after running 2.6.32-5 for a while

On Wed, Jun 23, 2010 at 1:22 PM, Stephen Powell wrote: > On Wed, 23 Jun 2010 12:35:50 -0400 (EDT), Tom H wrote: >> On Wed, Jun 23, 2010 at 11:14 AM, Stephen Powell >> wrote: >>> ... >>> I then tried to boot my old kernel (the -3 >>> kernel).  It failed.  The kernel and initial RAM file system >>

Re: Can't boot 2.6.32-3 after running 2.6.32-5 for a while

On Wed, 23 Jun 2010 14:04:53 -0400, Stephen Powell wrote: > On Wed, 23 Jun 2010 13:33:16 -0400 (EDT), Camaleón wrote: >> >> So, all entries in "/etc/lilo.conf" are pointing to "uuid" devices or >> just the ones loading the "-3" kernel? > > There are only two lines in /etc/lilo.conf that are rele

Re: Can't boot 2.6.32-3 after running 2.6.32-5 for a while

On Wed, 23 Jun 2010 13:33:16 -0400 (EDT), Camaleón wrote: > > So, all entries in "/etc/lilo.conf" are pointing to "uuid" devices or > just the ones loading the "-3" kernel? There are only two lines in /etc/lilo.conf that are relevant: boot and root. Both are in the global section, not in a per-

Re: Can't boot 2.6.32-3 after running 2.6.32-5 for a while

On Wed, 23 Jun 2010 13:22:11 -0400, Stephen Powell wrote: > On Wed, 23 Jun 2010 12:35:50 -0400 (EDT), Tom H wrote: >> IIUC, linux-image-2.6.32-3-686 uses hdX and linux-image-2.6.32-5-686 >> uses sdX so wouldn't your update-initramfs have updated your >> linux-image-2.6.32-3-686 initrd with sdX de

Re: Can't boot 2.6.32-3 after running 2.6.32-5 for a while

On Wed, 23 Jun 2010 12:35:50 -0400 (EDT), Tom H wrote: > On Wed, Jun 23, 2010 at 11:14 AM, Stephen Powell wrote: >> ... >> I then tried to boot my old kernel (the -3 >> kernel).  It failed.  The kernel and initial RAM file system >> were loaded just fine by the boot loader, but the -3 kernel >> co

Re: Can't boot 2.6.32-3 after running 2.6.32-5 for a while

On Wed, Jun 23, 2010 at 11:14 AM, Stephen Powell wrote: > OK, I'm sure it must be something simple, but I can't figure out what. > > I am running the "testing" release (Squeeze). > I have two stock Debian kernels installed on my system: > linux-image-2.6.32-3-686 and linux-image-2.6.32-5-686. > My

Can't boot 2.6.32-3 after running 2.6.32-5 for a while

OK, I'm sure it must be something simple, but I can't figure out what. I am running the "testing" release (Squeeze). I have two stock Debian kernels installed on my system: linux-image-2.6.32-3-686 and linux-image-2.6.32-5-686. My computer has a single hard disk, a traditional ATA IDE drive, also

Re: grb2 can't boot my ext4 partition

On 06/20/2010 06:49 PM, Huang, Tao wrote: On Sun, Jun 20, 2010 at 11:50 PM, mess-mate wrote: i've squeeze and lenny installed and squeeze as a production system now. Recently installed grub2 (1.98) on squeeze on the MBR of hd0. Evereting goes well but i can't boot lenny. The

Re: grb2 can't boot my ext4 partition

On Sun, Jun 20, 2010 at 11:50 PM, mess-mate wrote: > i've squeeze and lenny installed and squeeze as a production system now. > Recently installed grub2 (1.98) on squeeze on the MBR of hd0. > Evereting goes well but i can't  boot lenny. > The lenny file system partitions

grb2 can't boot my ext4 partition

i've squeeze and lenny installed and squeeze as a production system now. Recently installed grub2 (1.98) on squeeze on the MBR of hd0. Evereting goes well but i can't boot lenny. The lenny file system partitions are for /boot ext3 and all others ext4. When i try to boot lenny i have

Re: apt-get dist-update failure - can't boot

On Mon, May 03, 2010 at 12:59:38PM -0500, Boyd Stephen Smith Jr. wrote: > On Monday 03 May 2010 12:34:13 Fernando B. Scussel wrote: > > http://i4.photobucket.com/albums/y116/fscussel/Untitled.jpg > > Ugh. Does copy and paste not work for you? It would be much nicer if that > text was in the em

Re: apt-get dist-update failure - can't boot

Robert Brockway wrote: On Mon, 3 May 2010, Boyd Stephen Smith Jr. wrote: If a full-upgrade (previously known as dist-upgrade) throws errors, the last thing you should do is reboot. You should *fix the errors*; your system may not reboot cleanly until they are resolved. Well said. Rebootin

Re: apt-get dist-update failure - can't boot

apt-get dist-update failure - can't boot Boyd Stephen Smith Jr. wrote: From you output it looks like your 'perl-base' is scheduled to be upgraded. You should try installing the new version of that package with dpkg and then retrying your apt-get/aptitude run. It's worth a

Re: apt-get dist-update failure - can't boot

On Mon, 3 May 2010, Boyd Stephen Smith Jr. wrote: If a full-upgrade (previously known as dist-upgrade) throws errors, the last thing you should do is reboot. You should *fix the errors*; your system may not reboot cleanly until they are resolved. Well said. Rebooting in the middle of a dist-

Re: apt-get dist-update failure - can't boot

On Monday 03 May 2010 13:36:07 Jimmy Johnson wrote: > Boyd Stephen Smith Jr. wrote: > > From you output it looks like your 'perl-base' is scheduled to be > > upgraded. You should try installing the new version of that package with > > dpkg and then retrying your apt-get/aptitude run. > > It's wort

Re: apt-get dist-update failure - can't boot

Boyd Stephen Smith Jr. wrote: From you output it looks like your 'perl-base' is scheduled to be upgraded. You should try installing the new version of that package with dpkg and then retrying your apt-get/aptitude run. It's worth a shot, depending of if dpkg has not been borked, 'dpkg -i p

Re: apt-get dist-update failure - can't boot

On Monday 03 May 2010 12:34:13 Fernando B. Scussel wrote: > After doing a apt-get dist-update and restarting the pc because of some > errors If a full-upgrade (previously known as dist-upgrade) throws errors, the last thing you should do is reboot. You should *fix the errors*; your system may n

  1   2   3   4   >