Gen2 poweroff

Has anybody noticed that if you type poweroff on the gen2. It will halt the system. But the led ends up solid blue. Looks like the system is running but it is not. Here is the sequence of the poweroff.

The system is going down NOW!

Sent SIGTERM to all processes
Block size total free used max
----!!! ### APKG Server Terminated ### !!!
190325 11:50:00 mysqld_safe mysqld from pid file /mnt/HD_a4/.@database@/TestGen2.pid ended
Block size total free used max


2^001 0 0 0 0
2^002 0 0 0 0
2^003 0 0 0 0
2^004 0 0 0 0
2^005 0 0 0 0
2^006 0 0 0 0
2^007 0 0 0 0
2^008 0 0 0 0
2^009 0 0 0 0
2^010 0 0 0 0
2^011 0 0 0 0
2^012 0 0 0 0
2^013 0 0 0 0
2^014 0 0 0 0
2^015 0 0 0 0
2^016 0 0 0 0
2^017 0 0 0 0
2^018 0 0 0 0
2^019 0 0 0 0
2^020 0 0 0 0
2^021 0 0 0 0
2^022 0 0 0 0
2^023 0 0 0 0

total size : 0 bytes
free size : 0 bytes
used size : 0 bytes
md: md0 in immediate safe mode

Sent SIGKILL to all processes
nfsd: last server has exited, flushing export cache

Requesting system poweroff
sd 0:0:0:0: [sda] Synchronizing SCSI cache
sd 0:0:0:0: [sda] Stopping disk
xhci-hcd f1058000.usb3: remove, state 1
usb usb3: USB disconnect, device number 1
xhci-hcd f1058000.usb3: USB bus 3 deregistered
xhci-hcd f1058000.usb3: remove, state 1
usb usb2: USB disconnect, device number 1
xhci-hcd f1058000.usb3: USB bus 2 deregistered
ata1.00: disabled
sd 0:0:0:0: [sda] Synchronizing SCSI cache
sd 0:0:0:0: [sda]
Result: hostbyte=0x04 driverbyte=0x00
sd 0:0:0:0: [sda] Stopping disk
sd 0:0:0:0: [sda] START_STOP FAILED
sd 0:0:0:0: [sda]
Result: hostbyte=0x04 driverbyte=0x00
Shutting Down Marvell Ethernet Driver
Enter suspend mode on port #0
Shutting Down Marvell Ethernet Driver
System halted.

Compare this with the old win95 “It is now safe to turn off your computer” message that got displayed on old PCs that had AT style power supplies, and not the swanky new ATX style ones.

And or-- See also “always on” devices like the rPI.

The Gen2 seems to lack hardware to disable the power pin, and turn itself completely off. (Apparently, adding a flipflop gate, a resistor, and another GPIO pin to interrupt the power lead entering the system was too costly.)

Since the LEDs on the front are fully programmable, I would suggest as a very last action before halting, that the kernel set the LEDs to some odd color, like solid green. That would let you know that the system has successfully halted, and can be powered off safely by removing the power plug.

I was looking into the possibility of using a smart plug to turn the device back on. It should work. Just not sure if the disk partitions are unmounted.

First gen is similar. If one issues the shutdown command via the Dashboard (or SSH) the unit doesn’t totally power off. Instead there is still power going to the board as indicated by the network LED’s are still active.

Now if WoL was supported this would be a good thing since one could use WoL to turn on the My Cloud. But WoL isn’t supported.

True. But if you were to plug the device into one of these smart plugs. It would be the same as wol. You could say alexa turn off the My Cloud.

If one goes that route (using smart plugs and Alexa) they could (somehow) probably go even further and have Alexa run a shutdown script to trigger the My Cloud to shut down before issuing the Alexa command to trigger the smart plug. Probably something like this: Launch a Script Using Alexa Voice Commands

Interesting. I looked around and found a powershell script to communicate with the tp-link smart plug. I’ll have to take a look at the alexa code.
Thanks