SSD not waking from sleep

Have a unused samsung ssd which I’ve connected to my vero+ but it goes to sleep and doesn’t wake up. using file manager I get Path not found or invalid.
The only way to get it to work is to disconnect and reconnect.
Can I get round this, or is a ssd not suitable.

That doesn’t sound “normal”, are you sure it is not a power issue? Can you try with a powered hub? Upload kernel logs via MyOSMC or grab-logs -K -d and share the URL.

Exact model of the SSD? Often you find the max. current besides the voltage (5V) on the label of the SSD. The max. current will only be reached if the SSD is under fulll load (what never will happen with an USB 2.0 port) but a collegue at work showed me an SSD with 1.7 A some days ago which would be more than 3 times more an USB 2.0 port could offer in theory.

Have moved it to a powered hub, will have to wait to see if it happens again.
Power is 1.2A
not sure if ext case adds anything, but wouldn’t have thought it would.

A SATA to usb adapter would have very minimal power draw. Some adapters can be problematic with Linux though. I remember running across several threads where Orico cases were identified as causing some issues for example.

Drive is a Cable Matters type, and is the second one I’ve tried. Both did the same. As I’m using my vero tonight will know in the morning.

Keep us posted

I have changed the drive onto the other vero, it is on a powered hub.
it is still doing it .

Here are logs

Vero that the drive is on
https://paste.osmc.tv/afebosewif

and the other one on the network
https://paste.osmc.tv/cigosasaki

Don’t know how long before it happens, maybe the logs will say.

at the moment I have to unplug the drive and reconnect to get it back running.

Seems to be at about 3 hours inactivity its shuts down.

So the issue is only about accessing via the network or you also loose access on the Vero the drive is physically connected to?

Also you have 4 drives connected does the problem only happen with the SSD?

Apr 25 16:32:46 bedroomosmc kernel: scsi 0:0:0:0: Direct-Access     Verbatim STORE N GO       5.00 PQ: 0 ANSI: 6
Apr 25 16:32:46 bedroomosmc kernel: sd 0:0:0:0: [sda] 241735680 512-byte logical blocks: (123 GB/115 GiB)
Apr 25 16:32:46 bedroomosmc kernel: sd 0:0:0:0: [sda] Write Protect is off
Apr 25 16:32:46 bedroomosmc kernel: sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00
Apr 25 16:32:46 bedroomosmc kernel: sd 0:0:0:0: [sda] No Caching mode page found
Apr 25 16:32:46 bedroomosmc kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Apr 25 16:32:46 bedroomosmc kernel: sd 0:0:0:0: [sda] No Caching mode page found
Apr 25 16:32:46 bedroomosmc kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Apr 25 16:32:46 bedroomosmc kernel:  sda: sda1
Apr 25 16:32:46 bedroomosmc kernel: sd 0:0:0:0: [sda] No Caching mode page found
Apr 25 16:32:46 bedroomosmc kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Apr 25 16:32:46 bedroomosmc kernel: sd 0:0:0:0: [sda] Attached SCSI removable disk
Apr 25 16:32:46 bedroomosmc kernel: aml_wifi wifi.32: [extern_wifi_set_enable] WIFI  Disable! 240
Apr 25 16:32:47 bedroomosmc kernel: scsi 2:0:0:0: Direct-Access     Kingston DT microDuo 3C   PMAP PQ: 0 ANSI: 6
Apr 25 16:32:47 bedroomosmc kernel: sd 2:0:0:0: [sdc] 121110528 512-byte logical blocks: (62.0 GB/57.7 GiB)
Apr 25 16:32:47 bedroomosmc kernel: sd 2:0:0:0: [sdc] Write Protect is off
Apr 25 16:32:47 bedroomosmc kernel: sd 2:0:0:0: [sdc] Mode Sense: 45 00 00 00
Apr 25 16:32:47 bedroomosmc kernel: sd 2:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Apr 25 16:32:47 bedroomosmc kernel: aml_wifi wifi.32: [extern_wifi_set_enable] WIFI  Enable! 240
Apr 25 16:32:47 bedroomosmc kernel:  sdc: sdc1
Apr 25 16:32:47 bedroomosmc kernel: sd 2:0:0:0: [sdc] Attached SCSI removable disk
Apr 25 16:32:47 bedroomosmc kernel: sd 1:0:0:0: [sdb] 499744768 512-byte logical blocks: (255 GB/238 GiB)
Apr 25 16:32:47 bedroomosmc kernel: sd 1:0:0:0: [sdb] Write Protect is off
Apr 25 16:32:47 bedroomosmc kernel: sd 1:0:0:0: [sdb] Mode Sense: 21 00 00 00
Apr 25 16:32:47 bedroomosmc kernel: sd 1:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Apr 25 16:32:47 bedroomosmc kernel:  sdb: sdb1
Apr 25 16:32:47 bedroomosmc kernel: sd 1:0:0:0: [sdb] Attached SCSI removable disk
Apr 25 16:32:47 bedroomosmc systemd[1]: Started Rebuild Hardware Database.
Apr 25 16:32:47 bedroomosmc systemd[1]: Starting udev Coldplug all Devices...
Apr 25 16:32:47 bedroomosmc kernel: scsi 3:0:0:0: Direct-Access     Samsung  SSD 860 EVO 1TB  0    PQ: 0 ANSI: 6
Apr 25 16:32:47 bedroomosmc kernel: random: nonblocking pool is initialized
Apr 25 16:32:47 bedroomosmc kernel: sd 3:0:0:0: [sdd] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
Apr 25 16:32:47 bedroomosmc kernel: sd 3:0:0:0: [sdd] Write Protect is off
Apr 25 16:32:47 bedroomosmc kernel: sd 3:0:0:0: [sdd] Mode Sense: 43 00 00 00
Apr 25 16:32:47 bedroomosmc kernel: sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 25 16:32:47 bedroomosmc kernel: GPT:Primary header thinks Alt. header is not at the end of the disk.

