ALERT! /dev/hda1 does not exist. Dropping to a shell!
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
My current failure is during boot time, using GRUB version 0.97.
Because I can not copy paste the boot output, I copied some lines which might help me:
Code:
...
Driver 'sr' needs updating - please use bus-type methods
...
Buffer I/O error on device sr0, block 165496
sr 1:0:0:0 [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sr 1:0:0:0 [sr0] Sense Key: Illegal Request [current]
sr 1:0:0:0 [sr0] Add Sense: Illegal made for this track
end_request: I/O error, dev sr0, sector 1323968
The above last section repeat itself several times.
Then it is released and continues
Code:
Begin: Mounting root file system...Begin: Running /scripts/local-top...done
Begin: waiting for root file system...done.
WARNING bootdevice may be renamed. Try root=/dev/sda1
Gave up waiting for boot device. Common problems:
-Boot args (cat/proc/cmdline)
- Check root delay (...)
- Check root (did the system wait for the right device?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/hda1 does not exist. Dropping to a shell!
Now, to complete the information giving hereby, I made the fdisk -l command and got the following:
Code:
LinuxMachine:/home/yona# fdisk -l
Disk /dev/hda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x24a424a3
Device Boot Start End Blocks Id System
/dev/hda1 * 1 9541 76638051 83 Linux
/dev/hda2 9542 9729 1510110 5 Extended
/dev/hda5 9542 9729 1510078+ 82 Linux swap / Solaris
Disk /dev/hdb: 20.5 GB, 20547841536 bytes
255 heads, 63 sectors/track, 2498 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x42607084
Device Boot Start End Blocks Id System
/dev/hdb1 * 1 2388 19181578+ 83 Linux
/dev/hdb2 2389 2498 883575 5 Extended
/dev/hdb5 2389 2498 883543+ 82 Linux swap / Solaris
LinuxMachine:/home/yona#
Begin: Mounting root file system...Begin: Running /scripts/local-top...done
Begin: waiting for root file system...done.
WARNING bootdevice may be renamed. Try root=/dev/sda1
Gave up waiting for boot device. Common problems:
-Boot args (cat/proc/cmdline)
- Check root delay (...)
- Check root (did the system wait for the right device?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/hda1 does not exist. Dropping to a shell!
Did you try this? Seems like the root device gets renamed. Maybe a look at the menu.lst in /boot/grub will clear things up. See what root device is set for the other boot entries.
Quote:
Originally Posted by JonesD1
Code:
...
Driver 'sr' needs updating - please use bus-type methods
...
Buffer I/O error on device sr0, block 165496
sr 1:0:0:0 [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sr 1:0:0:0 [sr0] Sense Key: Illegal Request [current]
sr 1:0:0:0 [sr0] Add Sense: Illegal made for this track
end_request: I/O error, dev sr0, sector 1323968
The above last section repeat itself several times.
There is a kernel option that exactly matches this error message. But dunno where it is.
Regarding your second hint, how can I continue from here?
My bad. Mixed it up with another error message. Here is the extract from make menuconfig
Code:
CONFIG_IDEDISK_MULTI_MODE:
If you get this error, try to say Y here:
hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
hda: set_multmode: error=0x04 { DriveStatusError }
If in doubt, say N.
But I still believe in some io problem. Either the driver for the harddisk controller is not probably loaded or for the filesystem. I'd rather go for the controller.
Did you check on the initrd of the new kernel? Maybe create a new one with mkinitrd or mkinitramfs.
I found the problem.
Yet, I don't don't know how to solve it.
The 'make menuconfig' creates a wrong configuration for my hardware.
Comparing the running kernel .config file versus the new one generated, reveals a missing "CONFIG_BLK_DEV_IDEDISK=m".
The kernel thinks that I have a SATA or a SCSI disk, because I can run the ls shell command after the failure during boot, and it downloads /dev/sda drivers instead of /dev/hda drivers.
I don't really know every peace of HW inside my PC box, weather it uses IDE, ATA, or else. So, I have difficulties in configuring correctly into the menuconfig program. I just know that my disk is surely IDE (it was made in the year 2000).
Is there a simple utility that can advice me what is the minimum configuration elements for my PC?
Since you are booting from a new kernel the issues lie there. If I were in that case my options are these:
1) Get correct specifications of my hardware: user@host-$: lspci
2) Check what modules my quite old bios require but are not built-in to the 2.6.30.3, get them;
3) Recompile the kernel with these required modules;
4) After the kernel is compiled, the proper initrd.img must be compiled using that new kernel: use mkinitrd command and be sure to compile it with *relevant* modules.
5) It appears that you are installing linux into the first partition. So if you install Grub there it will only use Stage 1.5 and is capable of booting ALL systems located in the disk.
Just a side point: your RAM might require a minimalist distro, if you have no plan of replacing or adding more Mbytes try consider Slackware 12.2 or Absolute Linux, although Debian is also good.
Hope it helps.
Goodluck.
Last edited by malekmustaq; 08-22-2009 at 06:50 AM.
Now to your Next advice:
"Check what modules my quite old bios require but are not built-in to the 2.6.30.3, get them"
How am I suppose to know what the 2.6.30.3 is missing for my HW, and how should I download it?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.