USB external drives showing 0kb

Linux WDMyCloud 3.2.26 #1 SMP Thu Aug 22 15:05:37 PDT 2013 armv7l

The programs included with the Debian GNU/Linux system are free software;

the exact distribution terms for each program are described in the

individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent

permitted by applicable law.

Last login: Sat Oct 26 23:09:09 2013 from 192.168.1.69

WDMyCloud:~# cat /var/log/messages

WDMyCloud:~#

that’s all it says nothing else, when i click the USB buton in the UI it just shows 0kb but detects the “Seagate 4tb + backup”

try 2 on another hard drive doing the same thing

Oct 27 02:14:20 WDMyCloud kernel: [5793.349053] usb 1-1: new high-speed USB device number 2 using xhci-hcd

Oct 27 02:14:20 WDMyCloud kernel: [5793.392297] usb 1-1: New USB device found, idVendor=1058, idProduct=1021

Oct 27 02:14:20 WDMyCloud kernel: [5793.399159] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3

Oct 27 02:14:20 WDMyCloud kernel: [5793.406522] usb 1-1: Product: Ext HDD 1021

Oct 27 02:14:20 WDMyCloud kernel: [5793.410688] usb 1-1: Manufacturer: Western Digital

Oct 27 02:14:20 WDMyCloud kernel: [5793.415622] usb 1-1: SerialNumber: 574D41593030323839303434

Oct 27 02:14:20 WDMyCloud kernel: [5793.430949] usb 1-1: ep 0x81 - rounding interval to 32768 microframes, ep desc says 0 microframes

Oct 27 02:14:20 WDMyCloud kernel: [5793.439953] usb 1-1: ep 0x2 - rounding interval to 32768 microframes, ep desc says 0 microframes

Oct 27 02:14:20 WDMyCloud kernel: [5793.491747] scsi2 : usb-storage 1-1:1.0

Oct 27 02:14:21 WDMyCloud kernel: [5794.491835] scsi 2:0:0:0: Direct-Access     WD       Ext HDD 1021     2021 PQ: 0 ANSI: 4

Oct 27 02:14:21 WDMyCloud kernel: [5794.500932] sd 2:0:0:0: Attached scsi generic sg1 type 0

Oct 27 02:14:21 WDMyCloud kernel: [5794.518228] sd 2:0:0:0: [sdb] 3907024896 512-byte logical blocks: (2.00 TB/1.81 TiB)

Oct 27 02:14:21 WDMyCloud kernel: [5794.529195] sd 2:0:0:0: [sdb] Write Protect is off

Oct 27 02:14:21 WDMyCloud kernel: [5794.605934]  sdb: unknown partition table

Oct 27 02:14:21 WDMyCloud kernel: [5794.626869] sd 2:0:0:0: [sdb] Attached SCSI disk

Oct 27 09:49:01 WDMyCloud kernel: [33074.513376] usb 2-1: new SuperSpeed USB device number 2 using xhci-hcd

Oct 27 09:49:01 WDMyCloud kernel: [33074.575806] usb 2-1: New USB device found, idVendor=0bc2, idProduct=a0a4

Oct 27 09:49:01 WDMyCloud kernel: [33074.582548] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1

Oct 27 09:49:01 WDMyCloud kernel: [33074.589749] usb 2-1: Product: Backup+ Desk

Oct 27 09:49:01 WDMyCloud kernel: [33074.593887] usb 2-1: Manufacturer: Seagate

Oct 27 09:49:01 WDMyCloud kernel: [33074.598008] usb 2-1: SerialNumber: NA5JYDJR

Oct 27 09:49:01 WDMyCloud kernel: [33074.640225] scsi3 : uas

Oct 27 09:49:01 WDMyCloud kernel: [33074.659664] scsi 3:0:0:0: Direct-Access     Seagate  Backup+ Desk     050B PQ: 0 ANSI: 6

Oct 27 09:49:01 WDMyCloud kernel: [33074.668610] sd 3:0:0:0: Attached scsi generic sg1 type 0

Oct 27 09:49:12 WDMyCloud kernel: [33074.687537] sd 3:0:0:0: [sdb] Spinning up disk…ready

Oct 27 09:49:12 WDMyCloud kernel: [33086.264297] sd 3:0:0:0: [sdb] physical block alignment offset: 68760723

