DISK BOOT FAILURE

[Debian User]

i am unable to boot from /dev/hda. i have a boot disk and that worked.
i am trying to figure out why i cannot boot from the hard drive.
i have compaired this to a machine that boots but i cannot figure
out what is wrong. help!!

my root filesystem looks like:

server:/# ls
backuphda1 bin dev initrd mnt sbin var
backuphda2 boot etc initrd.img opt server.cfg vmlinuz
backuphda3 cdrom floppy lib proc tmp vmlinuz.old
backuphda5 core.287 home lost+found root usr

my boot file system looks like:

server:/boot# ls -l
total 5074
-rw-r--r-- 1 root root 272725 Jan 31 08:02 System.map-
2.2.20
-rw-r--r-- 1 root root 407266 Apr 14 2002 System.map-
2.4.18-586tsc
-rw-r--r-- 1 root root 7988 Apr 13 2002 boot-bmp.b
-rw-r--r-- 1 root root 6204 Apr 13 2002 boot-compat.b
-rw-r--r-- 1 root root 7964 Apr 13 2002 boot-menu.b
-rw-r--r-- 1 root root 6204 Apr 13 2002 boot-text.b
-rw-r--r-- 1 root root 512 Jan 31 08:37 boot.0300
lrwxrwxrwx 1 root root 11 Jan 31 08:36 boot.b ->
boot-menu.b
-rw-r--r-- 1 root root 728 Apr 13 2002 chain.b
-rw-r--r-- 1 root root 14979 Jan 31 08:02 config-2.2.20
-rw-r--r-- 1 root root 37091 Apr 13 2002 config-2.
4.18-586tsc
-rw-r--r-- 1 root root 2703360 Feb 1 09:43 initrd.img-
2.4.18-586tsc
drwx------ 2 root root 12288 Jan 31 07:56 lost+found
-rw------- 1 root root 49664 Feb 1 09:44 map
-rw-r--r-- 1 root root 656 Apr 13 2002 os2_d.b
-rw-r--r-- 1 root root 1005181 Jan 31 08:02 vmlinuz-2.2.20
-rw-r--r-- 1 root root 626776 Apr 14 2002 vmlinuz-2.
4.18-586tsc


# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump>
<pass>
/dev/hda3 / ext2 errors=remount-ro 0
1
/dev/hda6 none swap sw 0

0
proc /proc proc defaults 0

0
/dev/fd0 /floppy auto user,noauto 0

0
/dev/cdrom /cdrom iso9660 ro,user,noauto 0

0
/dev/hda1 /boot ext2 defaults 0
2
/dev/hda2 /home ext2 defaults 0
2
/dev/hda5 /usr ext2 defaults 0
2
/dev/hdc1 /backuphda1 ext2 defaults 0

0
/dev/hdc2 /backuphda2 ext2 defaults 0

0
/dev/hdc3 /backuphda3 ext2 defaults 0

0
/dev/hdc5 /backuphda5 ext2 defaults 0

0


when i try to mount to the /dev/hdc drive, i get this error:

server:/boot# mount -a
mount: wrong fs type, bad option, bad superblock on /dev/hdc1,
or too many mounted file systems
(could this be the IDE device where you in fact use
ide-scsi so that sr0 or sda or so is needed?)
mount: wrong fs type, bad option, bad superblock on /dev/hdc2,
or too many mounted file systems
(could this be the IDE device where you in fact use
ide-scsi so that sr0 or sda or so is needed?)
mount: wrong fs type, bad option, bad superblock on /dev/hdc3,
or too many mounted file systems
(could this be the IDE device where you in fact use
ide-scsi so that sr0 or sda or so is needed?)
mount: wrong fs type, bad option, bad superblock on /dev/hdc5,
or too many mounted file systems
(could this be the IDE device where you in fact use
ide-scsi so that sr0 or sda or so is needed?)











--
To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

[Debian User]

i have with no success.

fdisk /dev/hdc1 does not see the device. i think there may be two
problems ... the boot on /dev/hda and not seeing the second drive
/dev/hdc

>> when i try to mount to the /dev/hdc drive,

>have you tried to mount them by hand?
><snip>
>The list needs info! Specific error message are best.
>-Kev
>
>--
>To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
>with a subject of "unsubscribe". Trouble? Contact listmaster@lists.

debian.org

>

--
To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

[Kevin Mark]

On Sat, 2003-07-26 at 19:13, Debian User wrote:

> after bios, i think lilo is not ever run. the bios displays the system
> configuration then the error message:
>
> DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS ENTER
>
> my boot sequence is A,C.

IIRC the machine is not seeing the drives properly. Did this happen
after you added the 'backup' drive? Computers use the bios to find the
bootable drive(meaning 'bootable' flag and boot loader), if not found
yours wants a floppy for help which the lilo boot provides. So that
would explain the boot disk working.

>
> the boot floopy i am using is 2.2.20. the machine was booting 2.4.
> 18 ... for months before this problem occured. apparently, i never
> made a boto disk for the 2.4.18 kernel.
>

