From owner-freebsd-hackers Tue Dec 10 08:44:43 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA11978 for hackers-outgoing; Tue, 10 Dec 1996 08:44:43 -0800 (PST) Received: from luke.pmr.com (luke.pmr.com [206.224.65.132]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id IAA11973 for ; Tue, 10 Dec 1996 08:44:41 -0800 (PST) Received: (from bob@localhost) by luke.pmr.com (8.7.5/8.7.3) id KAA29064 for freebsd-hackers@freefall.cdrom.com; Tue, 10 Dec 1996 10:44:27 -0600 (CST) From: Bob Willcox Message-Id: <199612101644.KAA29064@luke.pmr.com> Subject: Dump "short read error" on a Micropolis disk To: freebsd-hackers@freefall.FreeBSD.org (freebsd-hackers) Date: Tue, 10 Dec 1996 10:44:27 -0600 (CST) Reply-To: bob@luke.pmr.com X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I have this Micropolis disk that the dump program doesn't seem to like. I continually get the following kinds of errors when dumping it: DUMP: Date of this level 0 dump: Tue Dec 10 10:00:12 1996 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/rsd6a (/usr3) to standard output DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 951885 tape blocks. DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: 11.27% done, finished in 0:39 DUMP: 23.46% done, finished in 0:32 DUMP: 35.43% done, finished in 0:27 DUMP: short read error from /dev/rsd6a: [block -670977536]: count=3072, got=0 DUMP: short read error from /dev/rsd6a: [sector -670977536]: count=512, got=0 DUMP: short read error from /dev/rsd6a: [sector -670977535]: count=512, got=0 ... Conincident with the dump errors I get the following system messages: Debugger("Slice code got negative blocknumber") called. Which lead me to be suspect that I had some kind of partition/label problem. But, alas, I have re-partitioned and re-labeled this disk a couple of times with no effect. The SCSI probe messages for this driver are: ahc2: target 0 Tagged Queuing Device (ahc2:0:0): "MICROP 2217-15MZ1001901 HZ30" type 0 fixed SCSI 2 sd6(ahc2:0:0): Direct-Access 1685MB (3450902 512 byte sectors) I have also included the disks partition and label info below. Thanks for any help you can give, Bob Willcox ******* Working on device /dev/rsd6 ******* parameters extracted from in-core disklabel are: cylinders=421 heads=256 sectors/track=32 (8192 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=421 heads=256 sectors/track=32 (8192 blks/cyl) Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 0 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 32, size 3448800 (1683 Meg), flag 80 beg: cyl 0/ sector 1/ head 1; end: cyl 420/ sector 32/ head 255 The data for partition 1 is: The data for partition 2 is: The data for partition 3 is: # /dev/rsd6c: type: SCSI disk: MICROP label: flags: bytes/sector: 512 sectors/track: 32 tracks/cylinder: 256 sectors/cylinder: 8192 cylinders: 420 sectors/unit: 3448800 rpm: 5400 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 3 partitions: # size offset fstype [fsize bsize bps/cpg] a: 3448800 0 4.2BSD 1024 8192 0 # (Cyl. 0 - 420*) c: 3448800 0 unused 0 0 # (Cyl. 0 - 420*) -- Bob Willcox politics, n: bob@luke.pmr.com A strife of interests masquerading as a contest of Austin, TX principles. The conduct of public affairs for private advantage. -- Ambrose Bierce