Oct 27 09:49:12 WDMyCloud kernel: [33086.270956] sd 3:0:0:0: [sdb] Unsupported sector size 1768121715.

Oct 27 09:49:12 WDMyCloud kernel: [33086.277131] sd 3:0:0:0: [sdb] 0 512-byte logical blocks: (0 B/0 B)

Oct 27 09:49:12 WDMyCloud kernel: [33086.283369] sd 3:0:0:0: [sdb] 1768121715-byte physical blocks

Oct 27 09:49:12 WDMyCloud kernel: [33086.308692] sd 3:0:0:0: [sdb] Write Protect is off

Oct 27 09:49:12 WDMyCloud kernel: [33086.319032] xhci-hcd xhci-hcd: Mismatch between completed Set TR Deq Ptr command & xHCI internal state.

Oct 27 09:49:12 WDMyCloud kernel: [33086.328485] xhci-hcd xhci-hcd: ep deq seg = c6a00fc0, deq ptr = ffda28a0

Oct 27 09:49:12 WDMyCloud kernel: [33086.335287] xhci-hcd xhci-hcd: WARN Set TR Deq Ptr cmd invalid because of stream ID configuration

Oct 27 09:49:43 WDMyCloud kernel: [33117.383304] sd 3:0:0:0: uas_eh_abort_handler tag 0

Oct 27 09:49:43 WDMyCloud kernel: [33117.388139] sd 3:0:0:0: uas_eh_device_reset_handler tag 0

Oct 27 09:49:43 WDMyCloud kernel: [33117.393601] sd 3:0:0:0: uas_eh_target_reset_handler tag 0

Oct 27 09:49:43 WDMyCloud kernel: [33117.399035] sd 3:0:0:0: uas_eh_bus_reset_handler tag 0

Oct 27 09:49:44 WDMyCloud kernel: [33117.523783] usb 2-1: reset SuperSpeed USB device number 2 using xhci-hcd

Oct 27 09:49:44 WDMyCloud kernel: [33117.543780] xhci-hcd xhci-hcd: xHCI xhci_drop_endpoint called with disabled ep cdd51bc0

Oct 27 09:49:44 WDMyCloud kernel: [33117.551835] xhci-hcd xhci-hcd: xHCI xhci_drop_endpoint called with disabled ep cdd51bec

Oct 27 09:49:44 WDMyCloud kernel: [33117.559924] xhci-hcd xhci-hcd: xHCI xhci_drop_endpoint called with disabled ep cdd51c18

Oct 27 09:49:44 WDMyCloud kernel: [33117.568009] xhci-hcd xhci-hcd: xHCI xhci_drop_endpoint called with disabled ep cdd51c44

Oct 27 09:49:44 WDMyCloud kernel: [33117.597413] sd 3:0:0:0: Device offlined - not ready after error recovery

Oct 27 09:49:44 WDMyCloud kernel: [33117.615231] sd 3:0:0:0: [sdb] Attached SCSI disk

Well, the first one is complaining that the Partition Type isn’t recognized.    How’s the disk formatted?

The second one is complaining about an unknown sector size.  Most disks are 512-byte or 4096-byte sectors.

Your disk is reporting a size of 1768121715.  

that’s the thing i don’t get, it works fine when connected to two different macs, and its formatted HFS+J with 1 partition. the other one i just got annoyed and formatted the drive 5-6 times in a row and it worked once, then stpped working again. 

after disconnecting it and then reconnecting it now its saying this

Oct 27 23:09:50 WDMyCloud kernel: [81124.403378] usb 2-1: new SuperSpeed USB device number 4 using xhci-hcd

Oct 27 23:09:50 WDMyCloud kernel: [81124.498128] usb 2-1: New USB device found, idVendor=0bc2, idProduct=a0a4

Oct 27 23:09:50 WDMyCloud kernel: [81124.504901] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1

Oct 27 23:09:50 WDMyCloud kernel: [81124.512078] usb 2-1: Product: Backup+ Desk

Oct 27 23:09:50 WDMyCloud kernel: [81124.516223] usb 2-1: Manufacturer: Seagate

Oct 27 23:09:51 WDMyCloud kernel: [81124.520488] usb 2-1: SerialNumber: NA5JYDJR

