Fireball3

I did some massive file movement - in fact it was consolidation of shares to dedicated drives, as the spread led to significant spin-up times. I'd like to feed back some of my experience and suggest some points that can possibly be improved. 1. Most of my issues rooted in missing permissions. Unfortunately rsync's failure messages are very cryptic thus useless most of the time. It will never tell you that you have permission issues! The plugin does, but not "strong enough". Therefore it is a matter of usability to add this utility to the plugin. Maybe provide a "change permissions" button if the dry run finds a related issue. It's annoying if you do the "dry run" and are told to "install docker xy first". Much more simple and without the need of a docker is the "newperms" script that comes with unRAID. Long story short, it is recommended to run the "newperms" on the source AND on the target! The plugin should have this option included. 2. Due to 1) I had many aborted runs which left me with lots of duplicates. Obviously the command aborted at some point during the copy so it didn't even come to the "remove sources". After figuring out that the permissions were the issue, I ran the job again and that removed the sources but I had to remember the exact task! My task was consolidating so it was easy to find the dupes as they were the sources, but I imagine this can turn into a problem. e.g. I have some shares spanning multiple drives and I found a couple of identical files on different drives of the share. Must have been moving the source to different drives in different sessions. Need to hunt the dupes now. I have no solution how to handle this, but if an rsync-command is failing at some point, dupes will be created. Maybe there is an rsync option to "remove sources" right after the "copy" of each file? Also a more comprehensive log of commands issues could be useful. Maybe somewhat like: date - rsync xyz source target etc. success - 0 errors - run again knob At the moment the log is too much. Maybe let's have some log levels (normal/debug/full)? That leads straight to 3. Logs are fine but it turned out that the unRAID OS update aborted due to space shortage. You know what I'm gonna say...there must be some sort of log handling. Rotation, size limit, whatever. I had hundreds of MB unbalance log data... Anyway, many thanks for the hard work! ...sry, it got quite long

Of course, there are numerous WOL apps for all kind of OS's to do the job manually. Some routers offer options to wake a target if they see inbound traffic/requests for its address. Open source routers can be customized to do so. example https://wiki.openwrt.org/doc/howto/auto_wake_on_lan

I wonder how one can be "impressed by the performance" of a PSU...

Until unRAID v6.? it was not performing a graceful shutdown by default. Posts from former times are still spread all over the forum so that's where you probably read about it.

Those buttons are just for a "quick" action. You can achieve the same actions with the switches on the main page.

Sometimes I also see this "out of sync" GUI. I don't use sleep, but occasionally a drive is shown "spun down" while it's definitely spinning.

Coming back to close my issue. While rsync is a great tool, the usability in terms of error handling is a real pain. It throws "error 23" at you and that's it. Good luck in finding the problem... Finally I found out that the permissions change has to be issued on the source as well as on the target. I was hesitant because I have no dockers set up but the onboard command "newperms" seems to do the job quite well.

Once the error is logged on a move action, the plugin refuses to restart the process. Is there a way to remove the log entry? For some reason, the error 23 appears although the other user is selected. Is the command "newperms" sufficient, or do I need the whole docker thing to change the permissions? Edit: even if the newpers is issued, the error 23 appears...

No, I have another user set up. It will write, but can't delete the sources. Is there any benefit in doing what is suggested (install the permissions docker)?

My server has been moving 10 hours from one disk to another, then I decided to shutdown my browser. I reconnected from another machine and the plugin didn't display the operation that was ongoing. I also couldn't see any writes and reads on the drives I'm copying. When trying to restart the procedure it says: Move operation was interrupted. Check log (/boot/logs/unbalance.log) for details. What should I do next? About 70% have been moved by now, but the moved files have not been deleted from the source. Is that normal? Edit: I guess now I know why: There are some permission issues with the folders/files you want to move 432 file(s)/folder(s) with an owner other than 'nobody' Due to this fact, unBALANCE can't delete the source files and throws the error 23. When invoked as another user, it runs flawlessly. Now what's this permission thingy? Why do I need to change them to nobody? Do I need to do that? Most files are created through a windows account, thus being not from user nobody.

