Return to BSD News archive
Newsgroups: comp.unix.bsd.freebsd.misc
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.uwa.edu.au!classic.iinet.com.au!news.uoregon.edu!usenet.eel.ufl.edu!news.mathworks.com!uunet!in1.uu.net!news.sprintlink.net!in2.uu.net!statsci.com!news
From: scott@statsci.com (Scott Blachowicz)
Subject: Suggestions for tracking disk corruption in 2.0.5R ?
X-Nntp-Posting-Host: chute
Message-ID: <vmvir3sa3g.fsf@chute.statsci.com>
Lines: 243
Sender: scott@chute.statsci.com
Reply-To: scott@statsci.com
Organization: StatSci div. of MathSoft, Seattle, WA USA
X-Newsreader: Gnus v5.0
Date: Fri, 8 Sep 1995 17:35:31 GMT
[I sent this to questions@freebsd.org, but things have been acting
strangely with our Internet connection lately, so I'm not positive if it
really made it and I've gotten no response. Besides I'm getting antsy for
ideas and was wondering if a wider audience might help... :-)]
Hi-
I've finally gotten 2.0.5 up & going without shooting my own bloody foot
off. I like it, but...
I was doing normal sort of work - editing files, doing a 'pkg_add' on a
new package from ftp.freebsd.org:/pub/FreeBSD/packages/ (BTW, are those
supposed to work with 2.0.5? or just -current? or maybe -stable &
-current? or ...) with a uucico running in the background. I noticed a
few odd messages that looked like this:
free inode /usr/20096 had -268370322 blocks
My partitioning/slicing looks like this:
wd0s1 - DOS /c
wd0s2a - 4.2BSD /
wd0s2e - 4.2BSD /usr/X11R6
wd0s3 - DOS /e
sd0s1 - DOS /d
sd0s2 - swap (shared between Linux & FreeBSD, or at least that's the goal)
sd0s3c - 4.2BSD /usr
sd0s4 - Linux ext2 /
This happened last night, so after fsck'ing my /usr, I reinstalled FreeBSD (no
newfs'ing) and editing my fstab to mount my DOS partitions as read-only (I've
been seeing things warning about rw-mounted DOS partitions - what EXACTLY is
the problem there? if any?), umount'd the DOS partitions, then mount'd them
again. I left the system running overnight and now doing things like 'ls /usr'
just return an error like:
/usr: Bad file descriptor
Does anything in here pop out at you as being something to investigate
further?
I ran a bunch of commands (e.g. dmesg, disklabel, fdisk) and their output
follows.
Now, here is some 'dmesg' output:
FreeBSD 2.0.5-RELEASE #0: Sat Sep 2 20:42:09 PDT 1995
root@sabami.seaslug.org:/usr/src/sys/compile/SABAMI
CPU: 90-MHz Pentium 735\\90 (Pentium-class CPU)
Origin = "GenuineIntel" Id = 0x522 Stepping=2
Features=0x1bf<FPU,VME,PSE,MCE,CX8,APIC>
real memory = 16384000 (4000 pages)
avail memory = 15036416 (3671 pages)
Probing for devices on the ISA bus:
sc0 at 0x60-0x6f irq 1 on motherboard
sc0: VGA color <16 virtual consoles, flags=0x0>
ed1 at 0x300-0x31f irq 10 on isa
ed1: address 00:80:48:88:74:5a, type NE2000 (16 bit)
sio0 at 0x3f8-0x3ff irq 4 on isa
sio0: type 16550A
sio1 at 0x2f8-0x2ff irq 3 on isa
sio1: type 16550A
sio2 not found at 0x3e8
sio3 not found at 0x2e8
lpt0 at 0x378-0x37f irq 7 on isa
lpt0: Interrupt-driven port
lp0: TCP/IP capable interface
lpt1 not found at 0xffffffff
lpt2 not found at 0xffffffff
fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
fdc0: NEC 72065B
fd0: 1.44MB 3.5in
wdc0 at 0x1f0-0x1f7 irq 14 on isa
wdc0: unit 0 (wd0): <ST31220A>
wd0: 1033MB (2115792 sectors), 2099 cyls, 16 heads, 63 S/T, 512 B/S
wdc1 not found at 0x170
npx0 on motherboard
npx0: INT 16 interface
Probing for devices on the pci0 bus:
configuration mode 1 allows 32 devices.
pci0:0: INTEL CORPORATION, device=0x122d, class=bridge [not supported]
pci0:7: INTEL CORPORATION, device=0x122e, class=bridge [not supported]
vga0 <VGA-compatible display device> rev 1 on pci0:10
ncr0 <ncr 53c815 scsi> rev 3 int a irq 11 on pci0:11
reg20: virtual=0xf2e91000 physical=0xfafff000 size=0x100
ncr0: restart (scsi reset).
ncr0 scanning for targets 0..6 (V2 pl21 95/03/21)
ncr0 waiting for scsi devices to settle
(ncr0:2:0): "TOSHIBA CD-ROM XM-3501TA 3054" type 5 removable SCSI 2
cd0(ncr0:2:0): CD-ROM
cd0(ncr0:2:0): 250ns (4 Mb/sec) offset 8.
cd present.[264427 x 2048 byte records]
(ncr0:3:0): "QUANTUM EMPIRE_1400S 100E" type 0 fixed SCSI 2
sd0(ncr0:3:0): Direct-Access
sd0(ncr0:3:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8.
1335MB (2734996 512 byte sectors)
(ncr0:5:0): "EXABYTE EXB-8200 265T" type 1 removable SCSI 1
st0(ncr0:5:0): Sequential-Access density code 0x0, drive empty
pci0: uses 8388864 bytes of memory from fafff000 upto fb7fffff.
pci0: uses 256 bytes of I/O space from e400 upto e4ff.
mountmsdosfs(): root directory is not a multiple of the clustersize in length
pid 284: xrdb: uid 1000: exited on signal 11
free inode /usr/20096 had -268370322 blocks
free inode /usr/20097 had -268370093 blocks
free inode /usr/20098 had -268370093 blocks
free inode /usr/20129 had -268370093 blocks
******* Working on device /dev/rsd0 *******
parameters extracted from in-core disklabel are:
cylinders=3053 heads=43 sectors/track=63 (2709 blks/cyl)
Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=3053 heads=43 sectors/track=63 (2709 blks/cyl)
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 0 is:
sysid 6,(Primary 'big' DOS (> 32MB))
start 63, size 246456 (120 Meg), flag 0
beg: cyl 0/ sector 1/ head 1;
end: cyl 90/ sector 63/ head 42
The data for partition 1 is:
sysid 165,(FreeBSD/NetBSD/386BSD)
start 246519, size 100233 (48 Meg), flag 80
beg: cyl 91/ sector 1/ head 0;
end: cyl 127/ sector 63/ head 42
The data for partition 2 is:
sysid 165,(FreeBSD/NetBSD/386BSD)
start 346752, size 1026711 (501 Meg), flag 80
beg: cyl 128/ sector 1/ head 0;
end: cyl 506/ sector 63/ head 42
The data for partition 3 is:
sysid 131,(Linux filesystem)
start 1373463, size 1359918 (664 Meg), flag 0
beg: cyl 507/ sector 1/ head 0;
end: cyl 1008/ sector 63/ head 42
******* Working on device /dev/rwd0 *******
parameters extracted from in-core disklabel are:
cylinders=2099 heads=64 sectors/track=63 (4032 blks/cyl)
Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=2099 heads=64 sectors/track=63 (4032 blks/cyl)
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 0 is:
sysid 6,(Primary 'big' DOS (> 32MB))
start 63, size 766017 (374 Meg), flag 80
beg: cyl 0/ sector 1/ head 1;
end: cyl 189/ sector 63/ head 63
The data for partition 1 is:
sysid 165,(FreeBSD/NetBSD/386BSD)
start 766080, size 241920 (118 Meg), flag 0
beg: cyl 190/ sector 1/ head 0;
end: cyl 249/ sector 63/ head 63
The data for partition 2 is:
sysid 6,(Primary 'big' DOS (> 32MB))
start 1008000, size 1104768 (539 Meg), flag 0
beg: cyl 250/ sector 1/ head 0;
end: cyl 523/ sector 63/ head 63
The data for partition 3 is:
<UNUSED>
# /dev/rwd0s2c:
type: ESDI
disk: wd0s2
label:
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 64
sectors/cylinder: 4032
cylinders: 60
sectors/unit: 241920
rpm: 0
interleave: 0
trackskew: 0
cylinderskew: 0
headswitch: 0 # milliseconds
track-to-track seek: 0 # milliseconds
drivedata: 0
8 partitions:
# size offset fstype [fsize bsize bps/cpg]
a: 71680 0 4.2BSD 0 0 0 # (Cyl. 0 - 17*)
c: 241920 0 unused 0 0 # (Cyl. 0 - 59)
e: 170240 71680 4.2BSD 0 0 0 # (Cyl. 17*- 59*)
# /dev/rsd0s2:
type: SCSI
disk: sd0s2
label:
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 43
sectors/cylinder: 2709
cylinders: 37
sectors/unit: 100233
rpm: 0
interleave: 0
trackskew: 0
cylinderskew: 0
headswitch: 0 # milliseconds
track-to-track seek: 0 # milliseconds
drivedata: 0
8 partitions:
# size offset fstype [fsize bsize bps/cpg]
b: 100233 0 swap # (Cyl. 0 - 36)
c: 100233 0 unused 0 0 # (Cyl. 0 - 36)
# /dev/rsd0s3c:
type: SCSI
disk: sd0s3
label:
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 43
sectors/cylinder: 2709
cylinders: 379
sectors/unit: 1026711
rpm: 0
interleave: 0
trackskew: 0
cylinderskew: 0
headswitch: 0 # milliseconds
track-to-track seek: 0 # milliseconds
drivedata: 0
8 partitions:
# size offset fstype [fsize bsize bps/cpg]
c: 1026711 0 unused 0 0 # (Cyl. 0 - 378)
e: 1026711 0 4.2BSD 0 0 0 # (Cyl. 0 - 378)
Don't you just hate it when people post big ole long messages?
Any ideas would be greatly appreciated!
--
Scott Blachowicz Ph: 206/283-8802x240 StatSci, a div of MathSoft, Inc.
1700 Westlake Ave N #500
scott@statsci.com Seattle, WA USA 98109
Scott.Blachowicz@seaslug.org