dtempleton

OK, maybe answering my own question, I realize I can rsync /mnt/disk2/ to /mnt/disk5/ rsync -aP --remove-source-files /mnt/disk2/ /mnt/disk5/

I have a failing zfs formatted array drive (disk2, 2TB) based on rapidly growing unallocated sectors. Under the presumption that the parity record for this drive is better than the drive itself, I unallocated Drive 2 hoping to use mover to empty disk2 onto the array, in which there is plenty of room. Then I saw in the 7.2 I saw that the empty drive utility is now moved to Global Disk Settings, and an empty disk settings. But I can't select Disk2 for this since it's not in the array anymore. When the contents of a drive are emulated (which will happen when I activate the array) is there a way to get an emulated drive copied elsewhere on the array? Once this happens I'm prepared to make a new config without this drive. Thanks Dennis (warnings: Warning [TOWER] - reallocated sector ct is 5912Warning [TOWER] - reported uncorrect is 115Warning [TOWER] - current pending sector is 56Warning [TOWER] - offline uncorrectable is 56All within a few minutes

I'll try rebooting safe mode but right now the server is running and in use; just can't access the GUI. But an update; This URL seems to access it OK this morning (I thought I tried this yesterday): http://192.168.1.220:8080/Main While the one setup with myUNRAID.net doesn't: https://192-168-1-220.eb4a424017fa08cd2cc8d2bbd9cd528f6c202fc6.myunraid.net:8443/Main (I altered this specific key to post) or it didn't until just a minute ago and now the HTML loads but no info from the server loads. 10 minutes now and no array or pool data. at the same time http://lime-technology.com or http://lime-technology.com.index flash a loading page then send a blank page without error. I think something is going on with our friends' server. Anyway; I'll wait to see if it fixes itself, but it makes me a bit leery of being dependent on the myunraid.net service yet.

My GUI won't load the main page, but instead gives a 503 nginx errror, I rebooted to the same problem. Im pasting the diagnostics zip file below, but the syslog lists hundreds of these: Jan 22 14:49:26 Tower nginx: 2023/01/22 14:49:26 [error] 6094#6094: *6 limiting requests, excess: 20.456 by zone "authlimit", client: 192.168.1.101, server: hash.myunraid.net, request: "GET /login HTTP/2.0", host: "hash.myunraid.net:8443", referrer: "https://hash.myunraid.net:8443/Settings/Userscripts" Jan 22 14:49:27 Tower nginx: 2023/01/22 14:49:27 [error] 6094#6094: *25 limiting requests, excess: 20.602 by zone "authlimit", client: 192.168.1.101, server: hash.myunraid.net, request: "GET /login HTTP/2.0", host: "hash.myunraid.net:8443", referrer: "https://hash.myunraid.net:8443/Main" Jan 22 14:49:28 Tower nginx: 2023/01/22 14:49:28 [error] 6094#6094: *6 limiting requests, excess: 20.473 by zone "authlimit", client: 192.168.1.101, server: hash.myunraid.net, request: "GET /login HTTP/2.0", host: "hash.myunraid.net:8443", referrer: "https://hash.myunraid.net:8443/Main" Jan 22 14:49:30 Tower nginx: 2023/01/22 14:49:30 [error] 6094#6094: *6 limiting requests, excess: 20.463 by zone "authlimit", client: 192.168.1.101, server: hash.myunraid.net, request: "GET /login HTTP/2.0", host: "hash.myunraid.net:8443", referrer: "https://hash.myunraid.net:8443/Settings/Userscripts" Jan 22 14:49:30 Tower nginx: 2023/01/22 14:49:30 [error] 6094#6094: *6 limiting requests, excess: 20.110 by zone "authlimit", client: 192.168.1.101, server: hash.myunraid.net, request: "GET /login HTTP/2.0", host: "hash.myunraid.net:8443", referrer: "https://hash.myunraid.net:8443/Main" Jan 22 14:49:30 Tower nginx: 2023/01/22 14:49:30 [error] 6094#6094: *25 limiting requests, excess: 20.102 by zone "authlimit", client: 192.168.1.101, server: hash.myunraid.net, request: "GET /login HTTP/2.0", host: "hash.myunraid.net:8443", referrer: "https://hash.myunraid.net:8443/Main" I also found that this link : http://lime-technology.com/wiki/index.php?title=Troubleshooting#Capturing_your_syslog gives a Cloudfare error from Limetech. Could this be a server problem from myunraid.net? Thanks! Dennis tower-diagnostics-20230122-1504.zip I see the reference to myunraid.net which I installed a few days ago but it seemed to work OK

OK, I figured this one out myself. The symptoms of crashing were not related to the parity rebuild, but coincidental. The syslog held the key- this several-times repeating error: ntpd[1135]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized I found a post on Reddit that suggested turning off ntpd auto update, but that did nothing. However one post there said "check your motherboard battery", so I did that. Replacing the battery on the motherboard prevented any subsequent UNRAID OS crashes. Hope this helps someone down the line. Dennis

Hi; I'm running 6.11 I've had three unraid OS crashes while trying to do a data rebuild from a failed drive. After about 3 hours of an 8 hour expected rebuild the system just goes offline. The server seems to work ok for these hours until the crash. I can't access it via ssh or the GUI, and can't get a diagnostic report. I have to restart with the reboot button. The last time it was in safe mode. Edit: I learned how to turn on "Mirror syslog to flash" and I'll report back... I finally for a syslog from the crash, it's below. I don't see many errors except a failed time synch. The crash seems to come at about the same percent data rebuild, so it could be related to a disk access error but I don't see evidence of that. I'll try booting the server but not mounting the array Thanks for any advice in advance syslog20221215.zip