A dump of a flashed controller should look like this: C:\SAS2FLSH.EXE -l Adapters.txt -c 0 -list Adapter Selected is a LSI SAS: SAS2008(B2) Controller Number : 0 Controller : SAS2008(B2) PCI Address : 00:01:00:00 SAS Address : 5b083fe-0-daa2-1d00 NVDATA Version (Default) : 14.01.00.08 NVDATA Version (Persistent) : 14.01.00.08 Firmware Product ID : 0x2213 (IT) Firmware Version : 20.00.07.00 NVDATA Vendor : LSI NVDATA Product ID : SAS9211-8i BIOS Version : N/A UEFI BSD Version : N/A FCODE Version : N/A Board Name : SAS9211-8i Board Assembly : N/A Board Tracer Number : N/A Finished Processing Commands Successfully. Exiting SAS2Flash. You can read Vendor LSI, Firmware Version 20.00.07.00, no BIOS Did you post the Adapters.txt from the logs directory or did you do a new dump after the flash. The logs directory contains only the original dump unless you run step 1 again, after the flash is complete. I'm not sure what you posted now, because of your question here.

From the beginning, step 1

It looks like this card is not flashed to IT mode. Repeat the process with this card. If possible, take a screenshot/pic from the error in step 5.

Can you post the Adapters.txt of the respective controller? Usually the lifesign is a green flashing LED. Was it green before? Maybe we can find some intel on that LED codes?

Yes, step 1 will create the adapters.txt again.

Yes, you can boot into EFI shell and perform the remaining tasks. There is a short notice what to do in this case right below the link to the toolset that you used. It should be sufficient to enter the BIOS with the USB drive plugged and select to boot from. This "boot override" is usually on the same page where you can save/exit the BIOS. Please download the latest toolset version (v4) - see my sig. Then execute the .nsh files and follow the instructions. In case of an H310 all should work up to the 5er steps, then you have to switch to EFI an go ahead with 5_DELL_IT\5itdell.nsh By the way, some posts earlier, there was also a "PAL error" report where I already outlined how to proceed. Note: Select the right drive by typing "FSx" with x being the drive letter of your USB drive. e.g. FS0, FS1 Type "ls" to list the content of your drive.

@master.h OK, now you have the same output as @EdgarWallace. See 2 posts above. Have you been trying other things on this controller before you started 1.bat? On an untouched, stock card this is not normal! Obviously your card is also wiped already! Is the megacli command also failing? This is only shown on screen. Continue with step 5_DELL_IT You won't have a SAS address as the card is already clean, just copy the one inside the 6efi.bat and use that. Same for you @EdgarWallace @mejutty Assuming you want the latest LSI P20 firmware then: Please run 1.bat - there is your SAS address then run 5_LSI_P20\5ITP20.bat and finally run 6.bat to reprogram the SAS address

I'm sure it was not the 1.bat because that does nothing but reading the controller info. Especially the SAS address... You ran 3.bat and that wiped the card...didn't you? File is up in the original thread. Since your card is clean, start with the 5_DELL_IT/5itdellefi.bat As already said, I couldn't test. If you see some errors, take a pic for me. pm them to me so we don't fill this thread needlessly.

Ah, the PAL error... There is a short notice what to do in this case right below the link to the toolset that you used. Anyway, now you can either try another mainboard (just for the flashing process) or use the EFI shell. Unfortunately I have no spare EFI capable mainboard where I could try the toolset. If you are willing to test it, I have prepared a new version that I'm gonna upload this evening. Until it's available for download you can try to get the EFI boot working. The v2 toolset has an x64 bootloader included already. It should be sufficient to enter the BIOS with the USB drive plugged and select to boot from. This "boot override" is usually on the same page where you can save/exit the BIOS. Once it boots, give sas2flash.efi a try - just execute it without options. Hopefully it works in the x64 environment or I will have to look for a 32bit version. If you have it working so far, please wait for the next toolset version (v3) Then execute the ?efi.bat files and follow the instructions. Note: Select the right drive by typing "FSx" with x being the drive letter of your USB drive. e.g. FS0, FS1 Type "ls" to list the content of your drive.

OK, then I didn't find what you meant with: Because yaldex's issue was related to another card. Can you explain your problem?

I'm also confused right now... What type of card do you want to flash?

Are you referring to flashing a 1068 based card? That is not possible with the H310 toolset you linked! Please follow yaldex's posts eventually there is a solution by using mptutil iirc.

You are right, which version of sas2flsh.efi did you use? I will add that to the next package update.

I have just updated the toolset for the dell cards. It's safe to use the P20.00.07.00 that is in the package. P20.00.00.00 had issues, that's right. @cdoublejj Did you flash a BIOS? Please remove the quote, as it contains old information (links)! People finding this via the forum search might get confused. Leaving a link to the post instead is better! Thanks!