Known issue? Problem with 4TB Maxtor USB HDD (actually 'Seagate') connected to Vero4K+

Hi guys,
Just connected 4TB HDD USB3 to Vero4K+ via OSMC USB Hub.
It’s the only device connected to the USB hub.
I thought I was buying a ‘Maxtor’ drive, but it seems to be Seagate anyway…
I think the PSU is failing on my hub, so I’ve ordered another which is on the way.
My question is:
Is this particular HDD (Seagate) a known issue with OSMC (Vero4K+)?
If it’s just the PSU on the hub, that should be fine.
Thanks.

[Céad Beal 27 11:31:36 2020] usb 1-1.4: USB disconnect, device number 3

[Céad Beal 27 11:31:40 2020] usb 1-1.4: new high-speed USB device number 4 using xhci-hcd

[Céad Beal 27 11:31:40 2020] usb 1-1.4: New USB device found, idVendor=0bc2, idProduct=61b7

[Céad Beal 27 11:31:40 2020] usb 1-1.4: New USB device strings: Mfr=2, Product=3, SerialNumber=1

[Céad Beal 27 11:31:40 2020] usb 1-1.4: Product: M3 Portable

[Céad Beal 27 11:31:40 2020] usb 1-1.4: Manufacturer: Seagate

[Céad Beal 27 11:31:40 2020] usb 1-1.4: SerialNumber: NM16S63T

[Céad Beal 27 11:31:40 2020] usb-storage 1-1.4:1.0: USB Mass Storage device detected

[Céad Beal 27 11:31:40 2020] scsi1 : usb-storage 1-1.4:1.0

[Céad Beal 27 11:31:41 2020] scsi 1:0:0:0: Direct-Access Seagate M3 Portable 9300 PQ: 0 ANSI: 6

[Céad Beal 27 11:31:41 2020] sd 1:0:0:0: [sdb] Spinning up disk...

[Céad Beal 27 11:31:42 2020] **...................................................................................................not responding...**

[Céad Beal 27 11:33:21 2020] sd 1:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).

[Céad Beal 27 11:33:21 2020] sd 1:0:0:0: [sdb] 7814037167 512-byte logical blocks: (4.00 TB/3.63 TiB)

[Céad Beal 27 11:33:28 2020] sd 1:0:0:0 **: [sdb] Test WP failed, assume Write Enabled**

[Céad Beal 27 11:33:35 2020] sd 1:0:0:0: [sdb] Asking for cache data failed

[Céad Beal 27 11:33:35 2020] sd 1:0:0:0: [sdb] Assuming drive cache: write through

[Céad Beal 27 11:33:35 2020] sd 1:0:0:0: [sdb] Spinning up disk...

[Céad Beal 27 11:33:36 2020] **....................................................................................................not responding...**

[Céad Beal 27 11:35:16 2020] sd 1:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).

[Céad Beal 27 11:35:23 2020] sd 1:0:0:0 **: [sdb] Test WP failed, assume Write Enabled**

[Céad Beal 27 11:35:30 2020] sd 1:0:0:0: [sdb] Asking for cache data failed

[Céad Beal 27 11:35:30 2020] sd 1:0:0:0: [sdb] Assuming drive cache: write through

They merged in 2005/2006.

Looks like not enough power to spin up. So try the new power supply first.
Also if you have another USB cable you could try that. I once had an issue with a Maxtor external drive that came down to a faulty cable.

I connected HDD to MacBook.
HDD is ok, and cable ok.
Hopefully it will be fine with new hub.

Thanks.

Let us know how it goes.

1 Like

I’ve been using two of these drives with my Vero 4K for a few years, powered by an external hub (non osmc). Never had any playback problems at all, but do tend to lose files more often than I’d like when switching between my Mac and vero (recoverable via disk utility first aid) even though I always unmount drives correctly.

I had been using the 1TB Maxtor HDD for a few years with no problems (with OSMC powered USB hub) … that’s why I chose the 4TB version. I have a few 1TB drives, and they keep filling up :slight_smile:
I find the PSUs that we use for hubs, Veros and Pis seem to wear out after a few years.

Once the HDD is connected to Vero, I access it from the Mac with Samba.
Probably better not to be plugging HDD in and out and in again.

Yeah I hear that about 1TB drives filling up. I’m now using 2x 4TB Maxtors. I generally use samba to transfer smaller files as I thought transferring a full 4K rip over samba would take far too long. Might give it a try though, as I would like to minimise unplugging drives.

It was working ok with Vero4K+ on a powered USB hub with some HDDs on the same hub. But it stopped working after a few days - it wouldn’t spin up.

Now, I’ve moved it to Vero USB hub. It will only spin up, if there are no other HDDs on the same hub.

I’m trying to fix it now with fsck…

/dev/sda1 194235 1550 178349 1% /media/ab1eb9e4-bd96-40c8-8bb9-0e5bbe06b62d
osmc@osmc-Cavendish:/$ sudo fsck /dev/sda2
fsck from util-linux 2.29.2
e2fsck 1.43.4 (31-Jan-2017)
ext2fs_check_desc: Corrupt group descriptor: bad block for block bitmap
fsck.ext4: Group descriptors look bad… trying backup blocks…
Superblock needs_recovery flag is clear, but journal has data.
Recovery flag not set in backup superblock, so running journal anyway.
/dev/sda2: recovering journal
JBD2: Invalid checksum recovering block 4 in log
JBD2: Invalid checksum recovering block 5 in log
JBD2: Invalid checksum recovering block 5 in log
JBD2: Invalid checksum recovering block 5 in log
Journal checksum error found in /dev/sda2
Pass 1: Checking inodes, blocks, and sizes

ok, I’ve given up on that…
I’ll try just re-format it and try again.
I think the OSMC powered-hub can power this HDD, but not with other HDDs at the same time.
If I wanted 2 x 4TB USB3 HDDs, I think I would need a 3A (at least) PSU for the OSMC powered-hub.