After 17 minutes there is a disconnect, I assume that was not initiated by yourself? That would indicate either a power issue or an issue with the SSD controller.>

Apr 25 17:49:39 bedroomosmc kernel: usb 1-2.4: USB disconnect, device number 7
Apr 25 17:49:39 bedroomosmc kernel: sd 3:0:0:0: [sdd] Synchronizing SCSI cache
Apr 25 17:49:39 bedroomosmc kernel: sd 3:0:0:0: [sdd]  
Apr 25 17:49:39 bedroomosmc kernel: Result: hostbyte=0x01 driverbyte=0x00
Apr 25 17:49:39 bedroomosmc udisks-glue[549]: Device file /dev/sdd2 unmounted from /media/MyMedia
Apr 25 17:49:39 bedroomosmc udisks-glue[549]: Device file /dev/sdd2 removed
Apr 25 17:49:39 bedroomosmc udisks-glue[549]: Device file /dev/sdd1 unmounted from /media/EFI
Apr 25 17:49:39 bedroomosmc udisks-glue[549]: Device file /dev/sdd1 removed
Apr 25 17:49:39 bedroomosmc udisks-glue[549]: Device file /dev/sdd removed

no I didn’t initiate it.
Yes it only happens with SSD (Tried on both drives)
Yes the physical drive looses it as well.

Then as written I believe must be power or controller issue.

How do I fix that?
The hub is a OSMC powered hub, and I’ve already changed the SATA to usb adapter.

Hard to say as we don’t know exactly what is causing it

If it’s 17 minutes, it could be that we suspend the drive but it can’t wake.

He could try disabling hdparm

Would that cause a USB Disconnect?

Not sure. Depends how the caddy is responding to it.

When I checked this morning it was ok for about 3 hours.
I can tell because the slideshow background kept running, for about that time. Then it stops, which I presume is the hard disk going off line.

What devices are connected to this hub?

On the first vero it was direct into the vero.
On the second the hub had a couple of usb sticks which were not being used.