Date: Thu, 10 Jan 2002 14:58:26 -0600 (CST) From: Steven Kirk <kirk@blackhat.net> To: <freebsd-questions@freebsd.org> Subject: Slices, and Partitions, and Tigers, OH MY! Message-ID: <Pine.LNX.4.33.0201101449130.30990-100000@tempest.blackhat.net>
next in thread | raw e-mail | index | archive | help
You'll be glad to know this is not your standard "I don't know how to
partition my drive" question :)
I have two physical drives in my system (a server):
/dev/amrds0 - for the OS
/dev/amrds1 - for my data
Well, something happened (don't know what, how, why etc) but now the
partition/slice entries are fubar'd.
It started after I did a firmware update on the SCSI backplane. It
installed fine, so I don't know what happened to cause this. At this
point I just need to recover, then I can root-cause it afterwards.
Don't care about the first (OS) drive -- that's easily rebuilt. It's the
data drive which has had me up for two days trying to save.
Anytime I attempt to access the drive, I get a series of kernel messages:
/kernel: amrd1: raw partition size != slice size
/kernel: amrd1: start 63, end 8369864, size 8369802 #(this is incorrect)
/kernel: amrd1c: start 63, end 143107019, size 143106957 #(this is correct)
/kernel: amrd1e: start 63, end 143107019, size 143106957
/kernel: amrd1: truncating raw partition
/kernel: amrd1: rejecting partition in BSD label: it isn't
entirely within the slice
I've tried installing the OS (FreeBSD 4.4) back onto the OS drive (start
from scratch)(no amrd1 NOT in the system). The install went fine, no
errors. Then I run /stand/sysinstall to add the data drive into the
system, but I get the kernel messages when sysinstall starts up & probes
devices. I'm VERY wary of making any changes thru fdisk or disklabel for
fear of losing anything that's still there.
I've tried installing FreeBSD 4.2, 4.3, and 4.4, all get the same error.
I've tried mounting the drive under Linux, but I get a cryptic error
(reclen does not match namelen, directory #2 -- ??).
I tried running "fsck -n /dev/amrd1s1e" (and variations) to see if fsck
could maybe see the errors enough to repair them, but again the kernel
messages spew out, and fsck reports wrong superblock.
so.... I'm open to any ideas. I'm really rather desperate to save what's
on this drive.
Thoughts, ideas, theories...all are welcome!
Thanks!
--Steve
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.33.0201101449130.30990-100000>