Technical article 104781

fsck(ADM) is reporting read errors on block 0 of my root device.

OpenServer 5.0.0OpenServer 5.0.2OpenServer 5.0.4OpenServer 5.0.5OpenServer 5.0.6

Written · Last revised

Problem

I have booted from my emergency floppies following a system
crash and am attempting to clean the root filesystem of the
hard drive.  When I run fsck against /dev/hd0root, I see this
error message:  (reformatted to fit text)

NOTICE: Sdsk unrecoverable error reading scsi disk 0 dev 1/40 (ha=0 id=0 lun=0) block=0 medium error: unrecoverable read error

NOTICE: Sdsk unrecoverable error reading scsi disk 0
        dev 1/40 (ha=0 id=0 lun=0)
block={some other block number}
                      .
                      .
                      .
fsck: cannot determine filesystem type of /dev/hd0root

Cause

Block 0, which contains the masterboot block information for the device, has become unreadable by the host adaptor. (Block 0 is also referred to as the masterboot block.)

Any utility which accesses the hard drive requires the host
adaptor to obtain information about the device from the
masterboot block.  If this block becomes unreadable the host
adaptor will return a read error and the utility will fail.

Further, this drive will no longer boot any operating system as the masterboot block is loaded in by the system ROMS as the first step in the boot sequence.

Solution

As is, the hard drive is no longer usable and should be
replaced.  You may attempt a low-level format from the
host-adaptor BIOS utilities to recover the masterboot block
but this may not be successful.

You may also wish to replace the controller if multiple disks fail at the same time or also replace the SCSI lead connecting those drives.

You may also wish to upgrade the firmware of the disks, controller or operating system driver of the controller used on your server.

If you are able to recover the masterboot block, then you will need to decide if you want to entrust your system data to a device which has already failed at least once.

***NOTE:  According to the SCSI-experts in Technical Support,
it is strongly recommended that if this drive unit fails on
a production machine, you replace the drive with a new unit.

If you decide to replace the hard disk drive, you will need to do a minimal install of the operating system and restore your files from your last successful backup.

See also

boot(HW) man page.  These articles:
"Layout and Explanation of the Masterboot block"
"How to recover from a system crash under SCO UNIX System V/386"
"How to recover root filesystem after crash if backups,
boot/root exist. 4.2"
"Recover root filesystem after crash if backups, boot/root
exist" (OpenServer 5)

From the Xinuos technical article database, record 104781. Reproduced with permission. The original is at www.sco.com/ta/104781, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.