'Hard error reading fsbn' in 5.1 but not 5.0?

From: Darren Pilgrim (dmp_at_bitfreak.org)
Date: 07/16/03

  • Next message: Sławek Żak: "NFS problem" 
    Date: Wed, 16 Jul 2003 05:16:29 -0700
To: current@freebsd.org

    Just now, my 120GB western digital, immediately upon the mounting of all
    filesystems during startup, made a faint "click", then my screen filled with
    errors of the form:

    ad6: hard error reading fsbn -# of -#--# error=10

    That's not an exact quote, of course, since the messages scrolled by so fast I
    couldn't actually read parts of them. Those # signs are in place of large
    numbers (most were 12-18 digits). This was in 5.1-R, fresh install, in the
    first 15G of the disk, just after having booted into DOS to create some DOS
    partitions after the FreeBSD slice.

    I booted back into 5.0, and am presently writing across the entire disk with
    this command:

    fdisk -I /dev/ad6 && dd if=/dev/zero of=/dev/ad6s1 bs=1m

    At more than 33 minutes into it at 24+MB/sec, there have been no such errors and
    the portion of the disk that was being mounted has already been covered by
    zeros.

    After dd completes/dies, I'm going to try to reproduce the error, but I figured
    I'd bring this up now in case I've tripped over something someone else already
    knows about. I did notice that when I used fdisk(8) to look at the partition
    table, the slice table showed the new DOS slice starting before the end of the
    FreeBSD slice. Assuming that was real overlap, and not harmless output
    screwiness as a result of using two very different fdisks, is it possible for
    such corruption to cause hard read errors?
    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"

  • Next message: Sławek Żak: "NFS problem"

    Relevant Pages

    • Re: 8.0-Beta installation problem -- Unable to find /dev/ad0s1b
      ... I do not enve know how to make "dangerously dedicated" disk, and the 8.0 may do this sliently. ... S1 for DOS ... Label (Unix partitions, failed to find device node /dev/ad0s1b in /dev), ... I encountered such a problem too; was your disk ad0 ...
      (freebsd-current)
    • Re: 8.0-Beta installation problem -- Unable to find /dev/ad0s1b
      ... I do not enve know how to make "dangerously dedicated" disk, and the 8.0 may do this sliently. ... S1 for DOS ... Label (Unix partitions, failed to find device node /dev/ad0s1b in /dev), ... I encountered such a problem too; was your disk ad0 ...
      (freebsd-stable)
    • Re: Move existing system to a larger disk...
      ... > Is there a trick I can use to move an existing system to a larger disk? ... Before leaving the fdisk and bsdlabel screens, ... Do not worry if the bsd partitions are not labelled from *a* to *f* as ... to make your freebsd slice active or use a bootmanager of some kind to ...
      (comp.unix.bsd.freebsd.misc)
    • Re: Partition help
      ... partitions on a disk; the limit is four. ... Third is that DOS, and its tools like FDISK, do not like having more ... arrangement Two primaries; one 2 GB for DOS: ...
      (microsoft.public.windowsxp.general)
    • Re: reinstall windows xp with dos??
      ... Boot from the XP CD, delete the exsisting partitions, create a new partition ... Throw DOS in trash after breaking media. ... > me with my own computer and i had the wrong windows xp installed i have no ... > have the code) but cannot log in to windows to load the disk therefore i ...
      (microsoft.public.windowsxp.general)