When running a Safepoint on my WD MyCloud to a new 4TB My Passport, I get this stream of errors that eventually result in the Safepoint failing. Is there a firmware update for the drive to fix this? The Universal Firmware Updater doesn’t even recognize this drive.
Model #WDBZGE0040BBK-0A
Errors:
[274303.869473] usb 2-1: reset SuperSpeed USB device number 2 using xhci-hcd
[274303.889747] xhci-hcd xhci-hcd: xHCI xhci_drop_endpoint called with disabled ep cfe5c2e0
[274303.898214] xhci-hcd xhci-hcd: xHCI xhci_drop_endpoint called with disabled ep cfe5c30c
[274303.907463] usb 2-1: Successful Endpoint Configure command
[274303.913225] sd 2:0:0:0: [sdb] Unhandled error code
[274303.918134] sd 2:0:0:0: [sdb] Result: hostbyte=0x07 driverbyte=0x00
[274303.924671] sd 2:0:0:0: [sdb] CDB: cdb[0]=0x88: 88 00 00 00 00 01 3d c0 0c 98 00 00 00 68 00 00
[274303.933871] end_request: I/O error, dev sdb, sector 5330963608
[274376.469423] usb 2-1: reset SuperSpeed USB device number 2 using xhci-hcd
[274376.490813] xhci-hcd xhci-hcd: xHCI xhci_drop_endpoint called with disabled ep cfe5c2e0
[274376.499040] xhci-hcd xhci-hcd: xHCI xhci_drop_endpoint called with disabled ep cfe5c30c
[274376.507387] usb 2-1: Successful Endpoint Configure command
[274376.513205] sd 2:0:0:0: [sdb] Unhandled error code
[274376.518122] sd 2:0:0:0: [sdb] Result: hostbyte=0x07 driverbyte=0x00
[274376.524645] sd 2:0:0:0: [sdb] CDB: cdb[0]=0x88: 88 00 00 00 00 01 45 80 0b 10 00 00 00 e0 00 00
[274376.533766] end_request: I/O error, dev sdb, sector 5460986640
[274616.199384] usb 2-1: reset SuperSpeed USB device number 2 using xhci-hcd
[274616.219774] xhci-hcd xhci-hcd: xHCI xhci_drop_endpoint called with disabled ep cfe5c2e0
[274616.228109] xhci-hcd xhci-hcd: xHCI xhci_drop_endpoint called with disabled ep cfe5c30c
[274616.236386] usb 2-1: Successful Endpoint Configure command
[274616.242224] sd 2:0:0:0: [sdb] Unhandled error code
[274616.247138] sd 2:0:0:0: [sdb] Result: hostbyte=0x07 driverbyte=0x00
[274616.253687] sd 2:0:0:0: [sdb] CDB: cdb[0]=0x88: 88 00 00 00 00 01 3c c0 09 10 00 00 00 88 00 00
[274616.262804] end_request: I/O error, dev sdb, sector 5314185488
[274679.949462] usb 2-1: reset SuperSpeed USB device number 2 using xhci-hcd
[274679.969743] xhci-hcd xhci-hcd: xHCI xhci_drop_endpoint called with disabled ep cfe5c2e0
[274679.978330] xhci-hcd xhci-hcd: xHCI xhci_drop_endpoint called with disabled ep cfe5c30c
[274679.986572] usb 2-1: Successful Endpoint Configure command
[274679.992373] sd 2:0:0:0: [sdb] Unhandled error code
[274679.997284] sd 2:0:0:0: [sdb] Result: hostbyte=0x07 driverbyte=0x00
[274680.003805] sd 2:0:0:0: [sdb] CDB: cdb[0]=0x88: 88 00 00 00 00 01 46 80 0f 20 00 00 00 a8 00 00
[274680.012894] end_request: I/O error, dev sdb, sector 5477764896
Note that this was with an ext4 filesystem. When I switched to NTFS, I got new errors. It hasn’t reset the whole USB complex, but I’m not sure if data is being written correctly.
2018-07-22T19:32:41.136930-07:00 di=2n58CMfvkZ notice kernel:[291077.408028] ufsd:write_end: copied ffe0 < len 10000
2018-07-22T19:32:46.235608-07:00 di=2n58CMfvkZ notice kernel:[291082.442122] ufsd:write_end: copied 0 < len 10000
2018-07-22T19:33:24.659424-07:00 di=2n58CMfvkZ notice kernel:[291120.812462] ufsd:write_end: copied 0 < len 10000
2018-07-22T19:33:35.263948-07:00 di=2n58CMfvkZ notice kernel:[291131.358013] ufsd:write_end: copied 0 < len 10000
2018-07-22T19:33:35.587382-07:00 di=2n58CMfvkZ notice kernel:[291131.904008] ufsd:write_end: copied 0 < len 10000
2018-07-22T19:33:57.701784-07:00 di=2n58CMfvkZ notice kernel:[291153.945899] ufsd:write_end: copied ffe0 < len 10000
2018-07-22T19:34:17.192374-07:00 di=2n58CMfvkZ notice kernel:[291173.426277] ufsd:write_end: copied ffe0 < len 10000
2018-07-22T19:34:18.766206-07:00 di=2n58CMfvkZ notice kernel:[291175.082922] ufsd:write_end: copied 0 < len 10000
2018-07-22T19:34:28.227005-07:00 di=2n58CMfvkZ notice kernel:[291184.419873] ufsd:write_end: copied 0 < len 10000
2018-07-22T19:35:39.171832-07:00 di=2n58CMfvkZ notice kernel:[291255.319155] ufsd:write_end: copied ffe0 < len 10000
2018-07-22T19:35:47.982885-07:00 di=2n58CMfvkZ notice kernel:[291264.274988] ufsd:write_end: copied ffe0 < len 10000
I wouldn’t expect much in the way of support options for this combination of drive and operating system. Your drive model begins with “WDBZGE”, which means it’s a gaming edition of their drives. None of the desktop utilities support it as the drive is intended as a storage solution for things like the Playstation (in fact, that’s its only advertised purpose), and not intended to be configured, formatted, or even used outside of that use case scenario, despite being the exact same hardware as the desktop editions.
That said, I’d be worried that the desktop version could give you the same errors if it’s something funky between the kernel and these drives. Have you tried a full disk write/readback test, in case the drive is genuinely having issues?
Hey, thanks for the reply! I did see it was a PS4 specific drive but I didn’t believe that the drive would be THAT different. Apparently, it is. It seems to have some form of specialized firmware optimized for the PS4, with no way for me to convert to ordinary portable drive firmware.
Since the PS4 could use ordinary desktop drives, I assumed a PS4 drive would be suitable for desktop application. It seems to be working Ok, minus the curious kernel errors. WDC declared the drive “failed” and asked me to RMA it. I’m not sure I believe that, but maybe I should take advantage of that knee-jerk support reaction and see if a different drive has the same issue!
I was hoping I could do some more diagnostics before giving up. Maybe I’ll just sell if to a PS4 owner on craigslist instead.
Yeah, it’s a bit curious that they don’t low-key support the drive in their utilities / let you flash a different firmware as the hardware is absolutely the same, and they drives normally retail for the same price so its not even a price differentiation issue.
I haven’t had any issues with mine under Windows, but had I known it had the aggressive power saving it does (causing a couple of seconds delay when accessing the drive if it spun down) and the utility that lets you change it on the desktop models can’t be used, I might have reconsidered. Probably not though as it’s just acting as bulk storage of ultimately non-critical data, and I can easily write something that’ll just access the drive periodically to keep it from spinning don, but definitely something people should be aware of, but probably wouldn’t find out until after the purchase (like I did).
I’d take them up on the offer (if you haven’t already - I must have reply notifications off or just missed it), just in case your drive does just have something odd going on. If nothing else you should be getting a more recent drive provided they don’t slip you a refurb, so that’s always nice. Heck, maybe they’ll let you exchange it for a desktop model if you ask nicely in the RMA request.
