This is a post meant to help anyone who finds his/her system unbootable
- as I did - after updating to the latest version of the testing stream
which comes with a 6.6.13-amd64 kernel.
When I updated last week, my system refused to boot. Checking revealed
that the system-load-modules service wa
Hi
did you solve this? i got this problem, too with qemu 7 and ubuntu 22.04.1
--
--
cordially
Charlie Schindler
+66 9 1083 7897
David composed on 2022-10-19 18:40 (UTC-0400):
> Just a general warning, for anyone who has not noticed, that
> installing the latest kernel (linux-image-5.10.0-19-amd64) on a
> machine with AMD graphics is causing numerous people to
> report boot failures:
> https://bugs.debian.org/cgi-bin/bugre
David wrote:
> Hello list,
>
> Just a general warning, for anyone who has not noticed, that
> installing the latest kernel (linux-image-5.10.0-19-amd64) on a
> machine with AMD graphics is causing numerous people to
> report boot failures:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=10
Hello list,
Just a general warning, for anyone who has not noticed, that
installing the latest kernel (linux-image-5.10.0-19-amd64) on a
machine with AMD graphics is causing numerous people to
report boot failures:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022025
https://bugs.debian.org/
On 10/10/2020 6:25 PM, john doe wrote:
On 10/10/2020 5:10 PM, Charles Curley wrote:
On Sat, 10 Oct 2020 08:06:16 +0200
john doe wrote:
No, I'm not even getting the grub bootloader.
If you aren't even getting to to GRUB, then your problem isn't an
encrypted /boot partition, it's something el
On 10/10/2020 5:10 PM, Charles Curley wrote:
On Sat, 10 Oct 2020 08:06:16 +0200
john doe wrote:
No, I'm not even getting the grub bootloader.
If you aren't even getting to to GRUB, then your problem isn't an
encrypted /boot partition, it's something else. Possibly something you
did in the pr
On Sat, 10 Oct 2020 08:06:16 +0200
john doe wrote:
> No, I'm not even getting the grub bootloader.
If you aren't even getting to to GRUB, then your problem isn't an
encrypted /boot partition, it's something else. Possibly something you
did in the process of encrypting /boot. Possibly a limitatio
On 10/9/2020 9:45 PM, Charles Curley wrote:
On Fri, 9 Oct 2020 19:28:59 +0200
john doe wrote:
Now I would like to encrypt the boot partition,, I can succesfully
encrypt the boot partition.
As soon as I restart the guest, I can no longer access the guest as it
will not boot at all.
Are you no
On Fri, 9 Oct 2020 19:28:59 +0200
john doe wrote:
> Now I would like to encrypt the boot partition,, I can succesfully
> encrypt the boot partition.
> As soon as I restart the guest, I can no longer access the guest as it
> will not boot at all.
Are you not even getting to the grub boot loader?
Debians,
I'm using libvirt with qemu-kvm to install Debian Buster VM with
encrypted lvm.
The installation and booting the guest works fine.
Now I would like to encrypt the boot partition,, I can succesfully
encrypt the boot partition.
As soon as I restart the guest, I can no longer access the gu
On Sun, 26 Jun 2016, Peter Baranyi wrote:
> >> when I turn on my desktop computer (i5 Skylake) with Debian testing,
Ensure you are using the latest BIOS/UEFI. Skylake systems with an old
BIOS are unsupportable and broken. This is always the first thing to
verify when any Skylake-based system beh
Dnia 2016-06-26, nie o godzinie 16:49 +0200, Peter Baranyi pisze:
> thanks, I disabled quiet, I'll check the messages.
>
> It is a new machine, 1-2 months old.
>
> On 23 June 2016 at 21:57, Norbert Kiszka wrote:
> > Dnia 2016-06-23, czw o godzinie 09:14 +0200, Peter Baranyi pisze:
> >> hi,
> >>
thanks, I disabled quiet, I'll check the messages.
It is a new machine, 1-2 months old.
On 23 June 2016 at 21:57, Norbert Kiszka wrote:
> Dnia 2016-06-23, czw o godzinie 09:14 +0200, Peter Baranyi pisze:
>> hi,
>>
>> when I turn on my desktop computer (i5 Skylake) with Debian testing,
>> on the
Dnia 2016-06-23, czw o godzinie 09:14 +0200, Peter Baranyi pisze:
> hi,
>
> when I turn on my desktop computer (i5 Skylake) with Debian testing,
> on the first try it always freezes right after the grub menu. Then
> when I press reset, it always boots correctly. I have one SATA SSD (/,
> /home), o
On Thu, 2016-06-23 at 09:14 +0200, Peter Baranyi wrote:
> hi,
>
> when I turn on my desktop computer (i5 Skylake) with Debian testing,
> on the first try it always freezes right after the grub menu. Then
> when I press reset, it always boots correctly. I have one SATA SSD
> (/,
> /home), one SATA
hi,
when I turn on my desktop computer (i5 Skylake) with Debian testing,
on the first try it always freezes right after the grub menu. Then
when I press reset, it always boots correctly. I have one SATA SSD (/,
/home), one SATA HDD (only storage) and one M2 NVME SSD (not even
mounted, has Windows)
like there is a bug in initramfs-tools.
Peter
-Original Message-
From: Peter McGill [mailto:petermcg...@goco.net]
Sent: August-13-14 12:21 PM
To: 'debian-user@lists.debian.org'
Subject: Boot failure after upgrade to wheezy
I have 2 debian virtual machines running under Windo
t of built-in commands.
/bin/sh: can't access tty; job control turned off
(initramfs)
cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-amd64
root=UUID=8cdd1090-26ac-4767-b975-05fad7d1f554 ro quiet
Adding rootdelay=120 has no effect (other than delaying boot failure...)
root= &
On 2014-07-27 00:48, Brian wrote:
On Sat 26 Jul 2014 at 20:32:32 +0200, Gregor Hoffleit wrote:
I tried different kernels. Same error. Only that the error message
is less specific on 3.2.0 than with 3.1.14: The later always says
"(error -8)".
3.14.1? Please see the date on the link below.
Ob
On Sun 27 Jul 2014 at 10:02:41 +, Curt wrote:
> On 2014-07-26, Brian wrote:
> >
> >dpkg-reconfigure linus-image-3.14-1-686-pae
> > *
> > should put the kernel and initrd in harmony.
> >
>
> * x
>
> (Not a fantastic contribution to the cause, but what the heck.)
On 2014-07-26, Brian wrote:
>
>dpkg-reconfigure linus-image-3.14-1-686-pae
> *
> should put the kernel and initrd in harmony.
>
* x
(Not a fantastic contribution to the cause, but what the heck.)
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
wi
On Sat 26 Jul 2014 at 20:32:32 +0200, Gregor Hoffleit wrote:
> I tried different kernels. Same error. Only that the error message
> is less specific on 3.2.0 than with 3.1.14: The later always says
> "(error -8)".
3.14.1? Please see the date on the link below.
> Obviously the error 8 is for ENOE
Am 26.07.2014 20:49, schrieb Gregor Hoffleit:
> Am 2014-07-26 20:42, schrieb Michael Biebl:
>> Am 26.07.2014 20:32, schrieb Gregor Hoffleit:
>>> Obviously the error 8 is for ENOEXEC - Exec format error. I wonder what
>>> this could mean. The kernel is i386 (686-pae) and /sbin/init is as well
>>> i3
On Sat 26 Jul 2014 at 20:32:32 +0200, Gregor Hoffleit wrote:
> Am 2014-07-26 17:10, schrieb Brian:
> >>I would appreciate any hints!
> >
> >A d-i image such as the netinst one has a rescue mode which could help
> >in any repairs to your machine.
>
> Thanks for the hint. I never realized how capab
Am 2014-07-26 20:42, schrieb Michael Biebl:
Am 26.07.2014 20:32, schrieb Gregor Hoffleit:
Obviously the error 8 is for ENOEXEC - Exec format error. I wonder
what
this could mean. The kernel is i386 (686-pae) and /sbin/init is as
well
i386.
What kind of hardware do you have? Does your process
Am 26.07.2014 20:32, schrieb Gregor Hoffleit:
> Obviously the error 8 is for ENOEXEC - Exec format error. I wonder what
> this could mean. The kernel is i386 (686-pae) and /sbin/init is as well
> i386.
What kind of hardware do you have? Does your processor support PAE?
--
Why is it that all of t
Am 2014-07-26 17:10, schrieb Brian:
I would appreciate any hints!
A d-i image such as the netinst one has a rescue mode which could help
in any repairs to your machine.
Thanks for the hint. I never realized how capable rescue mode is.
But now I'm even more confused.
Whatever I try, I alway
On Sat 26 Jul 2014 at 16:14:15 +0200, Gregor Hoffleit wrote:
> I also tried to add "break=init" to the command line, but it had no
> effect at all.
>
> Also, specifying a different init ("init=/sbin/init.sysvinit") had
> no effect at all.
I think that should be "init=/sbin/init". You could also
My system is running a mix of stable/testing. I managed to upgrade to
systemd, which brought a whole bunch of problems, boot still booted
nevertheless.
But now, somehow, the system is stuck in the very early boot process:
After just 1,5s the system stalls with this error:
...
Failed to execu
On Wed, 25 Jan 2012, Marc Auslander wrote:
To update files that must be correct, one can write a new version,
sync, and then use mv to replace the old with the new version.
The only way to easily do that seems to always call any editor via a script
doing that.
The journal_data option pro
Pierre Frenkiel writes:
> On Tue, 24 Jan 2012, Pierre Frenkiel wrote:
>
>Remains the question "how /etc/modprobe.d/options was corrupted"
>May-be after a power failure, but I thought that this couldn't
>happen with a ext4 file system.
>
The default/normal configuration of ext4 journa
On Tue, 24 Jan 2012, Pierre Frenkiel wrote:
But may-be /etc/modprobe/options is used at kernel upgrade to create
the initrd image. That would explain why the same error occured with
my 2 kernels.
Running dpkg-reconfigure, I checked that this is true
Remains the question "how /etc/modp
On 24/01/12 23:30, Michael Lange wrote:
> Hi,
>
> Thus spoketh Pierre Frenkiel
> unto us on Tue, 24 Jan 2012 13:03:19 +0100 (CET):
>
> (...)
>> ===
>> [3.903186] scsi_mod: '20a' invalid for parameter 'inq_timeout'
>> done
On Tue, 24 Jan 2012, Brian wrote:
GRUB_CMDLINE_LINUX="scsi_mod.inq_timeout=20"
That works. I checked that the value in grub.cfg has precedence, as expected,
over the value in initrd.
It'a a precious help in cas of boot problems.
--
Pierre Frenkiel
--
To UNSUBSCRIBE, email to debian-user-
On Tue 24 Jan 2012 at 18:24:29 +0100, Pierre Frenkiel wrote:
> the quesion is: what to put after GRUB_CMDLINE_LINUX= ?
GRUB_CMDLINE_LINUX="scsi_mod.inq_timeout=20"
Then 'update-grub'.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble?
On Tue, 24 Jan 2012, Brian wrote:
You may already have thought of it but checking the same file on your
system is worthwhile, otherwise the problem may occur again with the
next kernel upgrade.
According all the tests I made /etc/modprobe/options is rewritten by
initrd: just replacing 20a
On Tue, 24 Jan 2012, Brian wrote:
'scsi_mod.inq_timeout=20a' passed to the kernel causes the same behaviour
here too. The parameter should be an integer, of course.
That is obvious, but what is not obvious is where this 20a comes
from! that looks like a bug in the kernel upgrade procedure
On Tue 24 Jan 2012 at 15:02:48 +0100, Pierre Frenkiel wrote:
> hi Michael,
> Thank you for your quick answer.
> You were right: in the unpacked /etc/modprobe.d directory, the options file
> contained:
> options scsi_mod inq_timeout=20a
> After replacing 20a with 20, I rebuilt the in
On Tue 24 Jan 2012 at 13:30:08 +0100, Michael Lange wrote:
> so apparently it's the "20a" that is passed as 'inq_timeout' to scsi_mod
> that makes insmod scsi_mod fail and so the disk is not recognized.
'scsi_mod.inq_timeout=20a' passed to the kernel causes the same behaviour
here too. The parame
On Tue, 24 Jan 2012, Brian wrote:
Did these entries boot prior to yesterday?
hi Brian,
it was the first reboot after a kernel upgrade
it's fixed now (cf my previous post)
My understanding is that mails with attachments are not blocked. You
could try again in your next mail by attaching
On Tue, 24 Jan 2012, Michael Lange wrote:
If it is not grub, it must be something in the initrd; I would try to
unpack the initrd with
hi Michael,
Thank you for your quick answer.
You were right: in the unpacked /etc/modprobe.d directory, the options file
contained:
options scsi_m
On Tue 24 Jan 2012 at 13:03:19 +0100, Pierre Frenkiel wrote:
> I had yesterday a very big boot problem:
> after choosing any linux entry in the grub boot menu,
> I got failure messages, and was dropped to a busybox shell
Did these entries boot prior to yesterday?
> I sent a post 1 hour ago wi
Hi,
Thus spoketh Pierre Frenkiel
unto us on Tue, 24 Jan 2012 13:03:19 +0100 (CET):
(...)
> ===
> [3.903186] scsi_mod: '20a' invalid for parameter 'inq_timeout'
> done
> Gave up waiting for root device. Common problem
hi,
I had yesterday a very big boot problem:
after choosing any linux entry in the grub boot menu,
I got failure messages, and was dropped to a busybox shell
I sent a post 1 hour ago with an attachment showing these messages
but it didn't reach the list (I thought that small attached files
w
Sven:
On Sun, Jan 01, 2012 at 11:29:51AM +0100, Sven Joachim wrote:
> On 2011-12-31 21:41 +0100, Dean Allen Provins, P. Geoph. wrote:
>
> > On Sat, Dec 31, 2011 at 04:41:11PM +0100, Sven Joachim wrote:
---snip---
> It is essential to find out why it does not work. You might want to try
> my sugg
On Tue, 2012-01-03 at 08:53 -0600, hvw59601 wrote:
[...]
>
> I had a hang: blank screen w/o the "Loading..." message. Waited a few
> secs. and hit the reset button.
>
> Hugo
>
>
No messages at all?
My machine has now booted 3 times without issue since I disconnected the
IDE drives, the last
Steven wrote:
On Sun, 2012-01-01 at 19:02 -0600, hvw59601 wrote:
[...]
But shouldn't it fail all the time then?
Not if it's a race condition of some sorts, which is quote possible, see
below.
Since I turned off 'quiet' it
hasn't failed yet...
Mine has, just now, I had to reset, second tim
On Sun, 2012-01-01 at 19:02 -0600, hvw59601 wrote:
[...]
>
> But shouldn't it fail all the time then?
Not if it's a race condition of some sorts, which is quote possible, see
below.
> Since I turned off 'quiet' it
> hasn't failed yet...
Mine has, just now, I had to reset, second time I turned
Steven wrote:
On Sun, 2012-01-01 at 08:04 -0600, hvw59601 wrote:
[*snip*]
This is a desktop with an Asus
M4N98TD EVO mobo, 4GB mem, 4 HDD's. No messages anywhere about the hang.
I have an Asus as well, P8H67, but this also happened with the previous
board, a MSI P45 Diamond, but not until ove
On Sun, 2012-01-01 at 08:04 -0600, hvw59601 wrote:
[*snip*]
> This is a desktop with an Asus
> M4N98TD EVO mobo, 4GB mem, 4 HDD's. No messages anywhere about the hang.
I have an Asus as well, P8H67, but this also happened with the previous
board, a MSI P45 Diamond, but not until over a year afte
Sven:
I have executed the recommended procedure. I didn't appreciate
the need for the remote login until you explained the purpose -
sorry for the delay.
On Sun, Jan 01, 2012 at 11:29:51AM +0100, Sven Joachim wrote:
> On 2011-12-31 21:41 +0100, Dean Allen Provins, P. Geoph. wrote:
>
> > On Sa
On 2012-01-01 18:11 +0100, Camaleón wrote:
> On Sun, 01 Jan 2012 17:57:09 +0100, Sven Joachim wrote:
>
>> On 2012-01-01 17:46 +0100, Camaleón wrote:
>>
>>> On Sun, 01 Jan 2012 17:20:25 +0100, Sven Joachim wrote:
>>>
On 2012-01-01 15:33 +0100, Camaleón wrote:
> On Sun, 01 Jan 2012 1
On Sun, 01 Jan 2012 17:57:09 +0100, Sven Joachim wrote:
> On 2012-01-01 17:46 +0100, Camaleón wrote:
>
>> On Sun, 01 Jan 2012 17:20:25 +0100, Sven Joachim wrote:
>>
>>> On 2012-01-01 15:33 +0100, Camaleón wrote:
>>>
On Sun, 01 Jan 2012 11:29:51 +0100, Sven Joachim wrote:
> On 2011-
On 2012-01-01 17:46 +0100, Camaleón wrote:
> On Sun, 01 Jan 2012 17:20:25 +0100, Sven Joachim wrote:
>
>> On 2012-01-01 15:33 +0100, Camaleón wrote:
>>
>>> On Sun, 01 Jan 2012 11:29:51 +0100, Sven Joachim wrote:
>>>
On 2011-12-31 21:41 +0100, Dean Allen Provins, P. Geoph. wrote:
T
On Sun, 01 Jan 2012 17:20:25 +0100, Sven Joachim wrote:
> On 2012-01-01 15:33 +0100, Camaleón wrote:
>
>> On Sun, 01 Jan 2012 11:29:51 +0100, Sven Joachim wrote:
>>
>>> On 2011-12-31 21:41 +0100, Dean Allen Provins, P. Geoph. wrote:
>>>
>>> That's why I suggested to log in from a second computer
On 2012-01-01 15:33 +0100, Camaleón wrote:
> On Sun, 01 Jan 2012 11:29:51 +0100, Sven Joachim wrote:
>
>> On 2011-12-31 21:41 +0100, Dean Allen Provins, P. Geoph. wrote:
>>
>> That's why I suggested to log in from a second computer via ssh. It's
>> hard to do anything with a blank screen.
>
> I
Steven wrote:
Hi list,
First of all Happy New Year.
I'm running Debian Wheezy and the past month I have this strange problem
when doing a cold boot. The system hangs right after the GRUB2 selection
menu, before any md raid arrays have been started.
After the GRUB2 selection menu the screen only
On Sun, 01 Jan 2012 14:09:30 +0100, Steven wrote:
> First of all Happy New Year.
Same to you :-)
> I'm running Debian Wheezy and the past month I have this strange problem
> when doing a cold boot. The system hangs right after the GRUB2 selection
> menu, before any md raid arrays have been start
On Sun, 01 Jan 2012 11:29:51 +0100, Sven Joachim wrote:
> On 2011-12-31 21:41 +0100, Dean Allen Provins, P. Geoph. wrote:
>
>> On Sat, Dec 31, 2011 at 04:41:11PM +0100, Sven Joachim wrote:
>>>
>>> That should work around the problem. If possible, use a second
>>> machine to log in via ssh and r
Steven wrote:
Hi list,
First of all Happy New Year.
I'm running Debian Wheezy and the past month I have this strange problem
when doing a cold boot. The system hangs right after the GRUB2 selection
menu, before any md raid arrays have been started.
After the GRUB2 selection menu the screen only
Hi list,
First of all Happy New Year.
I'm running Debian Wheezy and the past month I have this strange problem
when doing a cold boot. The system hangs right after the GRUB2 selection
menu, before any md raid arrays have been started.
After the GRUB2 selection menu the screen only displays "Loadi
On 2011-12-31 21:41 +0100, Dean Allen Provins, P. Geoph. wrote:
> On Sat, Dec 31, 2011 at 04:41:11PM +0100, Sven Joachim wrote:
>>
>> That should work around the problem. If possible, use a second machine
>> to log in via ssh and run "rmmod nouveau; modprobe nouveau modeset=1"
>> then.
>
> Apend
Sven and Camaleón:
Thankyou for the replies and suggestions. I have made some
progress. See below.
On Sat, Dec 31, 2011 at 04:41:11PM +0100, Sven Joachim wrote:
> On 2011-12-31 16:31 +0100, Camaleón wrote:
>
> > On Sat, 31 Dec 2011 07:30:30 -0700, Dean Allen Provins, P. Geoph. wrote:
> >
> >>
On 2011-12-31 16:31 +0100, Camaleón wrote:
> On Sat, 31 Dec 2011 07:30:30 -0700, Dean Allen Provins, P. Geoph. wrote:
>
>> My nVidia GeForce 6600 GT card started to act up, so I purchased an
>> inexpensive MSI N210 card (which uses the 210 nVidia chipset). The
>> salesman said I'd be happier with
On Sat, 31 Dec 2011 07:30:30 -0700, Dean Allen Provins, P. Geoph. wrote:
> My nVidia GeForce 6600 GT card started to act up, so I purchased an
> inexpensive MSI N210 card (which uses the 210 nVidia chipset). The
> salesman said I'd be happier with it!
>
> Sadly, after the the initial boot sequenc
Hello:
My nVidia GeForce 6600 GT card started to act up, so I purchased an
inexpensive MSI N210 card (which uses the 210 nVidia chipset).
The salesman said I'd be happier with it!
Sadly, after the the initial boot sequence lines of text (in regular
VGA font) appear, the screen goes blank, and the
Hi all
Successfully loaded the last snapshot of Wheezy without a hitch the second time
after moving the HD to
another SATA port.
Good news for me is that my sound card is fully recognised with kernel 3.0.1.
Which point the finger of why it didn't when upgraded from squeeze at a file
which is not
On Sun, 2011-10-09 at 22:18 +0100, Brian wrote:
> On Sun 09 Oct 2011 at 22:10:19 +0100, richard2 wrote:
>
> > hi
> > It sat at the end of its install wirh a flashind screen with a debiam
> > logo on it, went to a cosole and scrolling seg fault meesage. No
> > keyboard entry possible.
>
> This was
09/10/2011 23:10, richard2 wrote:
> hi
> It sat at the end of its install wirh a flashind screen with a debiam
> logo on it, went to a cosole and scrolling seg fault meesage. No
> keyboard entry possible.
> rebooted got a grub error
> "error hd0,msdos5 read error
> entering rescue mode >
>
> anyth
On Sun 09 Oct 2011 at 22:10:19 +0100, richard2 wrote:
> hi
> It sat at the end of its install wirh a flashind screen with a debiam
> logo on it, went to a cosole and scrolling seg fault meesage. No
> keyboard entry possible.
This was even before you had booted into the new OS?
> rebooted got a g
hi
It sat at the end of its install wirh a flashind screen with a debiam
logo on it, went to a cosole and scrolling seg fault meesage. No
keyboard entry possible.
rebooted got a grub error
"error hd0,msdos5 read error
entering rescue mode >
anything I can do ?
and wth is msdos5 doing with linux ?
Philipp Überbacher writes:
> Excerpts from lee's message of 2011-06-27 20:57:55 +0200:
>
> I'm now at the point where it boots in qemu and via usb-boot from my
> laptop but not in the real hardware. I need to get a serial-to-usb
> adapter to diagnose further, working blind doesn't help a lot...
>
Excerpts from lee's message of 2011-06-27 20:57:55 +0200:
> Philipp Überbacher writes:
>
> > However, after spending many hours on this (thanks phcoder from #grub)
> > it turned out that necessary modules were missing from initramfs.
> > Adding jfs was enough for the system to boot in qemu but no
Philipp Überbacher writes:
> However, after spending many hours on this (thanks phcoder from #grub)
> it turned out that necessary modules were missing from initramfs.
> Adding jfs was enough for the system to boot in qemu but not for the
> real hardware. I've not yet found out what's necessary f
Excerpts from Joe's message of 2011-06-26 21:46:47 +0200:
> On Sun, 26 Jun 2011 18:44:49 +0200
> Philipp Überbacher wrote:
>
> >
> > I tried manual mounting from busybox:
> > mount /dev/sda1 /root
> > fails with Invalid Argument
> >
> > mount -t jfs /dev/sda1 /root
> > fails with No suc
On Sun, 26 Jun 2011 18:44:49 +0200
Philipp Überbacher wrote:
>
> I tried manual mounting from busybox:
> mount /dev/sda1 /root
> fails with Invalid Argument
>
> mount -t jfs /dev/sda1 /root
> fails with No such device
>
> So this is what happens during boot as well. I found a post sugg
Excerpts from Philipp Überbacher's message of 2011-06-26 04:38:27 +0200:
> Excerpts from lee's message of 2011-06-25 22:40:59 +0200:
> > Philipp Überbacher writes:
> >
> > > Excerpts from lee's message of 2011-06-25 20:06:48 +0200:
> > >> Philipp Überbacher writes:
> > >>
> > >> > The system wa
Excerpts from lee's message of 2011-06-25 22:40:59 +0200:
> Philipp Überbacher writes:
>
> > Excerpts from lee's message of 2011-06-25 20:06:48 +0200:
> >> Philipp Überbacher writes:
> >>
> >> > The system waits for the root file system for a while and then
> >> > drops into a shell with the (i
Philipp Überbacher writes:
> Excerpts from lee's message of 2011-06-25 20:06:48 +0200:
>> Philipp Überbacher writes:
>>
>> > The system waits for the root file system for a while and then
>> > drops into a shell with the (initramfs) prompt.
>> >
>> > There's no /dev/sd* or /dev/disk for some re
Excerpts from lee's message of 2011-06-25 20:06:48 +0200:
> Philipp Überbacher writes:
>
> > The system waits for the root file system for a while and then drops
> > into a shell with the (initramfs) prompt.
> >
> > There's no /dev/sd* or /dev/disk for some reason.
>
> A few weeks ago I found th
Philipp Überbacher writes:
> The system waits for the root file system for a while and then drops
> into a shell with the (initramfs) prompt.
>
> There's no /dev/sd* or /dev/disk for some reason.
A few weeks ago I found that I was suddenly unable to boot a
self-compiled kernel after making a cha
Excerpts from Philipp's message of 2011-06-25 15:12:26 +0200:
> Hi there,
> I have a debian server that doesn't boot anymore since I ran
> upgrade-from-grub-legacy. It uses xen. I managed to upgrade to Debian
> 6 and got everything working. Well, a power outage caused my domUs to
> not boot anymore
Hi there,
I have a debian server that doesn't boot anymore since I ran
upgrade-from-grub-legacy. It uses xen. I managed to upgrade to Debian
6 and got everything working. Well, a power outage caused my domUs to
not boot anymore and while trying to deal with that I also figured I
didn't complete the
Never mind. Found it in one of the Linus' post on LKML.
Back in the days when Debian repo had the
linux-image-2.6.30-bpo.2-686_2.6.30-8~bpo50+2_i386.deb kernel, I had
installed on my PC. Now I have installed the current kernel package from
lenny-backports -- linux-image-2.6.32-bpo.5-686_2.6.32-29~bpo50+1_i386.deb.
The problem is that the old 2.6.30 ker
On Mon, May 31, 2010 at 5:42 PM, wrote:
> Thanks for the comments and help.
>
> I have edited /boot/grub/grub.cfg to match my devices by UUID as
> proposed, getting UUIDs from blkid /dev/md{0,1} (previously I run
> blkid -g):
>
> menuentry "Debian GNU/Linux, with Linux 2.6.32-3-686-bigmem" --clas
On Tue, Jun 01, 2010 at 03:31:41AM -0500, Stan Hoeppner wrote:
> d.sastre.med...@gmail.com put forth on 5/30/2010 4:45 PM:
> > On Sun, May 30, 2010 at 02:24:41PM -0500, Stan Hoeppner wrote:
> >> What happens when you use LILO instead of Grub?
> >
> > I haven't tried that yet.
> > [ snip ]
> > But
d.sastre.med...@gmail.com put forth on 5/30/2010 4:45 PM:
> On Sun, May 30, 2010 at 02:24:41PM -0500, Stan Hoeppner wrote:
>> What happens when you use LILO instead of Grub?
>
> I haven't tried that yet.
>
> First thing would be to know if the bootloader is to blame for not
> having a bootable s
d.sastre.med...@gmail.com wrote:
> Thanks for the comments and help.
>
> I have edited /boot/grub/grub.cfg to match my devices by UUID as
> proposed, getting UUIDs from blkid /dev/md{0,1} (previously I run
> blkid -g):
Good.
> It doesn't boot.
Bummer.
> Note a added `rootdelay=15' and removed
Thanks for the comments and help.
I have edited /boot/grub/grub.cfg to match my devices by UUID as
proposed, getting UUIDs from blkid /dev/md{0,1} (previously I run
blkid -g):
menuentry "Debian GNU/Linux, with Linux 2.6.32-3-686-bigmem" --class
debian --class gnu-linux --class gnu --class os {
On Sun, May 30, 2010 at 7:13 AM, wrote:
> On Sat, May 29, 2010 at 05:44:22PM -0400, Tom H wrote:
>> On Sat, May 29, 2010 at 7:06 AM, David Sastre Medina
>> wrote:
>> >
>> > Grub2 is failing to boot a softRAID1 + LVM2 squeeze box.
>> >
>> > r...@sysresccd /root % mdadm --detail /dev/md0
>> > /dev
d.sastre.med...@gmail.com wrote:
> On Sat, May 29, 2010 at 05:44:22PM -0400, Tom H wrote:
>> On Sat, May 29, 2010 at 7:06 AM, David Sastre Medina
>> wrote:
>> >
>> > Grub2 is failing to boot a softRAID1 + LVM2 squeeze box.
I use an equivalent setup and it was all automatically setup
correctly wi
On Sun, May 30, 2010 at 02:24:41PM -0500, Stan Hoeppner wrote:
> What happens when you use LILO instead of Grub?
I haven't tried that yet.
First thing would be to know if the bootloader is to blame for not
having a bootable system. As of now, it would be some timming issues
related to initramfs-
What happens when you use LILO instead of Grub?
d.sastre.med...@gmail.com put forth on 5/30/2010 6:13 AM:
> On Sat, May 29, 2010 at 05:44:22PM -0400, Tom H wrote:
>> On Sat, May 29, 2010 at 7:06 AM, David Sastre Medina
>> wrote:
>>>
>>> Grub2 is failing to boot a softRAID1 + LVM2 squeeze box.
>>>
On Sat, May 29, 2010 at 05:44:22PM -0400, Tom H wrote:
> On Sat, May 29, 2010 at 7:06 AM, David Sastre Medina
> wrote:
> >
> > Grub2 is failing to boot a softRAID1 + LVM2 squeeze box.
> >
> > r...@sysresccd /root % mdadm --detail /dev/md0
> > /dev/md0:
> > ...
> > UUID : 8052f7d4:54a97fb
On Sat, May 29, 2010 at 7:06 AM, David Sastre Medina
wrote:
>
> Grub2 is failing to boot a softRAID1 + LVM2 squeeze box.
> The error is "can't find root_vg-root_lv". After that, it drops me to
> a initrd shell, but my USB keyboard stops working, so I must
> button-reboot.
> There are two kernels i
I think my previous post requires some more info:
I've got three HDs, two of them (twin disks) have two partitions,
one /boot partition (md0) and the other one for LVM filesystems (md1),
where root_vg-root_lv lives (among others). The third disk is unpatitioned,
and has one only lv (var_lv)
So, p
Hello,
Grub2 is failing to boot a softRAID1 + LVM2 squeeze box.
The error is "can't find root_vg-root_lv". After that, it drops me to
a initrd shell, but my USB keyboard stops working, so I must
button-reboot.
There are two kernels installed.
I've attached grub.cfg. It's an automated cfg from upd
On Mon, Jul 13, 2009 at 21:52, lee wrote:
> On Mon, Jul 13, 2009 at 12:04:12PM -0700, Kelly Clowers wrote:
>> On Mon, Jul 13, 2009 at 11:18, Raphael
>> Bossek wrote:
>> > My problem is "Resourse or device busy" at this moment within the initrd
>> > environment afer hparm -z reloaded the partitionta
1 - 100 of 180 matches
Mail list logo
