hendrst1

I just shutdown the Unraid server to take a peak at the BIOS power management settings. The UPS reading now indicate that my 15 year old pc is only using 36-72 watts so not so bad. I must have known what I was doing when I originally assembled it back in 2008. Ha.

How did I miss that document? Thank you. PS: I liked what I actually saw and bought a license.

Initial set-up was easy (but make sure your hardware is working). Performance (read/write speed) generally as expected but will vary depending on your hardware. (Do turn on the faster write setting in disk settings for large initial writes). Plug-ins work well but some can cause instability so check them out on the forums before installing. Same for Dockers, I presume, but I haven't tried any yet. Otherwise OS appears pretty stable. If you are a Mac OS user, Time Machine apparently works for some but not others (me). Power consumption remains a significant issue. If repurposing an old PC (Intel core2duo 2.66Ghz, 4GB ram, 4hdd+2SSD) like I am, my power usage ranges from 90 watts at idle (drives spun down) to 126 in normal active usage. That is about triple the usage of some of the 2-/4bay home commercial NAS' from Synology/QNAP or a Mac mini. I presume there are some PCs out there that use much less power; if I could find one I would prefer that with Unraid over those proprietary commercial boxes. So, still testing and learning and looking for energy efficient hardware.

I recreated the Time Machine share with YES selected as case sensitive. Still same result: Initial backup worked fine but then no subsequent reconnection for incrementals. Yet, I can connect a drive to my old Airport Extreme router and TM backups work fine. Oh well, at least this time I could use the Unraid File Manager to remove the files for easy share deletion.

So you selected YES for case sensitive; I left it on AUTO.

Please share your options because that was certainly not my experience backing up two M2 machines to an Unraid share. In my case the initial time machine backup worked but then it wouldn't do any incremental hourly updates after that. Moreover, clicking on the time machine share in Mac OS Finder immediately locked up Finder requiring a reboot. I couldn't even delete the contents of the time machine share from Mac OS; had to go to a Windows machine to do that. So not a happy experience. I am not sure Time Machine is worth the trouble. It has never been reliable over the years I have used it unless direct attached to your machine; and even then it eventually gets corrupted. I hear it is more reliable since Apple implemented apfs file system but I have my doubts.

Solved. I have access through webgui now. Instead of accessing tower.local I used ip address instead and also used http instead of https. Apparently Firefox didn't remember the self-cert but had no problem with less secure http.

I have rebooted into server gui directly from server no problem. But login from local machine on lan not successful. There is no error message given at login screen; it just keeps looping back to blank name and password field. Must be a simple solution? I must say a lot of trouble for what looks like an incompatible Nvidia plugin; but except for having to revalidate the parity drive and no local gui access it is still running.

I can now get to the tower.local login screen from MyServer but still can't login. I have edited the flash boot drive to remove the password files and rebooted. Get to the tower.local login screen via My Server and reset the root password but still doesn't let me login. So what's next?

I removed the Nvidia plugin from the flash boot drive and was able to reboot into webgui and all is intact with no recheck of the parity drive required. Only problem now is I am unable to access the gui from my local browser (local access). The My Servers app shows server online now but the local access button shows a red lock symbol. I get the login screen but it doesn't take my login credentials. Only way I can access the gui is through the monitor directly attached to the server. Must be an easy fix for this involving password reset, right? Oh, and I have recovered the syslog file (attached). syslog-192.168.254.124.log

In addition to the NVIDIA plugin, I also installed the Unraid file manager plugin and that network fine tuning plugin. Both of those installed correctly. Things got unstable only when I attempted to install the Nvidia plugin.

Attempted to install Nvidia plugin but got a pop-up warning about background process running; after a long while I clicked on option to stop the background process with another warning that would cause instability. I proceeded anyway and system became unstable (as in app store not showing apps, CA plugin not loading) and so I successfully stopped the array and shutdown. Now, when I restart tower.local not recognized in web browser. If I look at screen I get to login prompt, put in name and password but get the following: Linux 5.19.17-Unraid. root@Tower: ``# _ Then nothing. I booted into safe mode with no plugins with GUI option and got a gui and logged in (didn't show my account name) and managed to click on reboot but it didn't reboot. So I just powered down and restarted and got to prompt as above. Can't get to syslog file which is stored on system share and appears to be intact from when I got to the gui from process above. I have attached a previous diagnostic file that shows my hardware configuration. What else can I do? tower-diagnostics-20230214-1357.zip

I experimented with a few more downloads. It looks like a batch of old Apple Aperture library files that are causing the download to slow to a crawl (2 hrs est. to download a 2GB library file). Other directories with just photos download at the expected speeds (60-80MBs). These Aperture library files have a large number of small files composed of not just .jpg previews and master files but all sorts of database, xml files and other peculiar system files. But, even so, why do these present such a problem for downloading? I don't recall there was a problem on the initial upload but maybe I didn't notice it.

In have loaded my server with data and got good write speeds once I discovered turbo write. But now when backing up a share from the server to a disk attached to my local machine, it is too slow. I take it there is no turbo read but is there some other tuning that can speed things up? The share in question is a 500GB photo archive which contains lots of small thumbnail images as well as large ones. The backup is initiated on my mac mini with Carbon Copy Cloner and is the only process going on. Backup speed was averaging 15-30MBs and for fisrt 5 minutes was in the kb range so I just stopped the backup; I would expect 80-90MBs over ethernet. Backup speed on local disk to local disk is a steady 130MBs. Hardware config: Intel Core 2 Duo 2.66Ghz, 4GB ram; 1Gib nic Unraid: array: 1 x 5TB parity HDD 2x 4TB 1 x 3TB HDD cache pool: 2 x 512GB SSD Diagnostic file attached. tower-diagnostics-20230215-1445.zip

Ok. I just set up the syslog server for local capture on system share (cache). Would like to redirect to a Windows or a MAC OS machine so trying to figure out how to do that.