Date: Fri, 01 Sep 2000 11:25:38 -0700 From: "Kevin Oberman" <oberman@es.net> To: questions@freebsd.org Subject: Problems with slice setup in Fujitsu disk Message-ID: <200009011825.e81IPcU01438@ptavv.es.net>
next in thread | raw e-mail | index | archive | help
I have a problem running dd between a Fujitsu and a Maxtor disk. I am simply trying to copy my root partition from one disk to the other with a simple dd. dd bs=8192 if=/dev/ad0s1a of=/dev/ad2s1a This command works fine on my laptop, but on my home system it fails and I log the following errors: dscheck(#ad/0x20010): fixlabel: raw partition size > slice size fixlabel: raw partition offset != slice offset (This message does not seem to be from dd, itself. I assume it's from the kernel. First, I don't know how to interpret "#ad/0x20010". Which disk has a problem? I suspect it's the Fujitsu. A boot -v provides the following information: Aug 28 18:30:14 kzin /kernel: ad0: <FUJITSU MPE3136AT/ED-90-06> ATA-4 disk at a$ Aug 28 18:30:14 kzin /kernel: ad0: 13031MB (26688576 sectors), 26476 cyls, 16 h$ Aug 28 18:30:14 kzin /kernel: ad0: 16 secs/int, 1 depth queue, UDMA33 Aug 28 18:30:14 kzin /kernel: ad0: piomode=4 dmamode=2 udmamode=4 cblid=0 Aug 28 18:30:14 kzin /kernel: Creating DISK ad0 Aug 28 18:30:14 kzin /kernel: Creating DISK wd0 Aug 28 18:30:14 kzin /kernel: ata1-master: success setting UDMA2 on Aladdin chip Aug 28 18:30:14 kzin /kernel: ad2: <Maxtor 91366U4/RA530JN0> ATA-5 disk at ata1$ Aug 28 18:30:14 kzin /kernel: ad2: 13029MB (26684784 sectors), 26473 cyls, 16 h$ Aug 28 18:30:14 kzin /kernel: ad2: 16 secs/int, 1 depth queue, UDMA33 Aug 28 18:30:14 kzin /kernel: ad2: piomode=4 dmamode=2 udmamode=4 cblid=1 Aug 28 18:30:14 kzin /kernel: Creating DISK ad2 Aug 28 18:30:14 kzin /kernel: Creating DISK wd2 When I mount the partitions, I get: Aug 28 18:30:14 kzin /kernel: ad0s1: type 0xa5, start 63, end = 26687807, size $ Aug 28 18:30:14 kzin /kernel: ad2s1: type 0xa5, start 63, end = 26684783, size $ So all of the numbers look fine for the ad2 device (MAXTOR), but not so good for ad0 as I have a mis-match of 26688576 vs. 26687808. If I try to use sysinstall to look at the slices, I get something similar. I tell it to use the whole disk for the first slice, but it shows that I have a slice ending at 26687807 and an unused space of 768 blocks. This matches the difference between 26688576 and 26687808.) Is this the cause of the errors and, if so, how can it be fixed? fdisk (in sysinstall) is adamant about leaving 768 blocks. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 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?200009011825.e81IPcU01438>