As a follow up to the previous thread on which I was the OP have followed
the advice given, contacted Ian Dowse who kindly walked me through fixing my
hard drive. Here is a synopsis as best as I can do to explain what was done:
First find out the offsets of the bad sectors, and check with dd that
On 2/26/07, Jerry McAllister <[EMAIL PROTECTED]> wrote:
On Mon, Feb 26, 2007 at 04:49:46PM +1100, Ian Smith wrote:
>
> Firstly, Marty, you should run dumpfs(8) on your ad1s1a.
Well this didn't raise my spirits too much:
%sudo dumpfs /dev/ad1s1a
dumpfs: /dev/ad1s1a: could not read superblock
On Mon, Feb 26, 2007 at 04:49:46PM +1100, Ian Smith wrote:
> On Sun, 25 Feb 2007, Jerry McAllister wrote:
> > On Sun, Feb 25, 2007 at 10:38:01AM -0500, Marty Landman wrote:
> >
> > > On 2/24/07, Jerry McAllister <[EMAIL PROTECTED]> wrote:
> > > >
> > > >
> > > >Well, I think you are past an
On Sun, 25 Feb 2007, Jerry McAllister wrote:
> On Sun, Feb 25, 2007 at 10:38:01AM -0500, Marty Landman wrote:
>
> > On 2/24/07, Jerry McAllister <[EMAIL PROTECTED]> wrote:
> > >
> > >
> > >Well, I think you are past any label problems now and on to the
> > >bad sectors and/or finding superb
On Sun, Feb 25, 2007 at 10:38:01AM -0500, Marty Landman wrote:
> On 2/24/07, Jerry McAllister <[EMAIL PROTECTED]> wrote:
> >
> >
> >Well, I think you are past any label problems now and on to the
> >bad sectors and/or finding superbocks.Although I am not quite clear
> >from above what resulted
On 2/24/07, Jerry McAllister <[EMAIL PROTECTED]> wrote:
Well, I think you are past any label problems now and on to the
bad sectors and/or finding superbocks.Although I am not quite clear
from above what resulted in the 'INCOMPLETE LABEL...' message.
Ok then, can you point me to somewhe
On Fri, Feb 23, 2007 at 05:13:37PM -0500, Marty Landman wrote:
> On 2/23/07, Jerry McAllister <[EMAIL PROTECTED]> wrote:
> >
> >
> >I would go back to that bsdlabel ad1s1 and edit the 'a' partition
> >
>
> Also changed the size and offset to match the 'c' partition. Looks like
> progress here b
On Sat, Feb 24, 2007 at 06:12:39PM +1100, Ian Smith wrote:
> On Fri, 23 Feb 2007, Jerry McAllister wrote:
>
> Jerry, just on a couple of points:
>
> Me to Marty:
> > > Does the above result mean that my boot sector is ok?
> >
> > I think maybe you might be getting some of your terminology sh
On Fri, 23 Feb 2007, Jerry McAllister wrote:
Jerry, just on a couple of points:
Me to Marty:
> > Does the above result mean that my boot sector is ok?
>
> I think maybe you might be getting some of your terminology shuffled
> around.Your boot sector is not at question here. It doesn't
On Fri, 23 Feb 2007, Marty Landman wrote:
> On 2/23/07, Ian Smith <[EMAIL PROTECTED]> wrote:
>
> So just show 'fdisk ad1' to see the disk's partition (slice) table (which
> > may be damaged, but it's the only one you're interested in).
>
> %sudo fdisk ad1
> *** Working on device /dev/a
On 2/23/07, Jerry McAllister <[EMAIL PROTECTED]> wrote:
I would go back to that bsdlabel ad1s1 and edit the 'a' partition
Also changed the size and offset to match the 'c' partition. Looks like
progress here but still haven't gotten all the way to a mount as you can
see:
%sudo bsdlabel -
On Fri, Feb 23, 2007 at 11:08:29AM -0500, Marty Landman wrote:
> On 2/23/07, Ian Smith <[EMAIL PROTECTED]> wrote:
>
> So just show 'fdisk ad1' to see the disk's partition (slice) table (which
> >may be damaged, but it's the only one you're interested in).
>
>
> %sudo fdisk ad1
> *** Working
On 2/23/07, Ian Smith <[EMAIL PROTECTED]> wrote:
So just show 'fdisk ad1' to see the disk's partition (slice) table (which
may be damaged, but it's the only one you're interested in).
%sudo fdisk ad1
*** Working on device /dev/ad1 ***
parameters extracted from in-core disklabel are:
c
In freebsd-questions Digest, Vol 166, Issue 12
At Message: 15
On Thu, 22 Feb 2007 18:12:48 -0500 Marty Landman <[EMAIL PROTECTED]> wrote:
> Thanks Derek,
>
> I tried deleting and recreating the one slice on that drive in sysinstall,
> also rewriting the boot label. Didn't seem to help as show
N, this is a 250 GB drive with tons of data (mostly bigger files) on it.
On 2/22/07, Derek Ragona < [EMAIL PROTECTED]> wrote:
Slice names are version dependent. In major releases the names have
changed a bit.
There are a few recovery tools in the ports. You can try those and see if
they
Jerry,
Below is what I see in response to the cmd; as I'm unfamiliar with it could
you please be more explicit about how I may proceed?
Marty
%sudo bsdlabel -e /dev/ad1s1
Password:
# /dev/ad1s1:
8 partitions:
#size offsetfstype [fsize bsize bps/cpg]
a: 490234736 16unu
Thanks Derek,
I tried deleting and recreating the one slice on that drive in sysinstall,
also rewriting the boot label. Didn't seem to help as shown:
%sudo fdisk ad1cs1
*** Working on device /dev/ad1cs1 ***
parameters extracted from in-core disklabel are:
cylinders=486332 heads=16 sector
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 overwriti
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.
-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 prim
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
# DeviceMountpoint FStype Options Dump
Pass#
/dev/ad0s1b non
20 matches
Mail list logo
