I have a NanoPI R5S with a Seagate Backup Plus external USB HDD.
The drive is only used occasionally for its capacity so I’d prefer for it to stay down most of the time. It’s the only audible thing on my entire desktop
Tried sdparm but it doesn’t even list the relevant parameters:
root@NanoPi:~# sdparm -l -a /dev/sda
/dev/sda: Seagate BUP Slim SL 0304
Direct access device specific parameters: WP=0 DPOFUA=0
Flexible disk (SBC) [fd] mode page:
XRATE 0 [cha: n, def: 0, sav: 0] Transfer rate
NUM_HD 16 [cha: y, def: 16, sav: 16] Number of heads
SECT_TR 63 [cha: y, def: 63, sav: 63] Sectors per track
BYTE_SECT 512 [cha: y, def:512, sav:512] Bytes per sector
NUM_CYL 16383 [cha: y, def:16383, sav:16383] Number of cylinders
I was able to spindown the disk using sdparm --readonly --command=stop /dev/sda and spin it back up with sdparm --command=start /dev/sda so it can theoretically work with software. The problem is there’s neither SCT nor STANDBY parameters available in sdparm, so those don’t work:
Interesting to look at the USB adapter. Makes sense actually. Do these options work?
hdparm -y /dev/sda # enter standby mode
hdparm -Y /dev/sda # enter sleep mode
It is btw not about the USB controller of the R5S, but the USB-SATA adapter of the external drive/case/docking station. But of course also the controller/driver/kernel might be a reason. We’ll switch to mainline kernel with the R5S soon, so then worth to retest.
It is btw not about the USB controller of the R5S, but the USB-SATA adapter of the external drive/case/docking station. But of course also the controller/driver/kernel might be a reason. We’ll switch to mainline kernel with the R5S soon, so then worth to retest.
Oh, interesting, is that going to be a new DIetPi release?
Okay seems to be all hdparm power state instructions which fail.
Most likely we will make available new R5S images between the DietPi releases, since the DietPi code on the systems does not need to change, only the build tools.