Oct 27 23:09:51 WDMyCloud kernel: [81124.783743] scsi5 : uas

Oct 27 23:09:51 WDMyCloud kernel: [81124.813709] scsi 5:0:0:0: Direct-Access     Seagate  Backup+ Desk     050B PQ: 0 ANSI: 6

Oct 27 23:09:51 WDMyCloud kernel: [81124.822570] sd 5:0:0:0: Attached scsi generic sg1 type 0

Oct 27 23:09:51 WDMyCloud kernel: [81124.843424] sd 5:0:0:0: [sdb] Spinning up disk…

Oct 27 23:10:03 WDMyCloud kernel: [81125.863358] …ready

Oct 27 23:10:03 WDMyCloud kernel: [81136.954693] sd 5:0:0:0: [sdb] Sector size 0 reported, assuming 512.

Oct 27 23:10:03 WDMyCloud kernel: [81136.961020] sd 5:0:0:0: [sdb] 13878555579489714177 512-byte logical blocks: (3.82 EB/3.31 EiB)

Oct 27 23:10:03 WDMyCloud kernel: [81136.969730] sd 5:0:0:0: [sdb] 0-byte physical blocks

Oct 27 23:10:03 WDMyCloud kernel: [81137.028173] sd 5:0:0:0: [sdb] Write Protect is off

Oct 27 23:10:03 WDMyCloud kernel: [81137.053468] xhci-hcd xhci-hcd: Mismatch between completed Set TR Deq Ptr command & xHCI internal state.

Oct 27 23:10:03 WDMyCloud kernel: [81137.062924] xhci-hcd xhci-hcd: ep deq seg = cf6bd880, deq ptr = ffd904a0

Oct 27 23:10:03 WDMyCloud kernel: [81137.069742] xhci-hcd xhci-hcd: WARN Set TR Deq Ptr cmd invalid because of stream ID configuration

Oct 27 23:10:33 WDMyCloud kernel: [81167.383281] sd 5:0:0:0: uas_eh_abort_handler tag 0

Oct 27 23:10:33 WDMyCloud kernel: [81167.388117] sd 5:0:0:0: uas_eh_device_reset_handler tag 0

Oct 27 23:10:33 WDMyCloud kernel: [81167.393586] sd 5:0:0:0: uas_eh_target_reset_handler tag 0

Oct 27 23:10:33 WDMyCloud kernel: [81167.399019] sd 5:0:0:0: uas_eh_bus_reset_handler tag 0

Oct 27 23:10:34 WDMyCloud kernel: [81167.523887] usb 2-1: reset SuperSpeed USB device number 4 using xhci-hcd

Oct 27 23:10:34 WDMyCloud kernel: [81167.543794] xhci-hcd xhci-hcd: xHCI xhci_drop_endpoint called with disabled ep c95481a0

Oct 27 23:10:34 WDMyCloud kernel: [81167.551848] xhci-hcd xhci-hcd: xHCI xhci_drop_endpoint called with disabled ep c95481cc

Oct 27 23:10:34 WDMyCloud kernel: [81167.559953] xhci-hcd xhci-hcd: xHCI xhci_drop_endpoint called with disabled ep c95481f8

Oct 27 23:10:34 WDMyCloud kernel: [81167.568029] xhci-hcd xhci-hcd: xHCI xhci_drop_endpoint called with disabled ep c9548224

Oct 27 23:10:34 WDMyCloud kernel: [81167.614978] sd 5:0:0:0: Device offlined - not ready after error recovery

Oct 27 23:10:34 WDMyCloud kernel: [81167.637256] sd 5:0:0:0: [sdb] Attached SCSI disk

So i tried something a little different I took apart both drives the 2TB WD drive and the 4TB seagate drive. I then formatted the 2TB as a DOS startup partition drive in HFS+J. When i plugged it through the Seagate USB 3.0 i got the same thing 0kb. I then switched it out to the USB 2.0 port drive connector and it still showed 0kb initially but a few seconds later it started working no problems so 1 drive down and i think i’ve narrowed the problem down to Seagate USB 3.0 connector. Apparently WD doesn’t wanna play nice with Seagate. 

This issue is currently under investigation.

