New Installtion on 5Big - Trouble adding disks

[uelpenich]

The buttons executable worked exactly as described.
The reboot behavior was exactly that, it ran perfectly.
The shutdown behavior was quick, all the disks stopped as they should and everything was unreachable after a few seconds.
The system did remain powered on and did not respond to the power switch, but as we discussed, [b]that's totally fine as I know the system is off after all the disks click,[/b] and a few moments.

Well done and thank you again!

Are you shure that the "disk click" is really caused by the hard disks?
With my 5big1 I also mentioned the "disks clicking" when the NAS had nothing to do. Disk clicking means every second some 5 to 10 to clicks. It took me some time to point out that it were not the disks but the fan. I had to dismantel the fan box to see that the fan controller pulsed the fan every second. Try to change the fan speed to see if it is also true with your 5big1.

[mattenwright]

@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 .

[fvdw]

thks for testing so all works as expected, we can incorporate this in the next release.
We will make a patch for you that at boot the correct buttons daemon is loaded for 5big1

[fvdw]

attached the patch, to be used when running fvdw-sl 18-2
Use upload patch menu of the webinterface and read the help text how to upload patch and use control code: unzip

In addition you should write the kernel UIMAGE-3142-5BIG1-33 to partition sda6 to have it loaded automatic at boot
put the kernel in the fvdw shared folder and use this command after logging in with ssh

Code: Select all

dd if=/direct-usb/fvdw/UIMAGE-3142-5BIG1-33 of=/dev/sda6

CAUTION ! be sure to us as of /dev/sda6 otherwise you will write it on wrong partition with all negative consequences.

Now everything should work after next reboot

[mattenwright]

Not to raise a dead post, but I just wanted to thank everyone for the wonderful work.
I recently had to put some new disks in (there was only one newer one), and I was able to get everything going again without any issues.

That and I realized I never thanked everyone properly to begin with.
So, thank you all!