Error message during boot

Login or Register to Reply

Thread Tools Search this Thread
# 9  
I also (think I) remember that, when booting from CD/DVD or floppy, the kernel creates a device node 'hd0root' to point to any hard disk root filesystem. Therefore to take a look around from CD booted maintenance mode you can:

 # mount /dev/hd0root /mnt
 # cd /mnt
 # ls

Obviously to umount that you would:

 # cd /
 # umount /dev/hd0root  (or # umount /mnt)

Without hd0root mounted (of course) you can:

# fsck -n /dev/hd0root

to see any damage to the hd root filesystem.

Hope that helps.

Last edited by hicksd8; 10-16-2017 at 09:51 AM.. Reason: factual correction
# 10  
Originally Posted by bill szabo
does have floppy drive which I have never used and do have 'boot' no 'root" disk- tried booting with floppy after powering down - system steps right around the floppy drive though it floopy is showing in setup and is first in the boot sequence - my guess is the drives are on scsci controllers and may not see the floppy- checking my wiring next -do remember switching machines after the hardware had issues - may have led to floppy issue.

will use the -n opition as you suggested.
The likelihood of successfully booting from a diskette is very low. I went through this process recently, and was unable to create a btld diskette for 5.0.5. I ended up calling one of the diskette manufacturers and their tech people told be that the life expectancy of a diskette is less than 10 years, and that they stopped manufacturing diskettes more than 10 years ago.
SCSI disks have a write protect jumper.
What I would do, write protect your boot disk, change the scsi id from 0 to 1, get a new/reconditioned disk scsi 0, and do a fresh install on it, Go through the process of adding the original disk as a second disk, and copy the data to the new drive.
When adding the second disk, do not create any new files ystems, and rename the divisions so that they do not conflict with the divisions on drive 0 that have the same names.
This User Gave Thanks to jgt For This Post:
# 11  
I would buy 2 drives, one to load the new OS and the second to create a duplicate after everything is cleaned up so this doesn't happen again.

Fortunately I haven't had to do this in probably 10 years but JGT's suggested way works well. I simplify things for recovery by keeping the boot drive clean and putting data/programs on a separate drive and use another drive as the destination for backups.
# 12  
trying to replace diskette with cd rom drive to try use cd - system does recognize new cd rom dirve when booting - not sure which cd I should be trying to use - do not have maintence disk do have install cd - which cd do I need to get to maintence menu
need help not sure where to turn - guys used 10 yrs ago retried on dead!
# 13  
Do you have any working floppy media? The installation CD media usually has images of the first few floppy disks (1.44MB) on the CD. Put the media in a Windows machine and take a look.

Also, I recall that, when at the install screens, at one point you can hit F8 and select "Shell escape" but, unfortunately, it isn't a very powerfull shell and very few commands; although 'mount' is available.
# 14  
The best route is probably that suggested by jgt and do a fresh install onto a spare HDD and then mounting your current disk as a secondary drive. Then you will be able to 'fsck' it, etc.
Login or Register to Reply

Thread Tools Search this Thread
Search this Thread:
Advanced Search

More UNIX and Linux Forum Topics You Might Find Helpful
Problem in displaying message on RHEL6 on EFI during PXE boot
Hi, I am doing PXE boot for RHEL6.4 on EFI and want to display custom messsage before loading vmlinuz and initrd.img, which is not working. boot server side (In case of BIOS client): In /var/lib/tftpboot/default file I am putting the message in below format: SAY hello world boot...... Linux
stage 1 boot failure: error loading hd (40)/boot
hi SCO Unix 5.0.6 doesn't boot due to this problem: not a directory boot not found cannot open stage 1 boot failure: error loading hd (40)/boot Knows someone howto solve it?... SCO
solaris boot problem boot error loading interpreter(misc/krtld)
When I installed the SOLARIS 10 OS first time, the desktop would not start up, this was because of network setup. Reinstalled worked. After a week due to some problem I had to reinstall OS, installation went fine and but when i reboot I get this error. cannot find mis/krtld boot error loading...... Solaris

Featured Tech Videos