Hi I have a Raspberry Pi 2 running completely up to date osmc - albeit I have not performed a clean install.
Since the January update I’ve noticed that my osmc install appears less stable, and has started disconnecting my usb drive rather randomly.
My dmesg says:
[ 4177.157231] scsi 1:0:0:0: Direct-Access Seagate Expansion 0637 PQ: 0 ANSI: 6
[ 4177.161931] sd 1:0:0:0: Attached scsi generic sg0 type 0
[ 4177.162442] sd 1:0:0:0: [sdb] 1953525167 512-byte logical blocks: (1.00 TB/931 GiB)
[ 4177.167390] sd 1:0:0:0: [sdb] Write Protect is off
[ 4177.167435] sd 1:0:0:0: [sdb] Mode Sense: 2b 00 10 08
[ 4177.169013] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
[ 4177.203400] sdb: sdb1
[ 4177.209913] sd 1:0:0:0: [sdb] Attached SCSI disk
[ 4182.337931] Buffer I/O error on dev sda1, logical block 122061314, lost sync page write
[ 4182.337957] JBD2: Error -5 detected when updating journal superblock for sda1-8.
[ 4182.337965] Aborting journal on device sda1-8.
[ 4182.337984] Buffer I/O error on dev sda1, logical block 122061314, lost sync page write
[ 4182.337994] JBD2: Error -5 detected when updating journal superblock for sda1-8.
[ 4192.107995] d_splice_alias: 2121 callbacks suppressed
[ 4192.108017] VFS: Lookup of ‘1-1.2’ in sysfs sysfs would have caused loop
[ 4192.108103] VFS: Lookup of ‘1-1.2’ in sysfs sysfs would have caused loop
If after one of these episodes I unplug and replug the usb drive everything works - of course following efsfsck.
Now the drive is on a separate usb hub - is this a osmc kernel issue, or is there something wrong with my hub or its power supply? How would I go about further categorising this?
I guess the “Lookup of ‘1-1.2’” indicates the usb hub is going down for some reason, but I’m not certain as to the cause.
Many thanks
Andy