My server is working now, thanks for your input JorgeB and others. I bought this 5 port card: https://www.amazon.com/dp/B08BHZQVP7?psc=1&ref=ppx_yo2ov_dt_b_product_details and all seems to be ok except several of my drives report UMDA CRC errors (that seem to be permanent but unimportant). Regarding the previously purchased card from Ziyituod, it's a mess. It was listed at Amazon as originally listed as an ASMedia controller, then with the same part number a second version was listed on Amazon that was clearly a Marvell controller. When I pulled the controller the board actually showed neither of the Ziyituod model numbers and no identifiers at all. In future if I get a card that doesn't look like that advertised I'll send it right back. Thanks for helping put this back together. Dennis

sorry I posted the one after reboot. The earlier one had blown up with read error warnings, 128mb! I zipped it and add it herebelow I'll report after Wednesday when the new JMicro controller comes in. syslog.1.txt.zip

It looks like that Marvell 9215 controller is not on the approved list now, but the forum is full of questions. I just ordered a different one: https://www.amazon.com/gp/product/B08BHZQVP7/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1 PCIe SATA Card, Electop SATA III 6 Gbps Expansion Controller, JMB585/SATA 3.0 Non-Raid ,Support 5 Ports with 5 SATA Cables, Standard & Low Profile Bracket for Desktop PC that has the JMicro controller that is recommended here: https://forums.unraid.net/topic/102010-recommended-controllers-for-unraid/ won't know for a few days if it fixes things ChatNoir: Thanks, our messages passed each other simultaneously.

Thanks; reboot looks the same Here is the new syslog syslog.zip and diagnostics file tower-diagnostics-20221127-1441.zip I realize that all of the drive errors I'm seeing are controlled by one controller; this one: https://www.amazon.com/gp/product/B07SZDK6CZ/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1 Ziyituod PCIe SATA Card, 4 Port with 4 SATA Cable, SATA Controller Expansion Card with Low Profile Bracket, Marvell 9215 Non-Raid, Boot as System Disk its a Marvell 9215 device, about 7 months old; I thought that was a usable one. I'll go look at the list of usable controllers

My server has been working great for the past 7-8 months, no problems at all, mainly as a media server and TimeMachine. One morning the server was not accessible and I had to do a hard reboot with the power button. The array reported a bad Parity2 drive, which I removed from the array and then did a parity rebuild that completed. I reformatted the failed Parity drive (XFS) and the Attributes seemed OK. It's my newest drive, an 8 GB WD drive about a year old, maybe a bit more. I rebooted at least once and now have a failed array drive which shows that the contents are emulated (the data seems to be there). Thinking the reformatted 8G drive was good, I substituted it for the failed disk 3 and rebooted, which initiated a rebuild that never finished. Now the syslog is full of disk0 read errors, the tail is below I have some new drives coming, but its unclear that the issue is actually drive fail. I tried the extended SMART test on the former P2 drive, but it stopped before completion. The short SMART test reports "no such device". The drive attributes "could not be read". Today I tried to get a diagnostics file but the script starts and never completes. I attach a diagnostics file from the time of the parity drive fail though and can try to get a current one if anyone has suggestions on how to get it. I'll format the new drives as soon as I can, but it will be days before they're ready. At this point its not clear how the array drive can be emulated, if it cant read from the Parity drive (!?) Thanks for any help Dennis Here's the hardware profile:HW profile.xml.zip tower-smart-20221125-2237.zip tower-diagnostics-20221125-1150.zip

I get a similar warning using nzbget. I have mappings to container directories /data ; /media ; and /config. /media and /config are self explanatory but I'm not sure what goes in /data I put it inside /appdata but maybe it needs to map to my /nzbget download directory??

I'm having problems getting SSH setup under 6.9.2 It was working until I upgraded to 6.9.2 from 6.3.5 when I lost the ability to log in automagically with authorized keys. I figured that I would sort that out later and logged in successfully with the root password. I tried several things to get the authorized keys to work, and eventually renamed the /boot/config/ssh/ directory so that a new one would be created and I could set that one up from scratch. More on that later. In the meantime I lost the ability to log into the server as root, even though the root password allowed login to the webGUI. in the /boot/config/sshd_config file I see the following lines (about 27) AllowUsers root #LoginGraceTime 2m PermitRootLogin prohibit-password PermitRootLogin prohibit-password #StrictModes yes MaxAuthTries 6 #MaxSessions 10 I didn't know what 'prohibit-password' meant but from https://ubuntuforums.org/showthread.php?t=2359172 I learned that this is the new default for ssh_config to force automatic login, i.e. prohibiting the use of root passwords. OK, but for now I need the password option, so I changed the lines using nano to: AllowUsers root #LoginGraceTime 2m #PermitRootLogin prohibit-password PermitRootLogin yes #StrictModes yes then stopped and restarted SSH with the plugin. I still can't use a root password, and find that the sshd_config has been changed back to what it was before: # Authentication: AllowUsers root #LoginGraceTime 2m PermitRootLogin prohibit-password PermitRootLogin prohibit-password #StrictModes yes MaxAuthTries 6 #MaxSessions 10 What is happening? Is something writing a default sshd_config file here on every SSH restart, perhaps the SSH plugin? (Edit: sure enough deleting the plugin allows 'PermitRootLogin yes' to persist and login works) If so this is an important enough setting that it might should be accessible by the plugin GUI as an option Secondly, I note that in UnRAID /root/.ssh redirects to /boot/config/ssh/root but, the ssh keys that are generated are placed in /boot/config/ssh not in the root subdirectory, Is that as planned? I did try copying the keys to .../root and then to my client authorized keys but no joy so far. I'm more flummoxed by not being able to use a root password. Thanks for all you do! Dennis

Thanks!