-   Slackware (
-   -   Boot error (

michael.barnes 11-02-2012 02:24 PM

Boot error
I've got an ancient Slackware 8.1 machine. It was originally set up with two virtual IP addresses, eth0:1 and eth0:2. I went into /etc/rc.d/rc.inet1 and removed all references to the virtual IPs so it only has eth0 configured. Restarting the network did not remove the virtual IPs so I decided to try a reboot. This machine has not been rebooted in three or four years. Anyhow, on reboot it gets to grub then gives the following error:

kernel (hd0,0)/boot/vimlinuz root=/dev/hda1
error 17: cannot mount selected partition

Looking at the raid configuration utility, it says no errors on any disk. I don't know what do from here to get this thing to boot and get back in service.

Any ideas greatly appreciated.


chemfire 11-03-2012 09:43 AM

Should you get it running aging you can take down an sub interface using

ifconfig <Subint> down
Obviously the machine has a little more history as Slackware 8.1 would be using LILO not grub as the boot loader, ordinarily. Is some other distribution installed on the machine as well? Are you very sure /dev/hda1 is really your slackware root partition and nothing perhaps overwrite the boot loader later?

You mentioned raid and implied some sort of hardware raid controller, which makes me more than a little surprised the partition would be /dev/hda[x], /dev/hd[x] is almost always Plain Jane IDE. Which leads me back to perhaps the boot loader is just wrong? Its also possible you had a "fake" raid controller in the system that would have relied on software for the disk sync most of the time Linux just ignored those and exposed the raw volumes underneath so if was a cheaper IDE raid any settings on the card will be irrelevant.

Back in the 8.x days the second CD image was a bootable live CD. I would advise downloading both the first and second CD ISOs for Slackware 8.1 ( I am sure google can find them) and booting up on the second disk. It give you a chance to poke around with fdisk or cfdisk and find out what is really on those disks in the way of partitions. fsck from the live CD may help as well. You can also try passing the root= argument to the loader on the install CD more instructions for doing that are present on boot loader screen and see if you can fire up the /dev/hda1 partition that way. I would than re-install lilo ( not grub, grub sucks ) from CD 1.

gnashley 11-03-2012 10:00 AM

This sounds like there may be errors on the disk. You might try booting the machine with any LiveCD or slackware install disk and running 'fdisk' on the root partition.

All times are GMT -5. The time now is 06:29 PM.