Date: Mon, 4 Oct 2010 17:11:58 +0200 From: Polytropon <freebsd@edvax.de> To: Robert <traveling08@cox.net> Cc: freebsd-questions@freebsd.org Subject: Re: OT: fdisk Message-ID: <20101004171158.5940b9f5.freebsd@edvax.de> In-Reply-To: <20101004075221.7709740c@asus64> References: <201010031319.o93DJaDE005892@mail.r-bonomi.com> <20101003100051.23e2cc77@asus64> <20101003194045.849d6419.freebsd@edvax.de> <20101003142935.3d751862@asus64> <20101004123413.8e7cf859.freebsd@edvax.de> <20101004070858.3a101fa3@asus64> <20101004163225.34099bb8.freebsd@edvax.de> <20101004075221.7709740c@asus64>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 4 Oct 2010 07:52:21 -0700, Robert <traveling08@cox.net> wrote: > On Mon, 4 Oct 2010 16:32:25 +0200 > Polytropon <freebsd@edvax.de> wrote: > [root@asus64] ~# fdisk /dev/md10 > ******* Working on device /dev/md10 ******* > parameters extracted from in-core disklabel are: > cylinders=7648 heads=255 sectors/track=63 (16065 blks/cyl) > > Figures below won't work with BIOS for partitions not in cyl 1 > parameters to be used for BIOS calculations are: > cylinders=7648 heads=255 sectors/track=63 (16065 blks/cyl) > > Media sector size is 512 > Warning: BIOS sector numbering starts with sector 1 > Information from DOS bootblock is: > The data for partition 1 is: > sysid 7 (0x07),(NTFS, OS/2 HPFS, QNX-2 (16 bit) or Advanced UNIX) > start 63, size 976773105 (476939 Meg), flag 0 > beg: cyl 0/ head 1/ sector 1; > end: cyl 1023/ head 15/ sector 63 > The data for partition 2 is: > <UNUSED> > The data for partition 3 is: > <UNUSED> > The data for partition 4 is: > <UNUSED> Okay, as I see it, this looks valid - a working partition table. What can prevent mounting now is a defect in the NTFS MFT, everything "after" the disk's partition table. > > > [root@asus64] ~# ls -l /dev/md* > > > crw-r----- 1 root operator 0, 129 Oct 4 06:43 /dev/md10 > > > crw-r----- 1 root operator 0, 130 Oct 4 06:43 /dev/md10s1 > > > crw------- 1 root wheel 0, 66 Oct 1 14:43 /dev/mdctl > > > [root@asus64] ~# mount -o ro /dev/md10s1 /mnt > > > > Good. At least a bit. > > Is this the way to mount it, not _ntfs? My fault: Using mount_ntfs is the correct way (or mount -t ntfs); mount without options for a device / directory NOT listed in fstab defaults to UFS. > No. I was trying to just get the data to a 250GB drive. Now I am doing > the 500GB to a 1TB drive and will follow up when complete. Very good. You can check the progress by issuing ^T - dd will then show a status message. If you're using ddrescue (no big difference here), you'll get some more info, like this: % ddrescue -d -r 3 -n /dev/ad1s1f ad1s1f.ddr log.txt Press Ctrl-C to interrupt Initial status (read from logfile) rescued: 0 B, errsize: 0 B, errors: 0 Current status rescued: 90772 MB, errsize: 0 B, current rate: 6815 kB/s ipos: 90772 MB, errors: 0, average rate: 6723 kB/s opos: 90772 MB Finished This example is 3h 45min for 80 GB from one (P)ATA disk to another. You can watch the progress continuously here. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20101004171158.5940b9f5.freebsd>