Noooo, 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 find any usable data.  Since it is only 24MB hopefully any data loss is
minimal.

        -Derek


At 05:08 PM 2/22/2007, Marty Landman 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 shown:

%sudo fdisk ad1cs1
******* Working on device /dev/ad1cs1 *******
parameters extracted from in-core disklabel are:
cylinders=486332 heads=16 sectors/track=63 (1008 blks/cyl)

Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=486332 heads=16 sectors/track=63 (1008 blks/cyl)

Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
<UNUSED>
The data for partition 2 is:
<UNUSED>
The data for partition 3 is:
<UNUSED>
The data for partition 4 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
    start 0, size 50000 (24 Meg), flag 80 (active)
        beg: cyl 0/ head 0/ sector 1;
        end: cyl 1023/ head 254/ sector 63
%sudo fsck /dev/ad1cs1
fsck: Could not determine filesystem type
%sudo fsck /dev/ad1c
fsck: exec fsck_unused for /dev/ad1c in /sbin:/usr/sbin: No such file or
directory
%sudo mount /dev/ad1cs1 /hoss
mount: /dev/ad1cs1: Input/output error
%sudo mount /dev/ad1c /hoss
mount: /dev/ad1c on /hoss: incorrect super block
%sudo dd if=/dev/ad1s1 of=/tmp/scratch bs=512 count=1 skip=131
dd: /dev/ad1s1: Input/output error
0+0 records in
0+0 records out
0 bytes transferred in 1.199710 secs (0 bytes/sec)
%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.018295 secs (27986 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.024593 secs (20819 bytes/sec)
%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.319451 secs (0 bytes/sec)
%

Wonder why it renamed my slice from ad1s1c to ad1cs1, and what I can do
from here.

Marty

On 2/22/07, *Derek Ragona* <[EMAIL PROTECTED]> 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.

        -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 "
[EMAIL PROTECTED]"

--
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* <http://www.mailscanner.info/>, and is
believed to be clean.
MailScanner thanks transtec Computers <http://www.transtec.co.uk/> for
their support.




--
Web Installed Formmail - http://face2interface.com/formINSTal/
Webmaster's BBS - http://bbs.face2interface.com/
--
This message has been scanned for viruses and
dangerous content by MailScanner <http://www.mailscanner.info/>, and is
believed to be clean.
MailScanner thanks transtec Computers <http://www.transtec.co.uk/> for
their support.


--
This message has been scanned for viruses and
dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
believed to be clean.
MailScanner thanks transtec Computers <http://www.transtec.co.uk/> for
their support.




--
Web Installed Formmail - http://face2interface.com/formINSTal/
Webmaster's BBS - http://bbs.face2interface.com/


--
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 "[EMAIL PROTECTED]"

Reply via email to