View Single Post
Old Jan 3, 2013, 11:01 AM   #9
<<Onafets>>
500 Posts
 
<<Onafets>>'s Avatar
 
Join Date: Nov 2008
Location: Sydney, Australia
Posts: 757 (0.46/day)
Thanks: 490
Thanked 77 Times in 73 Posts

System Specs

I take it that just a regular mount doesn't work either?

Code:
mount: you must specify the filesystem type
Also what does fdisk have to say?

Code:
Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x4869c773

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1            2048  3907026943  1953512448    6  FAT16
It sounds odd that it thinks that it is formatted fat16. I didn't think fat16 supported partitions that large.

Neither did I lol. Any ideas? So far data recovery has proven insufficient at this stage
FAT16 is a worry because most files on the drive were over 4GB which is the limit for FAT32. Everything is probably destroyed under FAT16's file size limits.
__________________
“As long as you bypass the quantum septicular rings and interconnect the transmission module 3/4 the way down the flux capacitor you'll do just fine.” -Soylent Joe
“Don't go all flash. Your website would be a resource hog, slow down people's browsers and kill little baby seals.” -xbonez

Last edited by <<Onafets>>; Jan 3, 2013 at 12:35 PM.
<<Onafets>> is offline  
Reply With Quote