Vexz

Update

I fixed it with a restore of a backup on a new USB device and deleted all partitions via console on the SSD first.


I just upgraded to 7.3.1 and installed an SSD before doing so to migrate the system to the SSD after the update. While going through the process I encountered this error:

➜ Starting configuration... ➜ Starting internal boot setup. This might take a while... ➜ Configuring internal boot pool... ✗ Internal boot setup returned an error: assignableDisks snapshot: [{"id":"Samsung_SSD_970_EVO_Plus_500GB_S4EVNJ0N234529T","serialNum":"Samsung_SSD_970_EVO_Plus_500GB_S4EVNJ0N234529T","device":"/dev/nvme0n1"}] assignableDisks resolved serialNum->device: [["Samsung_SSD_970_EVO_Plus_500GB_S4EVNJ0N234529T",{"bootId":"Samsung_SSD_970_EVO_Plus_500GB_S4EVNJ0N234529T","devicePath":"/dev/nvme0n1"}]] Running: emcmd debug=cmdCreatePool,cmdAssignDisk,cmdMakeBootable Running: emcmd cmdCreatePool=apply&poolName=boot&poolSlots=1 mkbootpool: command failed or timed out emcmd request failed with status 500 Technical details { "request": { "operation": "CreateInternalBootPool", "variables": { "poolName": "boot", "devices": [ "Samsung_SSD_970_EVO_Plus_500GB_S4EVNJ0N234529T" ], "bootSizeMiB": 0, "updateBios": true, "reboot": false } }, "response": { "ok": false, "code": 1, "output": "assignableDisks snapshot: [{\"id\":\"Samsung_SSD_970_EVO_Plus_500GB_S4EVNJ0N234529T\",\"serialNum\":\"Samsung_SSD_970_EVO_Plus_500GB_S4EVNJ0N234529T\",\"device\":\"/dev/nvme0n1\"}]\nassignableDisks resolved serialNum->device: [[\"Samsung_SSD_970_EVO_Plus_500GB_S4EVNJ0N234529T\",{\"bootId\":\"Samsung_SSD_970_EVO_Plus_500GB_S4EVNJ0N234529T\",\"devicePath\":\"/dev/nvme0n1\"}]]\nRunning: emcmd debug=cmdCreatePool,cmdAssignDisk,cmdMakeBootable\nRunning: emcmd cmdCreatePool=apply&poolName=boot&poolSlots=1\nmkbootpool: command ...[truncated]" }, "status": 1, "error": { "name": "Error", "code": 1, "message": "Internal boot setup returned ok=false", "category": "unknown", "networkError": { "status": 1, "result": { "ok": false, "code": 1, "output": "assignableDisks snapshot: [{\"id\":\"Samsung_SSD_970_EVO_Plus_500GB_S4EVNJ0N234529T\",\"serialNum\":\"Samsung_SSD_970_EVO_Plus_500GB_S4EVNJ0N234529T\",\"device\":\"/dev/nvme0n1\"}]\nassignableDisks resolved serialNum->device: [[\"Samsung_SSD_970_EVO_Plus_500GB_S4EVNJ0N234529T\",{\"bootId\":\"Samsung_SSD_970_EVO_Plus_500GB_S4EVNJ0N234529T\",\"devicePath\":\"/dev/nvme0n1\"}]]\nRunning: emcmd debug=cmdCreatePool,cmdAssignDisk,cmdMakeBootable\nRunning: emcmd cmdCreatePool=apply&poolName=boot&poolSlots=1\nmkbootpool: command ...[truncated]" } } } } ➜ Updating Server Identity to NAS... ✓ Server Identity updated. ➜ Finalizing setup...I didn't reboot yet, I think the system will not be able to start if I do it. Help is appreciated.

@etsi @anhvo
Works for me on unRAID 7.
 
I downloaded the ITE IT87 Driver, then installed the Dynamix Auto Fan Control.
 
Dynamix Auto Fan Control is a little confusing, but I managed to get it to work somehow.
Set "PWM controller" to "it8613 - pwm3". Set "Fan control function" to "Enabled". Now click on the "DETECT" button next to "PWM fan". It might take a while and you might need to click on it twice. It sets the following value: "/sys/devices/platform/it87.2624/hwmon/hwmon2/fan3_input". "Minimum PWM value" is a little confusing. I set it to "100", which results in 1245 rpm. The value "120" gives me about 1457 rpm. You might wanna play around with the values here. Set low and high temperatures to your liking. I chose 35°C for low and 40°C for high. I think you should set the "Refresh interval (minutes)" value to "1", but that's just what I like. Save.  
Don't be confused if it says "Disabled" for "Fan control function" after saving. It does that, because it shows you the settings for the "it8613 - pwm2" fan controller now. You want that one to be disabled. In fact, you only want "it8613 - pwm3" to be enabled. Choose the "it8613 - pwm3" from the list and you will see that "Fan control function" will say "Enabled".
 
The setting "Fan control function" doesn't enable or disable the fan control function in general - it just sets it for the PWM controller you selected from the list in "PWM controller". I don't know why the devs did this, because it's just confusing.
 
Thanks for this thread. Two of my drives were constantly at 45°C. Now they are at 37°C.

Looks like this is the issue here.
 
I just created a new share (which automatically creates a new dataset), called "Test". In that dataset, I created two new datasets "Test1" and "Test2". I copied a file (around 4.5GB) to Test/Test1. From there I moved it to Test/Test2. It took about 20 seconds to move the file. Just to make sure, I moved the file back to Test/Test1 and then to Test/. It always took the same amount of time. Then I created a folder (not a dataset) Test/Testfolder and moved the file from Test/ to Test/Testfolder and it was instantly there.
 
Conclusion: Moving files from dataset to dataset makes unRAID have to copy the file over to the destination and then delete the source. It's not just a change of the pointer to the file in the file system.
@JorgeB can you confirm that?

Anyway, I ran some commands on the CLI which was another step in the right direction:
 
chown -R nobody /mnt/user/Downloads chgrp users /mnt/user/Downloads chmod g+s /mnt/user/Downloads setfacl -d -m u::rwx /mnt/user/Downloads setfacl -d -m g::rwx /mnt/user/Downloads setfacl -d -m o::rwx /mnt/user/Downloads  
At least the files in the subfolders get rw-rw-rw- permissions now, and I can do with them whatever I want. The only thing that still causes problems is the thing when I extract files from an archive.
 
Thanks for the help and taking the time @bmartino1. You helped me quite a bit here.