Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 22 Feb 2007 17:56:25 -0500
From:      Jerry McAllister <jerrymc@msu.edu>
To:        Derek Ragona <derek@computinginnovations.com>
Cc:        Marty Landman <martster@gmail.com>, freebsd-questions@freebsd.org
Subject:   Re: input/output error on hd
Message-ID:  <20070222225625.GA21524@gizmo.acns.msu.edu>
In-Reply-To: <6.0.0.22.2.20070222163157.0249d9f8@mail.computinginnovations.com>
References:  <70063950702221419s57a34f05p1bdee62713a67aae@mail.gmail.com> <6.0.0.22.2.20070222163157.0249d9f8@mail.computinginnovations.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Thu, Feb 22, 2007 at 04:34:24PM -0600, Derek Ragona wrote:

> You may have lost the partition table.  You can try repartitioning the 
> drive but do NOT do a newfs.  You can easily try it in sysinstall.

Yes, that has been mentioned - I wasn't sure if it would work as
desired - without overwriting too much - or not.  But, if it is tried
, be sure to use the exact partition schema as was done before.  I 
think that was everything in one partition - called c, but I am not
sure that is exactly what was done.

So, the question is, did the OP use bsdlabel (alone or in sysinstall)
when originally creating that filesystem?   If so, probably using
bsdlabel again on it - WITHOUT doing a newfs - would be worth trying.
It probably can't do anything worse than what is already the case.

If it was all one partition in a single slice, then run bsdlabel -e
on the slice /dev/ad1s1 and take out the unused type from 'c' and
make it BSD4.2.    Make the offset '*' and the size be everything.
Then exit out and hope for the best.

////jerry


> 
>         -Derek
> 
> At 04:19 PM 2/22/2007, Marty Landman wrote:
> >I wrote about this problem before, still working on recovery. After a power
> >outage I lost my primary slave hd, a 250MB Maxtor. Got rebooted ok by
> >editing it out of the fstab i.e.
> >
> >%cat /etc/fstab
> ># Device                Mountpoint      FStype  Options         Dump
> >Pass#
> >/dev/ad0s1b             none            swap    sw              0       0
> >/dev/ad0s1a             /               ufs     rw              1       1
> >...
> >#/dev/ad1s1c            /hoss           ufs     rw              2       2
> >%
> >
> >It's been explained to me that ad1s1c was an inappropriate name for the
> >partition on this drive, will change that after fixing this mess.
> >
> >Here is a problem symptom summary:
> >
> >%sudo mount /dev/ad1s1c /hoss
> >mount: /dev/ad1s1c: Input/output error
> >%sudo mount /dev/ad1s1 /hoss
> >mount: /dev/ad1s1: Input/output error
> >%sudo fsck -f /dev/ad1s1
> >fsck: Could not determine filesystem type
> >%sudo fsck -f /dev/ad1s1c
> >fsck: exec fsck_unused for /dev/ad1s1c in /sbin:/usr/sbin: No such file or
> >directory
> >%
> >
> >Have determined from dd's that there's data on here, wonder though if the
> >power outage caused some permanent damage. Have isolated the errors to
> >blocks 129 through 144:
> >
> >%sudo dd if=/dev/ad1s1 of=/tmp/scratch bs=512 count=1 skip=127
> >1+0 records in
> >1+0 records out
> >512 bytes transferred in 0.008638 secs (59274 bytes/sec)
> >%sudo dd if=/dev/ad1s1 of=/tmp/scratch bs=512 count=1 skip=128
> >dd: /dev/ad1s1: Input/output error
> >0+0 records in
> >0+0 records out
> >0 bytes transferred in 1.315347 secs (0 bytes/sec)
> >... [repeats for skip=129 to skip=142]
> >%sudo dd if=/dev/ad1s1 of=/tmp/scratch bs=512 count=1 skip=143
> >dd: /dev/ad1s1: Input/output error
> >0+0 records in
> >0+0 records out
> >0 bytes transferred in 1.336348 secs (0 bytes/sec)
> >%sudo dd if=/dev/ad1s1 of=/tmp/scratch bs=512 count=1 skip=144
> >1+0 records in
> >1+0 records out
> >512 bytes transferred in 0.018065 secs (28342 bytes/sec)
> >
> >So, I need to know what to do next. Have been looking for pertinant
> >information to learn how to pick apart whatever's keeping my drive for 
> >being
> >mountable and fix manually but either don't know what to look for or 
> >haven't
> >found the right explanation yet.
> >
> >For instance, is it possible if I somehow 'eliminated' blocks 129 through
> >144 that the volume would then mount for me?
> >
> >Any help would be appreciated.
> >
> >
> >Marty
> >
> >
> >--
> >Web Installed Formmail - http://face2interface.com/formINSTal/
> >Webmaster's BBS - http://bbs.face2interface.com/
> >_______________________________________________
> >freebsd-questions@freebsd.org mailing list
> >http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> >To unsubscribe, send any mail to 
> >"freebsd-questions-unsubscribe@freebsd.org"
> >
> >--
> >This message has been scanned for viruses and
> >dangerous content by MailScanner, and is
> >believed to be clean.
> >MailScanner thanks transtec Computers for their support.
> >
> 
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> MailScanner thanks transtec Computers for their support.
> 
> _______________________________________________
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?20070222225625.GA21524>