There’s a knowledge base article for this, please see the link bellow:

http://wdc.custhelp.com/app/answers/detail/a_id/10629

Regards, 

Robothief. 

Yeah, i actually saw that tried it on both drives and it worked for one of them, the WD one. so Using that currently and just using the other through USB right now. Hopefully a fix will come soon enough. 

Just want to confirm the same issue with Seagate Expansion 4TB USB 3.0.

The SE4 drive works fine being connected to PC, chkdsk shows no errors.

Safe eject from PC (Win 7-64) and insertion into Wd My Cloud 3TB (v03.01.03-127) results in 0kb size (the drive itself gets recognized though).

I started a support ticket as well and its been a week without reply. Seems like either WD working hard to fix the issue or are just ignoring it and hoping people the very few that will actually use the expansion slot for larger storage will just give up and go away… 

I too just purchased a Seagate 4TB expansion. Win7/64 usb 3.0 and I have the same issue as well.

Same here, about 6 hours total on working with techs to resolve this and other problems. This included sending out a new 3tb unit only to have the same issue. WD should do complete testing on their new products so the consumer does not run into this type of frustrating problem.

I am now out of the the refund period at BB and stuck with a drive that will not meet my storage requirements. Come on WD lets get this problem fixed!!

Guys I gotta tell ya, do the workaround I posted earlier in this thread, then when you plug it back into the WD NAS, just WAIT. It takes it awhile to populate. As in 60 seconds sometimes. Both of my external drives were doing this issue, and after I did the workaround they both work everytime. Also the newest firmware speeds up the process of recognizing them a little bit too.

I’m also having this issue with a WD My Passport USB 3.0 1.5TB attached to the USB port. The only way that I’m able to copy files is in two steps. 1st. copy the file(s) to the My Cloud 2TB Drive and then using the My Cloud Desktop application (Ver. 1.0.3.12)  I copy them to the USB attached drive. There are also issues creating folders, moving/copying files within the drive while Windows.

Tried the work around, performed ckdsk and performed proper eject. Connected 4tb seagate to mycloud and no joy :((

Thanks

I am open to any suggestions??

Like everybody else here, i was having the same problem with my Seagate Backup Plus hard drive.  I tried contacting WD to open a ticket and haven’t heard back.  To further troubleshoot the problem, i plugged in my secondary seagate drive (free agent) and it recognized the drive and its size so i figured that it had to be the “backup plus” seagate drive that was not playing nice with WD MyCloud.  Since i had just purchased the Seagate Backup Plus drive, i exchanged it for a WD MyBook and it worked wonders.  Now i have no problems.

I would suggest to anyone having this same problem to try a different external hard drive if available.  I spent many hours formatting my Seagate BUP using different formats trying to make this work. 

Good luck to everybody.

Well, no “workaround” works for me. As to “trying” a different drive etc.: why should I?

I have a perfectly healthy drive which works with every single device I have connected it to: 2 PCs, Mac,  Netgear Nighthawk R7000 router. No problem there!

So… The only thing that comes to mind: one dysfunctional firmware running WD My Cloud. That is, unless we all purchased faulty devices.

The USB 3.0 expansion port is one of the major selling points. The inability to use it, at least with certain hard drives, can and will hurt WD reputation. A lot of people know where to look for the real reviews on a particular product: its own support forum. And word gets around.

Fix it. Soon.

The ability to successfully copy, move, delete, rename and create files are “Fundamental” functions that any USB attached storage device to the My Cloud drive needs to perform flawlessly… Out of the box. Especially if the drives that are being connected to the USB 3.0 port are also manufactured by WD. There is no excuse for not performing thorough tests for compatibility with their own line of portable USB drives. I have tried 3 WD My Passport drives and they all have the same issue. As mentioned above, if this is a firmware issue, it needs to be addressed ASAP. I’m afraid that this product was rushed to market to take advantage of the holiday season. I just watched a My Cloud ad on TV. Hopefully WD has put as much effort to resolve the technical issues with the My Cloud NAS as they have to advertise it.

+1. I was fortunate enough to be able to send my seagate 4tb back for return after following the workaround instructions, etc with no success. I really like the WBMC product and concept. I just hope this issue is resolved before I exhaust the storage capacity, so I can obtain a more reliable expansion option.