Not a major problem. This can be fixed after you get this fixed.

> i have not tried re-lilo-ing b/c i am unsure if the problem is a
> bad lilo or not. could this be the problem?
>

I dont think is can hurt, so I think it would be ok. You are only
writing a few bits in a specific place that may have got corrupted. And
you have the boot disk.
<snip>
BUT ON SECOND THOUGHT,
if you set the jumpers on the HD's (single,master,slave) incorrectly...
that would explain alot....
not see the drives on bootup, the BIOS os message, not being able to
mount the second drive.
Just a thought....
-Kev


--
To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

[Debian User]

i'll give lilo another shot. this all happened after a power failure
... my ups didn't do it's job by keeping the line voltage up.

both disks were working fine until the power failure. of course,
this problem could have been there for some time as it was 180 some
odd days since i last reboot this particular machine.

At 26 July 2003, Kevin Mark <kmark@pipeline.com> wrote:

>On Sat, 2003-07-26 at 19:13, Debian User wrote:

>> after bios, i think lilo is not ever run. the bios displays the

system

>> configuration then the error message:
>>
>> DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS ENTER
>>
>> my boot sequence is A,C.

>IIRC the machine is not seeing the drives properly. Did this happen
>after you added the 'backup' drive? Computers use the bios to find the
>bootable drive(meaning 'bootable' flag and boot loader), if not found
>yours wants a floppy for help which the lilo boot provides. So that
>would explain the boot disk working.

>>
>> the boot floopy i am using is 2.2.20. the machine was booting 2.4.
>> 18 ... for months before this problem occured. apparently, i never
>> made a boto disk for the 2.4.18 kernel.
>>

>Not a major problem. This can be fixed after you get this fixed.

>> i have not tried re-lilo-ing b/c i am unsure if the problem is a
>> bad lilo or not. could this be the problem?
>>

>I dont think is can hurt, so I think it would be ok. You are only
>writing a few bits in a specific place that may have got corrupted. And
>you have the boot disk.
><snip>
>BUT ON SECOND THOUGHT,
>if you set the jumpers on the HD's (single,master,slave) incorrectly.

..

>that would explain alot....
>not see the drives on bootup, the BIOS os message, not being able to
>mount the second drive.
>Just a thought....
>-Kev
>
>--
>To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
>with a subject of "unsubscribe". Trouble? Contact listmaster@lists.

debian.org

>

--
To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

[Debian User]

bios still sees both drives ... i think the hardware is still working.

i re-lilo-ed without success. I still have to boot from the floopy.

what is IIRC?

At 26 July 2003, Kevin Mark <kmark@pipeline.com> wrote:

>On Sat, 2003-07-26 at 19:13, Debian User wrote:

>> after bios, i think lilo is not ever run. the bios displays the

system

>> configuration then the error message:
>>
>> DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS ENTER
>>
>> my boot sequence is A,C.

>IIRC the machine is not seeing the drives properly. Did this happen
>after you added the 'backup' drive? Computers use the bios to find the
>bootable drive(meaning 'bootable' flag and boot loader), if not found
>yours wants a floppy for help which the lilo boot provides. So that
>would explain the boot disk working.

>>
>> the boot floopy i am using is 2.2.20. the machine was booting 2.4.
>> 18 ... for months before this problem occured. apparently, i never
>> made a boto disk for the 2.4.18 kernel.
>>

>Not a major problem. This can be fixed after you get this fixed.

>> i have not tried re-lilo-ing b/c i am unsure if the problem is a
>> bad lilo or not. could this be the problem?
>>

>I dont think is can hurt, so I think it would be ok. You are only
>writing a few bits in a specific place that may have got corrupted. And
>you have the boot disk.
><snip>
>BUT ON SECOND THOUGHT,
>if you set the jumpers on the HD's (single,master,slave) incorrectly.

..

>that would explain alot....
>not see the drives on bootup, the BIOS os message, not being able to
>mount the second drive.
>Just a thought....
>-Kev
>
>--
>To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
>with a subject of "unsubscribe". Trouble? Contact listmaster@lists.

debian.org

>

--
To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

[Kevin Mark]

On Sun, 2003-07-27 at 18:11, Debian User wrote:

> bios still sees both drives ... i think the hardware is still working.
>
> i re-lilo-ed without success. I still have to boot from the floopy.
>

You finally mention the reason for your OP (original post): your
computer had a power failure. I think that the backup drives is hosed
and that if your remove the drive and change the main drive to 'single'
or 'single/master' mode you will see the problem fixed. That would be my
best guess.

> what is IIRC?

If I Recall Correctly

Other common email abreviations:
OTOH on the other hand
IMHO in my humble opinion
IANAL i am not a lawyer
LOL laugh out loud

>
> At 26 July 2003, Kevin Mark <kmark@pipeline.com> wrote:
>

<snip>
Welcome to the wonder world of debian!
-Kev


--
To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]