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
were allowed, but it seems I was wrong)
So, I extracted the more important part.
===============================================================
[ 3.903186] scsi_mod: '20a' invalid for parameter 'inq_timeout'
done
Gave up waiting for root device. Common problems:
- Boot args ...
- check rootdelay=
- check root=
- Missing modules...
ALERT /dev/disk/by-uuid/8f0abe00....... does not exist.
Dropping to a shell
BusyBox ......
....
/bin/sh: ca't access tty: job control turned off
===============================================================
here are some details:
1/ when in busybox, I saw that /dev/disk was missing.
I suppose that's why the root disk is not found at boot,
but I have no idea how this happened.
2/ all internal disks are seen in the BIOS setup
3/ selecting Windows (/dev/sda1) or memtest in the grub menu works
4/ I can boot my linux partition using the Gentoo SystemRescueCd
(command: rescuecd root=/dev/sda2)
and it's how I'm working now.
The situation is almost the same as if I had booted directly from my
internal disc. (except the sound)
As the actual working kernel is the one of the cd:
uname -a ==> 2.6.32.10-std150-i386,
I had just to copy the modules of this kernel to /lib/modules
In particular, /dev/disk has all usual entries(by-uuid ...),
and blkid shows all my disks, including /dev/sda2
Do anybody see a possible explanation?
--
Pierre Frenkiel
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/alpine.deb.2.00.1201241253290.26...@pfr2.frenkiel-hure.net
