:1. I was wondering if anyone knew of any such problems, or what other
:info I could provide to help figure this out.
:2. There are no panics or anything. I can't seem to find an isolated
:case to look at. Anyone have any idea how I would go about debugging
:this?
:3. Would I be better off running the newer driver in current? I keep
:tabs with whats going on in the current list, I just need a somewhat
:stable machine. It's only going to get light usage.
:
:Thanks for any help. Sorry this is so vauge. I'd really like you to
:get a dmesg. Below is the kernel config....
The very first think I would do is look at the disklabel for the drive
and make sure that none of the offset/sizes overlap (except for the
'c' whole-disk partition, of course).
e.g. take the offset, add the size, make sure the result is the offset
for the next partition, and repeat. The final offset+size should of course
not exceed the size of the disk. Partitions can slice up the disk
out of order, but if they overlap (except for c) you will get file
corruption.
Also look for error messages in /var/log/messages.
# disklabel da0 (or in your case perhaps wd0)
8 partitions:
# size offset fstype [fsize bsize bps/cpg]
a: 262144 0 4.2BSD 1024 8192 16 # (Cyl. 0 - 16*)
b: 1048576 262144 swap # (Cyl. 16*- 81*)
c: 4192902 0 unused 0 0 # (Cyl. 0 - 260*)
d: 262144 1310720 4.2BSD 1024 8192 16 # (Cyl. 81*- 97*)
e: 262144 1572864 4.2BSD 1024 8192 16 # (Cyl. 97*- 114*)
f: 2097152 1835008 4.2BSD 1024 8192 16 # (Cyl. 114*- 244*)
g: 260742 3932160 4.2BSD 1024 8192 16 # (Cyl. 244*- 260*)
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message