2.5" 4 TB NTFS drive not recognized by Libreelec on Odroid C2

tecc · July 21, 2017 at 6:03 AM

Is there a limit to what can be accessed? The drive is recognized by my desktop PC, a Macbook air and a Fritzbox Internet Router but when I connect it to my Odroid C2 which runs the current version of Libreelec, the drive starts spinning but it never pops up or gets mounted. My 2 TB Seagate drive OTOH is recognized immediately. Any suggestions? Thx!

**Klojum** · July 21, 2017 at 6:19 AM Official Post

Is the Odroid also supposed to power the 2TB drive? There is no external power adapter for that drive?

It's possible the USB port on the C2 has limited empowering capabilities.

tecc · July 21, 2017 at 8:26 PM

The Odroid does power the 2TB drive without any issues, just not the 4 TB drive. I haven't connected both drives at the same time, so I guess the power of the Odroid's USB drive could be sufficient.

EDIT:
I've just realized the drive does not work on my PC's USB2 front port anymore, but only on my USB3 rear port which is an extra card plugged into one of the mainboard's PCI-EX sockets. Maybe the drive is soon about to fail and so not being recognized by the Odroid might be related to this. I'm not sure I can read these SMART settings, though:

Code

ID Cur Wor Thr RawValues(6) Attribute Name
01 200 200 _51 000000000022 Read Error Rate
03 253 253 _21 0000000011AD Spin-Up Time
04 _98 _98 __0 000000000864 Start/Stop Count
05 200 200 140 000000000000 Reallocated Sectors Count
07 200 200 __0 000000000000 Seek Error Rate
09 _97 _97 __0 000000000A5D Power-On Hours
0A 100 100 __0 000000000000 Spin Retry Count
0B 100 100 __0 000000000000 Recalibration Retries
0C _99 _99 __0 0000000003FA Power Cycle Count
C0 200 200 __0 000000000124 Power-off Retract Count
C1 196 196 __0 000000002F28 Load/Unload Cycle Count
C2 116 103 __0 000000000024 Temperature
C4 200 200 __0 000000000000 Reallocation Event Count
C5 200 200 __0 000000000000 Current Pending Sector Count
C6 100 253 __0 000000000000 Uncorrectable Sector Count
C7 200 200 __0 000000000000 UltraDMA CRC Error Count
C8 100 253 __0 000000000000 Write Error Rate

Display More

**Klojum** · July 21, 2017 at 9:03 PM Official Post

USB 3.0 can also provide a stronger current as per design than USB 2.0 .

**chewitt** · July 22, 2017 at 12:43 AM Official Post

Make sure the filesystems are clean, i.e. unmounted properly in Windows, else Linux often objects and fails to mount things to be safe.

dmesg usually offers some clues on the issue

tecc · July 24, 2017 at 6:05 AM

I'm confused. Now that I've resigned to using the 4 TB drive for backup only and go with the 2 TB drive, I've suddenly had this click sound when I attached the 2 TB to my girlfriend's Odroid. On day 1 the drive would not even spin up properly nor get mounted so I disconnected it to stop potential damage to it. The next day, I came over with my Odroid's power supply, which is the same make and model with an output of 5V/3000mA. Before switching the power supply, I gave it another shot and this time the drive was recognized and mounted immediately. However, when a a 2 hour movie was finished, the drive clicked again when Kodi jumped back to the file list. Since it was getting late, I hate no time to SSH in for logs.

However, per your suggestions I'd already done a chkdsk on the drive and copied over the logs from my Odroid that currently only has problems with the 4 TB and not the 2 TB drive. Still, maybe you guys can make something of it:

Using username "root". root@10.10.10.51's password: ####################### - Pastebin.com

And here's the logs from Kodi booting with the drive attached:

00:03:41.095 T:547873222096 NOTICE: special://profile/ is mapped to: special:// - Pastebin.com