On Sat, 30 Aug 2014, Matthew Dharm wrote
> I was thinking of something that could notice a USB device which is formatted
> NTFS and has a partition table and filesystem that indicates a much bigger
> capacity than what the drive reports. Under this circumstances, you could do
> something like po
On Mon, 26 Aug 2014, David Leight wrote:
> I wonder what the manufacturer would saw in response the bug where
> windows shows the incorrect size when trying to partition the disk?
I contacted enclosure manufacturer (Welland) some weeks ago, they are supposed
to escalate my questions to enginee
On Mon, 25 Aug 2014 Alan Stern wrote:
> Part of the problem is that usb-storage has no way to know that anything
> strange is going on. It's normal for READ CAPACITY(16) to fail (this depend
> on
> the SCSI level), and it's normal for the READ
> CAPACITY(10) to report a value less than 2 TB.
> R
On Mon, 25 Aug 2014 Alan Stern wrote:
>
> On Mon, 25 Aug 2014, Alfredo Dal Ava Junior wrote:
>
> That's right. I don't know why Windows behaves that way.
Please look this output from diskpart (Windows):
DISKPART> list partition
Partition ### Type
On Mon, 15 Aug 2014 James Bottomley wrote:
> So how did the partition get on there at the correct size in the first place?
> Even under windows partition managers believe the disk size they get from
> the system if the disk is blank.
The HDD can be partitioned outside the enclosure, when connect
On Mon, 25 Aug 2014, Alan Stern wrote:
>
> Don't forget that lots of disks go crazy if you try to read from a nonexistent
> block, that is, one beyond the end of the disk.
> IMO, this bug cannot be worked around in any reasonable manner. The
> device simply cannot handle disks larger than 2 TB.
6 matches
Mail list logo
