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
_______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"