[PC-BSD Testing] 1TB external usb drive shows smaller size in Dolphin

Jeff dejamuse at yahoo.com
Sat May 8 10:35:06 PDT 2010


Hmm, that file dump shows both drives and it appears the correct size data for the 1TB drive (volume.size = 1000,202,241,024)

and lists the file system type as NTFS for the 320GB drive (volume.size = 320,062,063,104) (volume.fstype = 'ntfs').

See attached condensed file dump.

Could the system crash have corrupted the NTFS drive? It still works OK on Windoze.

--- On Sat, 5/8/10, Kris Moore <kris at pcbsd.org> wrote:

From: Kris Moore <kris at pcbsd.org>
Subject: Re: [PC-BSD Testing] 1TB external usb drive shows smaller size in Dolphin
To: "PC-BSD Testing list" <testing at lists.pcbsd.org>
Date: Saturday, May 8, 2010, 8:50 AM



"Jeff" <dejamuse at yahoo.com> wrote:

>dmesg reports da0 as:
>
>da0: <WD My Book 1028> Fixed Direct Access SCSI-4 device    
>da0: 40.000MB/s transfers                                                                               
>da0: 953869MB (1953525168 512 byte sectors: 255H 63S/T 121601C) 
>
>Dolphin doesn't interpret that data correctly.
>
>--- On Fri, 5/7/10, Jeff <dejamuse at yahoo.com> wrote:
>
>From: Jeff <dejamuse at yahoo.com>
>Subject: Re: [PC-BSD Testing] 1TB external usb drive shows smaller size in Dolphin
>To: "PC-BSD Testing list" <testing at lists.pcbsd.org>
>Date: Friday, May 7, 2010, 8:56 PM
>
>DiskFree gets it partly right - see attached image.
>
>/dev/ad70s1a is a spare internal drive (500MB) - correct data.
>/dev/da0s1 is a Western Digital external USB 1TB drive - wrong data.
>/dev/fuse0 is a Western Digital external USB 300MB drive - correct data.
>/dev/label/rootfs0 looks like the main drive root partition (500 MB drive).
>Nothing for /dev/ad6s1a which is the main drive - only its partitions.
>
>But the real problem is da0s1 because I can't put any more than about 2GB on the drive because it reports that it's full.  
>
>Anyway around this?  I'll ask over at FBSD too.
>
>
>
>--- On Fri, 5/7/10, Brodey Dover <doverosx at gmail.com> wrote:
>
>From: Brodey Dover
> <doverosx at gmail.com>
>Subject: Re: [PC-BSD Testing] 1TB external usb drive shows smaller size in Dolphin
>To: "PC-BSD Testing list" <testing at lists.pcbsd.org>
>Date: Friday, May 7, 2010, 6:03 PM
>
>Yep, I uncovered that tidbit in the other thread... I think Kris is onto something when specifying the right FS.
>
>On Fri, May 7, 2010 at 11:17 AM, Kris Moore <kris at pcbsd.org> wrote:
>
>
>
>
>  
>
>
>On 05/07/2010 19:08, Jeff wrote:
>
>  
>    
>      
>        Maybe dmesg gives a clue.  Windoze reported this as an
>NTFS drive:
>
>        
>
>uhub8: <vendor 0x1058 product 0x0500, class 9/0, rev 2.00/0.07, addr
>2> on usbus3
>
>uhub8: 4 ports with 2 removable, self powered
>
>ugen3.3: <Western Digital> at usbus3
>
>umass1: <Western Digital External HDD, class 0/0, rev 2.00/1.12,
>addr 3> on usbus3
>
>umass1:  SCSI over Bulk-Only; quirks = 0x008c
>
>umass1:3:1:-1: Attached to scbus3
>
>umass2: <Western Digital External HDD, class 0/0, rev 2.00/1.12,
>addr 3> on usbus3
>
>umass2:  SCSI over Bulk-Only; quirks = 0x008c
>
>umass2: could not setup required transfers, USB_ERR_NO_PIPE
>
>device_attach: umass2 attach returned 6
>
>da1 at umass-sim1 bus 1 target 0 lun 0
>
>da1: <WD 3200JB External 0112> Fixed Direct Access SCSI-0 device
>
>da1: 40.000MB/s transfers
>
>da1: 305245MB (625142448 512 byte sectors: 255H 63S/T 38913C)
>
>fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.8
>
>mountmsdosfs(): bad FAT32 filesystem
>
>mountmsdosfs(): bad FAT32 filesystem
>
>WARNING: /media/disk was not properly dismounted
>
>mountmsdosfs(): bad FAT32 filesystem
>
>mountmsdosfs(): bad FAT32 filesystem
>
>mountmsdosfs(): bad FAT32 filesystem
>
>        
>
>        
>
>        
>      
>    
>  
>
>Well, that makes sense why mount_msdosfs wouldn't work :P
>
>
>
>What about mount_ntfs <device> /mnt?
>
>
>
>
>
>
>
>-- 
>Kris Moore
>PC-BSD Software
>iXsystems
>
>
>
>_______________________________________________
>
>Testing mailing list
>
>Testing at lists.pcbsd.org
>
>http://lists.pcbsd.org/mailman/listinfo/testing
>
>
>
>
>
>-----Inline Attachment Follows-----
>
>_______________________________________________
>Testing mailing list
>Testing at lists.pcbsd.org
>http://lists.pcbsd.org/mailman/listinfo/testing
>
>
>
>
>
>
>
>
>
>      
>-----Inline Attachment Follows-----
>
>_______________________________________________
>Testing mailing list
>Testing at lists.pcbsd.org
>http://lists.pcbsd.org/mailman/listinfo/testing
>
>
>
>_______________________________________________
>Testing mailing list
>Testing at lists.pcbsd.org
>http://lists.pcbsd.org/mailman/listinfo/testing


Can you locate the device in the output of "lshal"? What size does it indicate there?  I'm guessing that's where the error is occurring.  



-- 
Kris Moore 
PC-BSD / iXsystems 
-----Inline Attachment Follows-----

_______________________________________________
Testing mailing list
Testing at lists.pcbsd.org
http://lists.pcbsd.org/mailman/listinfo/testing



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pcbsd.org/pipermail/testing/attachments/20100508/18f1cad3/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lshal data dump for ext WD HDDs
Type: application/octet-stream
Size: 42807 bytes
Desc: not available
URL: <http://lists.pcbsd.org/pipermail/testing/attachments/20100508/18f1cad3/attachment-0001.obj>


More information about the Testing mailing list