Short disk read - HELP please!

From: Shanti Suresh (shanti_at_umich.edu)
Date: 08/27/03

  • Next message: Sundaram Ramasamy: "telnetd error message"
    Date: Wed, 27 Aug 2003 12:11:19 -0400
    To: sunmanagers@sunmanagers.org
    
    

    Hi folks,

    I have an Ultra10 here which was fine until, I believe, a power outage.
    It just won't boot up. Here is a summary of the problem and what I've
    done so far.

    The OpenBoot PROM is version 3.15 on a Sun Ultra10, 360 Mhz machine.
    When I boot the machine, I get:
    -------------
    Short disk read
    failed to read superblock.
    failed to read superblock.
    failed to read superblock.
    Boot load failed.
    The file just loaded does not appear to be executable.
    --------------

    I booted from a Solaris2.6 cdrom.
    I fsck'd the "/" filesystem and it had problems reading sectors 7, 16
    and 17. So I aborted the fsck, used an alternate superblock of 32,
    and got it fsck'd. I then did an "fsck /dev/rdsk/c0t0d0s0" and
    things are fine.

    I am able to boot from CDROM, mount "/" under "/a"
    and things look good. Also, "lost+found" in
    "/a/lost+found" is empty.
    I also did an "installboot", just to be on the safer
    side. I mounted "/" under "/a", also created a clean copy of
    "ufsboot" from cdrom into "/a"(i.e. "/").

    Booting now says the same thing:
    ------------
    Short disk read
    failed to read superblock.
    failed to read superblock.
    failed to read superblock.
    Boot load failed.
    The file just loaded does not appear to be executable.
    ------------
    I booted from the CDROM.
    Ran "format", and saw the priamry drive. It is a
    0. c0t0d0 SEAGATE ST39140A cyl 17660 alt 2 hd 16 sec 63
    (8.49 GB)
    I selected the drive, labelled the drive. Rebooted.

    Same errors as in the beginning, starting with "Short disk read"
    and ending with "The file just loaded does not appear to be executable".

    The superblock is really not bad, at least as reported by "fsck", and
    "lost+found" being empty. So "Short disk read" is what the problem is.
    My "/" partition is only 100MB.

    Oh, and I also checked the device alias for "disk" and the
    OpenBoot parameter for "boot-device". They both look good.

    Luckily, I was able to read the "/" filesystem when mounted under "/a".
    So maybe I backuped it up that way onto another partition.

    Since I wanted to upgrade the machine to Solaris2.8,
    I reloaded the Solaris2.8 Operating System onto the hard-drive. The
    "initial install" formatted the drive fine and loaded the Core operating
    system. However, on a manual reboot, I still get the same error
    messages starting with "Short disk read" and ending with "The file
    just loaded does not appear to be executable". This time, two sets
    of these messages.

    I'm wondering what else I can try. I've got to get this done quick
    to make a few people here happy. So any help would be great.

    Thanks.

                                                         -Shanti

    -- 
    Shanti Suresh
    E-mail: shanti@umich.edu
    IT Communications Services
    Information Technology Central Services
    University Of Michigan
    _______________________________________________
    sunmanagers mailing list
    sunmanagers@sunmanagers.org
    http://www.sunmanagers.org/mailman/listinfo/sunmanagers
    

  • Next message: Sundaram Ramasamy: "telnetd error message"

    Relevant Pages

    • SUMMARY: Short disk read
      ... Solaris7 11/99 CD-ROM may fail to boot or mount ... Booting from CDROM repartition the disk. ... Run the install boot procedure if needed. ... failed to read superblock. ...
      (SunManagers)
    • ext3 & bad blocks error
      ... I was doing some update of system files last week. ... I am not able to boot the 2.6.13.4 kernel ... filesystem, then the superblock is corrupt, and you ... No I have tried fsck -c /dev/hda6 but this device ...
      (Debian-User)
    • SUMMARY: Solaris 10 u4, unable to mount / rw
      ... So, I did "boot cdrom -s" at the OK, then ... The disk is in slot 0. ... I can boot cdrom and fsck the boot disk just fine. ... WARNING - Unable to repair the / filesystem. ...
      (SunManagers)
    • Re: Strange "... read-only file system ..." on SUSE 10.1
      ... Aborting journal on device hda5. ... Boot a live CD and run fsck. ... As it's reporting a bad block, it looks like your disk might be on the way ... Run fsck -c -y on each partition when you can afford the downtime. ...
      (comp.os.linux.misc)
    • Re: very bad situation
      ... Get a bootable CD distribution such as Knoppix and boot it. ... Use the live CD and run fsck from that; make sure that the problems are fixed ... And mount up a new disk and copy the bad one onto it and trash the bad one as soon as you can. ...
      (comp.os.linux.setup)