OT: fdisk

Robert traveling08 at cox.net
Tue Oct 5 14:28:10 UTC 2010


On Tue, 5 Oct 2010 15:34:41 +0200
Polytropon <freebsd at edvax.de> wrote:

> On Tue, 5 Oct 2010 06:20:29 -0700, Robert <traveling08 at cox.net> wrote:
> > Update
> > 
> > [root at asus64] ~# dd if=/dev/da1 of=/1tb/disk500.img bs=1m
> > 476940+1 records in
> > 476940+1 records out
> > 500107862016 bytes transferred in 47027.134085 secs (10634453
> > bytes/sec)
> > 
> > ~ 14 hours later here is what I have.
> > 
> > [root at asus64] ~# ls -l /1tb
> > total 488625218
> > drwxrwxr-x  2 root  operator           512 Jan 19  2010 .snap
> > -rw-r--r--  1 root  wheel     500107862016 Oct  5 01:07 disk500.img
> >                               ^^^^^^^^^^^^
> 
> You got a copy of the entire disk. This is GOOD as you're not
> missing something important.
> 
> 
> 
> > [root at asus64] ~# mdconfig -a -t vnode -u 12 -f /1tb/disk500.img
> > [root at 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-r-----  1 root  operator    0, 131 Oct  5 05:55 /dev/md12
> > crw-r-----  1 root  operator    0, 133 Oct  5 05:55 /dev/md12s1
> > crw-------  1 root  wheel       0,  66 Oct  1 14:43 /dev/mdctl
> 
> Erm... erm erm erm!!! After using a md file that is connected to
> an image file, and you purge the image file, destroy the md file.
> Use "mdconfig -d -u 10" for unit 10, for example. See details in
> "man mdconfig".
> 
> 
> 
> > [root at asus64] ~# mount_ntfs /dev/md12s1 /mnt
> > mount_ntfs: /dev/md12s1: Invalid argument
> 
> This is the 1st "primary partition" with NTFS content, this one
> can't be mounted.

As ntfs.

> 
> 
> 
> > [root at asus64] ~# mount_ntfs /dev/md12 /mnt
> > [root at asus64] ~# ls -l /mnt
> > total 70044
> > -rwxr-xr-x  1 root  wheel      2560 Dec 31  1600 $AttrDef
> > -rwxr-xr-x  1 root  wheel         0 Oct  1 09:09 $BadClus
> > -rwxr-xr-x  1 root  wheel   4194304 Dec 31  1600 $Bitmap
> > -rwxr-xr-x  1 root  wheel      8192 Oct  1 09:09 $Boot
> > drwxr-xr-x  1 root  wheel         0 Oct  1 09:09 $Extend
> > -rwxr-xr-x  1 root  wheel  67108864 Oct  1 09:09 $LogFile
> > -rwxr-xr-x  1 root  wheel      4096 Oct  1 09:09 $MFTMirr
> > -rwxr-xr-x  1 root  wheel         0 Dec 31  1600 $Secure
> > -rwxr-xr-x  1 root  wheel    131072 Oct  1 09:09 $UpCase
> > -rwxr-xr-x  1 root  wheel         0 Oct  1 09:09 $Volume
> > -rwxr-xr-x  1 root  wheel     45124 Aug 18  2001 NTDETECT.COM
> > drwxr-xr-x  1 root  wheel         0 Oct  1 17:29 System Volume
> > Information 
> > -rwxr-xr-x  1 root  wheel       193 Oct  1 09:12 boot.ini
> > -rwxr-xr-x  1 root  wheel    222368 Aug 18  2001 ntldr
> > [root at asus64] ~# umount /mnt
> 
> This is the second NTFS volume, can be mounted.

Without any of the data.

> 
> 
> 
> > [root at asus64] ~# mount /dev/md12s1 /mnt
> 
> Why can the first one NOW be mounted???

As ufs!!!!
> 
> 
> 
> > [root at asus64] ~# ls -l /mnt
> > total 0
> > [root at asus64] ~# df -h
> > Filesystem           Size    Used   Avail Capacity  Mounted on
> > /dev/label/rootfs    989M    523M    387M    57%    /
> > devfs                1.0K    1.0K      0B   100%    /dev
> > /dev/label/home      9.7G    2.0G    6.9G    22%    /home
> > /dev/label/slice2     56G     53G   -1.4G   103%    /slice2
> > /dev/label/slice3     56G    4.0K     52G     0%    /slice3
> > /dev/label/slice4     56G     39G     13G    76%    /slice4
> > /dev/label/spare      20G    6.0K     18G     0%    /spare
> > /dev/label/tmp       484M     22M    423M     5%    /tmp
> > /dev/label/usr        20G    7.5G     11G    40%    /usr
> > /dev/label/var       989M    158M    752M    17%    /var
> > /dev/label/500ext    451G    153G    262G    37%    /500ext
> > /dev/label/1tb       902G    466G    364G    56%    /1tb
> > /dev/ad12s1d         226G     59G    149G    28%    /250extra
> > /dev/md12s1          451G     32G    383G     8%    /mnt
> >                               ^^^
> 
> This looks like "missing data". In terms of UFS file system, one
> would say that there a inodes not referenced, but still occupied
> as they are not marked as being free.
> 
> Sadly, I have *zero* knowledge about NTFS to make an interpretation
> about what we see here...

> 
> Good luck!

Thanks for that :-)

> 
> 
> 


More information about the freebsd-questions mailing list