@fvdw
So I finally had a few minutes to do some testing, and just loading the new kernel provided the following output to both the netconsole and serial console:
- Code: Select all
[ 276.707354] FVDW-SL-GPIO_KEYS: Detected button release, duration of 99
[ 283.626654] FVDW-SL-GPIO_KEYS: Detected button press
[ 283.731499] FVDW-SL-GPIO_KEYS: Detected button release, duration of 99
[ 286.236284] FVDW-SL-GPIO_KEYS: Detected button press
[ 291.031659] FVDW-SL-GPIO_KEYS: Detected button release, duration of 4790
[ 299.168336] FVDW-SL-GPIO_KEYS: Detected button press
[ 309.253044] FVDW-SL-GPIO_KEYS: Detected button release, duration of 10079
[ 331.059016] FVDW-SL-GPIO_KEYS: Detected button press
[ 335.455189] FVDW-SL-GPIO_KEYS: Detected button release, duration of 4391
Nothing happened after the long durations, but the amount of time was detected correctly.
I then connected via ssh and killed the running buttonsd (as you described) and ran the buttons-5big1.
Once running I then pressed the front button for about 3-4 seconds, and got the following on the ssh terminal:
- Code: Select all
root@LaCie5Big1-fvdw:/share/1003/fvdw #
pressed time 1606768619
start time =Wed Mar 11 00:41:20 1931
released time 1606768620 diff2 =1
Front button pressed more then 1 second but less then 5 seconds. Starting reboot procedure now...
pressed time 1606768621
start time =Wed Mar 11 00:41:20 1931
released time 1606768627 diff2 =6
Front button pressed for more then 5 seconds. Starting poweroff procedure now...
killall: udevd: no process killed
killall: smbd: no process killed
killall: nmbd: no process killed
cat: can't open '/var/run/noflushd.pid': No such file or directory
kill: you need to specify whom to kill
After that the serial console showed the system rebooting, and then the marvel prompt, and then booting to the old kernel (all as expected).
The long hold (more than 5 seconds) also works to shutdown perfectly (after buttonsd is killed and the new buttons-5big1 is loaded as above). The only difference was a slight difference in the ssh terminal:
- Code: Select all
root@LaCie5Big1-fvdw:/share/1003/fvdw #
pressed time 1606770005
start time =Fri Mar 6 11:27:44 1931
released time 1606770012 diff2 =7
Front button pressed for more then 5 seconds. Starting poweroff procedure now...
@uelpenich
The disk "click" is actually the hard drive(s), it's a single click per disk as far as I can tell, though it does happen pretty quickly, it does only happen once, and its after the shutdown request. Its the same click that can be heard after a shutdown request from the web admin console. The serial console outputs a SCSI disk cache sync and reports a disk stop for each disk. So based on that I would say the "click" is a head park (or today's equivalence thereof). This is the output that can be seen from the console (note, I only have 4 disks installed at the moment):
- Code: Select all
396.909243] nfsd: last server has exited, flushing export cache
[ 399.117874] sd 4:0:0:0: [sda] Synchronizing SCSI cache
[ 399.123805] sd 4:0:0:0: [sda] Stopping disk
[ 399.958619] sd 3:0:0:0: [sdb] Synchronizing SCSI cache
[ 399.978589] sd 3:0:0:0: [sdb] Stopping disk
[ 399.998613] sd 2:0:0:0: [sdc] Synchronizing SCSI cache
[ 400.018581] sd 2:0:0:0: [sdc] Stopping disk
[ 400.038610] sd 1:0:0:0: [sdd] Synchronizing SCSI cache
[ 400.058582] sd 1:0:0:0: [sdd] Stopping disk
Though I know the sound you're speaking of, and it can definitely sound like a drive, especially when in an enclosure :vhcool .