HDD temperature reached in LaCie Cloudbox, safe temp?

[Cubytus]

That's what I was about to ask. This is a good idea to integrate it in the next version. Will it show with a proper GUI once finalized?

I tried to log in as root to access the root tree, but it doesn't accept the default password, which I haven't changed. If this is a bug, it will be hard to reproduce.

[fvdw]

yes in the new version it will be incorporate in the GUI

To root access you need to use an ssh client like putty (telnet is not running)
user: root password: giveit2me (default)

[Jocko]

Hi Cubytus,

Additionally,

Will it show with a proper GUI once finalized?

There won't have a specific menu because this new feature can be used in three contexts:
- A manual standby with auto wake-up (=> add a new button in the Shutdown/Restart menu)
- use it with the temperature guard daemon so that the NAS wakes up automatically after a standby time (=> add an option with WOL mode)
- Plan it as the "Nas standby Wol" or "Nas shutdown" jobs in the Schedule Servers menu (=> add a new item in the select field)

I tried to log in as root to access the root tree, but it doesn't accept the default password, which I haven't changed. If this is a bug, it will be hard to reproduce.

Check if your numerical keypad is enabled as you use its key '2'

You can try to switch the access mode in the ssh menu (select key mode and again pwd mode). This may restore access.

[Cubytus]

Hmmm, I tried to toggle it back and forth from SSH-password to SSH-key, but it keeps on asking for the old password. Or is there a way to reset SSH altogether? In which case it would be good for me at the moment, but nevertheless a security risk. I noted I made backup on April 16th, probably back when I installed it. Would it restore SSH access? And what would be lost exactly when restoring the database?

There won't have a specific menu because this new feature can be used in three contexts:
- A manual standby with auto wake-up (=> add a new button in the Shutdown/Restart menu)

Is there a programmable autostart-autostandby already implemented? This could solve the issue, and streamline the experience with regular PC settings.

- use it with the temperature guard daemon so that the NAS wakes up automatically after a standby time (=> add an option with WOL mode)

…Or make it the default mode for temperature-related shutdowns: the NAS doesn't wake up from sleep when trying to access it when it has gone to standby with WoL, so the basic feature is broken anyways.

[Jocko]

Hi Cubytus,

You can reset the root password by using a cron job.

So you need to schedule this shell command :

Code: Select all

[ -f /etc/rootpasswd ] && echo 'use custom password' >>/direct-usb/cronjobs/cron.log; unlink /etc/rootpasswd; echo 'use default password' >>/direct-usb/cronjobs/cron.log

Please to use exactly this command (for example: keep the space chars in the test ([...])
I added a test to understand why you can not get a root access with the default passwd. So if you read 'use custom password' in cron log that means you already set a custom password previously.

You must plan this job without using any '*'(except for week field) so that the job runs only once.

When you read 'use default password' in the cron log (refresh the menu upto read it, by default the auto refresh is 10min), you must restart the NAS.

After rebooting the default root password is again used to login.

[Cubytus]

Ok, it has been reset thanks to the instructions. Of course, I had to start the cron assistant for temporary jobs. However, I think this is a security risk: root access is the topmost user in a Unix-like OS, and here it is accessible with only a web-interface login. This login should at least be as secured as the root one.

And where is the temp-alert.sh file?

[fvdw]

you can enable https for the web gui, it is an option in the web interface

temp-alert.sh can be found in /etc

[Jocko]

Hi Cubytus,

This login should at least be as secured as the root one.

version 16.0 uses stronger hash for passwords encryption with http protocol.
and I wrote in several topics to enable https feature for a remote access and not to open the port 80 as with a basic authentication, http protocol uses a very weak encryption (base24 encoding)

[Cubytus]

Is the HTTPS hash as secure as the OpenSSH one?

Besides, the disk finally reached its max temperature, but the script apparently didn't work. I used "60" in place of "yy" so as to automatically wake it up after an hour, but it still hasn't woken up, although the disk was put on standby about 6 hours ago. Any way to debug this?

[Jocko]

Hi Cubytus,

Is the HTTPS hash as secure as the OpenSSH one?

Yes that is and with the next version apache server will use also SHA256-signed SSL certificate instead of SHA1 SSL certificate (deprecated)

Besides, the disk finally reached its max temperature, but the script apparently didn't work. I used "60" in place of "yy" so as to automatically wake it up after an hour, but it still hasn't woken up, although the disk was put on standby about 6 hours ago. Any way to debug this?

1/ Can you post your temp-alert.sh

2/ check if the nas succeeds to auto-wake-up after 5min
- in putty do

echo 5 > /etc/time-suspend.txt

- Go to the shutdown/restart menu and do a standby with WoL

So if there is no issue, the NAS should wake up after 5 min