Posts by VancoD

Sorry - just didn't see anything of note to include. If it's of any use after the fact:

aGeW (dmesg)

Should I have issue again I'll capture the buffer again.

Well - good news / odd news.
I shut down LibreELEC to boot from my stick, had an issue with the bootloader, so I was going to run parted on it (inside LibreELEC) to wipe it out.... and....

Kodi:~ # dmesg | grep sdb

[ 2.987150] sd 6:0:0:0: [sdb] 60566016 512-byte logical blocks: (31.0 GB/28.9 GiB)

[ 2.987883] sd 6:0:0:0: [sdb] Write Protect is off

[ 2.987886] sd 6:0:0:0: [sdb] Mode Sense: 2b 00 00 08

[ 2.988641] sd 6:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA

[ 3.236826] sdb: sdb1 sdb2

[ 3.239190] sd 6:0:0:0: [sdb] Attached SCSI removable disk

[ 516.450350] sd 6:0:0:0: [sdb] 60566016 512-byte logical blocks: (31.0 GB/28.9 GiB)

[ 516.451111] sd 6:0:0:0: [sdb] Write Protect is off

[ 516.451116] sd 6:0:0:0: [sdb] Mode Sense: 2b 00 00 08

[ 516.451730] sd 6:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA

[ 517.966454] sdb: sdb1 sdb2
[ 517.969520] sd 6:0:0:0: [sdb] Attached SCSI removable disk

<USB stick pulled / USB drive inserted>
[ 710.369064] sdb:

[ 715.861101] sdb:

[ 731.358468] sdb:

[ 781.405228] sd 6:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).

[ 781.405608] sd 6:0:0:0: [sdb] 5860533168 512-byte logical blocks: (3.00 TB/2.73 TiB)

[ 781.406602] sd 6:0:0:0: [sdb] Write Protect is off

[ 781.406608] sd 6:0:0:0: [sdb] Mode Sense: 34 00 00 00

[ 781.407597] sd 6:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA

[ 781.409590] sd 6:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).

[ 781.476028] sdb: sdb1

[ 781.477203] sd 6:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).

[ 781.479952] sd 6:0:0:0: [sdb] Attached SCSI disk

[ 781.842249] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)

So it's now "fine".

Kodi:~ # ls -l /var/media/sdb1-ata-ST3000DM001-1CH1/

total 128

drwx------ 2 1000 1000 20480 Jul 20 2014 MST3k

drwxr-xr-x 5 1000 1000 12288 Sep 20 08:42 Movies

drwxr-xr-x 2 1000 1000 49152 Sep 18 10:09 Music

drwxr-xr-x 3 1000 1000 4096 Jul 8 2016 RiffTrax

drwxr-xr-x 7 1000 1000 4096 Feb 21 2016 TV

drwxr-xr-x 2 1000 1000 4096 Nov 18 14:59 Woodworking Vids

drwx------ 6 1000 1000 12288 Nov 20 10:37 YouTubes

drwx------ 2 1000 1000 16384 Jun 26 2014 lost+found

drwxrwxr-x 3 1000 1000 4096 Nov 23 18:13 temp

I'm wondering if the drive enclosure is going bad......

I just shot my previous install of Kodi in the face because it was becoming increasingly problematic over the course of the last several years as XBMC (and Kodibuntu) "matured" to where they are today - Kodi, and "no longer supported". Updating the core OS resulted in odd behavior in Kodi.

I had a perfectly functional external USB drive (2 TB) on that Kodi system. It was fine when I shut down my system, and it was not plugged in during the LibreELEC install....

Now that I've <ahem> "upgraded" to LibreELEC my USB drive isn't being seen correctly.

Kodi:~ # blkid

<snip>
/dev/sdb: PTTYPE="PMBR"

Kodi:~ # blkid -o list

device fs_type label mount point UUID

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------

<snip>
/dev/sdb (not mounted)

Kodi:~ # dmesg | grep sdb

[ 641.920427] sd 6:0:0:0: [sdb] 4294967295 512-byte logical blocks: (2.20 TB/2.00 TiB)

[ 641.921439] sd 6:0:0:0: [sdb] Write Protect is off

[ 641.921442] sd 6:0:0:0: [sdb] Mode Sense: 34 00 00 00

[ 641.922422] sd 6:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA

[ 642.159137] sd 6:0:0:0: [sdb] Attached SCSI disk

[ 1742.619992] F2FS-fs (sdb): Magic Mismatch, valid(0xf2f52010) - read(0xebd0a0a2)

[ 1742.619996] F2FS-fs (sdb): Can't find valid F2FS filesystem in 1th superblock

[ 1742.620616] F2FS-fs (sdb): Magic Mismatch, valid(0xf2f52010) - read(0x0)

[ 1742.620619] F2FS-fs (sdb): Can't find valid F2FS filesystem in 2th superblock

[ 1742.620631] F2FS-fs (sdb): Magic Mismatch, valid(0xf2f52010) - read(0xebd0a0a2)

[ 1742.620632] F2FS-fs (sdb): Can't find valid F2FS filesystem in 1th superblock

[ 1742.620634] F2FS-fs (sdb): Magic Mismatch, valid(0xf2f52010) - read(0x0)

[ 1742.620635] F2FS-fs (sdb): Can't find valid F2FS filesystem in 2th superblock

The boot buffer messages have me concerned - can LibreELEC not read GPT partitions??

From parted - the news does not look good at all:
(parted) print all

print all

Error: Invalid argument during seek for read on /dev/sdb

Retry/Ignore/Cancel? I

I

Error: The backup GPT table is corrupt, but the primary appears OK, so that will be used.

OK/Cancel? OK

OK

Model: ST3000DM 001-1CH166 (scsi)

Disk /dev/sdb: 2199GB

Sector size (logical/physical): 512B/512B

Partition Table: unknown

Disk Flags:

I really hope that "Partition table unknown" message is simply an issue with LibreELEC's version of parted...

At this point I'm most likely to just go back to Ubuntu or Debian hoping that the drive is fine (as I believe it to be) - but I thought I'd ask here just on the odds there's a simple answer to my issue.... Sadly I don't have another Linux box handy that I can try the drive on.....