power outage

From: Mike Spooner (spooner_at_scripps.edu)
Date: 11/28/05

  • Next message: Kris Kennaway: "Re: NFS network load on 5.4-STABLE"
    Date: Mon, 28 Nov 2005 00:05:18 -0800 (PST)
    To: freebsd-stable@freebsd.org
    
    

    I didn't know if I should post this to questions or stable but here it
    is...

    We had a power outage and now /home won't mount. Before the power outage
    all was fine.
    On boot I get the following...
    .
    .
    .
    Starting file system checks:
    /dev/da0s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS
    /dev/da0s1a: clean, 41075 free (587 frags, 5061 blocks, 0.8%
    fragmentation)
    /dev/ad1s1f: DEFER FOR BACKGROUND CHECKING
    /dev/ad1s1e: DEFER FOR BACKGROUND CHECKING
    /dev/da0s1d: DEFER FOR BACKGROUND CHECKING
    /dev/ad1s1d: DEFER FOR BACKGROUND CHECKING
    WARNING: /home was not properly dismounted
    /home: mount pending error: blocks 37920 files 0
    ad1: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=40<UNCORRECTABLE>
    LBA=69103423
    mount: /dev/ad1s1f: Input/output error
    WARNING: /tmp was not properly dismounted
    WARNING: /usr was not properly dismounted
    WARNING: /var was not properly dismounted
    Mounting /etc/fstab filesystems failed, startup aborted
    Boot interrupted
    Enter full pathname...
    #

    At this point all partitions are mounted except /home

    I get the following errors when running fsck

    # fsck /home
    ** /dev/ad1s1f
    ** Last Mounted on /home
    ** Phase 1 - Check Blocks and Sizes
    INCORRECT BLOCK COUNT I=6 (37920 should be 0)
    CORRECT? [yn] y

    ad1: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=40<UNCORRECTABLE>
    LBA=69103423

    CANNOT READ BLK: 54947584
    UNEXPECTED SOFT UPDATE INCONSISTENCY

    CONTINUE? [yn] y

    ad1: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=40<UNCORRECTABLE>
    LBA=69103423
    ad1: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=40<UNCORRECTABLE>
    LBA=69103445
    THE FOLLOWING DISK SECTORS COULD NOT BE READ: 54947584, 54947606,
    fsck_ufs: cannot alloc 3087484824 bytes for inoinfo

    There are two drives on this system (da0 and ad1). There are two other
    partitions on ad1 that mount with no problems and all partitions on da0
    mount with no problems.

    As root I've tried to run sysinstall and the disk label editor to try to
    re-label the partitions on ad1 but when I select W, I get an error saying
    it can't write to ad1.

    Am I S-O-L or can I recover /home from this? If so, how?

    The system is running 5.3-RELEASE-p18

    Thanks

    _______________________________________________
    freebsd-stable@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-stable
    To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"


  • Next message: Kris Kennaway: "Re: NFS network load on 5.4-STABLE"

    Relevant Pages

    • SVM Mirror jumpstart problem with Solaris 9 9/05
      ... I am trying to jumpstart an E3500 with Solaris 9 9/05 and perform the ... WARNING: forceload of misc/md_trans failed ... mount: warning: line for "{" in vfstab has too few entries ...
      (comp.unix.solaris)
    • SVM Mirror jumpstart problem with Solaris 9 9/05
      ... I am trying to jumpstart an E3500 with Solaris 9 9/05 and perform the ... WARNING: forceload of misc/md_trans failed ... mount: warning: line for "{" in vfstab has too few entries ...
      (SunManagers)
    • RE: [SLE] cifs mounts
      ... WARNING: ... CIFS mount option 'dmask' is deprecated. ...
      (SuSE)
    • Re: Mounting dirty ext3 partition
      ... > I have a hard drivethat was taken from a linux machine that just ... WARNING: mount of ad3s1 denied due to unsupported optional features ...
      (comp.unix.bsd.freebsd.misc)
    • kernel BUG at drivers/scsi/scsi_lib.c:544
      ... I hit this bug when trying to mount a md multipath device. ... Warning: You did not tell me where to find symbol information. ... map, modules, ksyms etc. ksymoops -h explains the options. ...
      (Linux-Kernel)