Everything posted by JDGJr
-
Unraid Server Unresponsive - Can't Survive 2 days!
Did you make it to 2 weeks? I'm happy to report that making those changes to my 7.1.4 system has given me 16+ days of uptime! Haven't had this in months.
-
Unraid Server Unresponsive - Can't Survive 2 days!
Thanks for posting this. I'm still trying to prove my 7.1.4 system isn't crash prone. (I am wary of moving to the next beta) Interestingly, I made the /mnt/user -> /mnt/cache changes late this week - mostly to become consistent. I hope that gives me the positive result you're looking for. Question: do you see a line similar to 'CIFS: VFS: \\Server has not responded in 180 seconds. Reconnecting...' at the end of the syslog when your machine crashes? (need to have a console window displaying syslog when it dies, as it would not be able to write to the disk log file)
-
Unraid Server Unresponsive - Can't Survive 2 days!
I do not have Connect installed. Auto backups run once a week, but the system had been stopping every other day. I'm still prepping for rolling back to 6.12 and system has been more stable since I posted here. But I've been doing a lot of backups to other systems overnight when the stoppage had been common. My system's UI looked ok - i could change pages, but I got the 'system error' message when interacting with Dockers and the spin up/down actions on the main drive list did nothing with the drives.
-
Unraid Server Unresponsive - Can't Survive 2 days!
I've had the same problem with 7.1.4 - started with 7.0.1 but was less frequent back then. The only useful output I've seen appears in the log window if you have it open (it is not written to the log file): Server kernel: CIFS: VFS: \\Server has not responded in 180 seconds. Reconnecting... Most times it dies around 1:15am, hours after the last drive has spun down (noted in the log) I need to rollback to 6.12 - same hardware was stable back then.
-
[Support] Docker-Mailserver
I got this working! The discussion here was a big help. Question: Where have others located their mailbox files? I don't want to spin a HDD every time an email arrives or is read, but I can see the benefit of having the data protected by the array. Should I be concerned about the continuous activity on my main cache SSD? Maybe add a non-array SSD dedicated to email server files? Any suggestions on best practices? Thanks
-
[support] dlandon - Logitech Media Server
My issue was resolved by upgrading from 6.8.3 to 6.11.5 and uninstalling and reinstalling docker image
-
[support] dlandon - Logitech Media Server
I'm seeing same issue, even after forcing an update 10 minutes ago. Is there a way to rollback to a previous version (I don't need new functionality)
-
Roon docker, unRaid Roon support, "steefdebruijn/docker-roonserver"
Yes, update went smoothly and your example for the port assignment helped. Took almost no time. Thanks for an excellent container!
-
Roon docker, unRaid Roon support, "steefdebruijn/docker-roonserver"
Can anyone comment on their success upgrading to Roon 2.0?
-
Roon docker, unRaid Roon support, "steefdebruijn/docker-roonserver"
Yes! I've upgraded several times and no problem
-
Roon docker, unRaid Roon support, "steefdebruijn/docker-roonserver"
Same here! So glad this is working.
-
Preclear plugin
Should I add this disk to my array? Just ran preclear on a 10TB WD Elements external drive and it reported: # ATTRIBUTE INITIAL CYCLE 1 STATUS # # 5-Reallocated_Sector_Ct 0 1 Up 1 # Should I return this drive, run another cycle to see if it increases, or add the drive to my array? Thanks, John
-
Roon docker, unRaid Roon support, "steefdebruijn/docker-roonserver"
I've switched to an older NUC (Intel NUC6CAYH) with 8 GB, similar to wcg66. I bought used it for less than $150 to be able to stream multichannel audio thru Roon, and it is working perfectly - now for multichannel and also as the server. I was able to easily upgrade Roon server software from 610 to 667.
-
Roon docker, unRaid Roon support, "steefdebruijn/docker-roonserver"
Anyone have success upgrading to build 667? I was prompted to upgrade and it failed to restart. Eeven uninstalling the container and reinstalling and applying a backup didn't give me a running server. I'm running off a NUC temporarily, will try to get functional tomorrow. Is there a process to roll back to a working version (611? was working for me for almost a month)
-
Intel Socket 1151 Motherboards with IPMI AND Support for iGPU
I've been running L2.32 since setting up my new hardware around the 25th. Seamless operation here
-
[Plugin] CA Fix Common Problems
Great plugin, a huge help. Feature request: Is it possible to check if a functioning DNS server is running at the addresses specified in Network Settings? I got bit by having invalid addresses and it showed up as a failing Plugins page. This seems to be a somewhat frequent issue, probably caused by people (me included) installing PiHole to block ads and having hardcoded DNS addresses which fail if the address of the external PiHole node is changed. See this thread for an example: Thanks!
-
Intel Socket 1151 Motherboards with IPMI AND Support for iGPU
It looks like 2.21a has been removed from the site - the Beta Zone is now empty
-
Preclear.sh results - Questions about your results? Post them here.
Earlier this month I bought a WL 6TB drive that cleared fine, so I bought a second, but it looks like this one is failing. I'm using the same power/sata ports/cables as i used for the first drive. Any reason to try something different, or should I send this one back? I ran the clear script twice - first post-read failed at about 86%, but 2nd seems to have failed immediately. ############################################################################################################################ # # # unRAID Server Preclear of disk WOL240387533 # # Cycle 1 of 1, partition start on sector 64. # # # # # # Step 1 of 5 - Pre-read verification: [12:11:59 @ 136 MB/s] SUCCESS # # Step 2 of 5 - Zeroing the disk: [12:02:34 @ 138 MB/s] SUCCESS # # Step 3 of 5 - Writing unRAID's Preclear signature: SUCCESS # # Step 4 of 5 - Verifying unRAID's Preclear signature: SUCCESS # # Step 5 of 5 - Post-Read verification: FAIL # # # # # # # # # # # # # # # ############################################################################################################################ # Cycle elapsed time: 34:00:15 | Total elapsed time: 34:00:15 # ############################################################################################################################ ############################################################################################################################ # # # S.M.A.R.T. Status default # # # # # # ATTRIBUTE INITIAL STATUS # # 5-Reallocated_Sector_Ct 0 - # # 9-Power_On_Hours 0 - # # 194-Temperature_Celsius 23 - # # 196-Reallocated_Event_Count 0 - # # 197-Current_Pending_Sector 0 - # # 198-Offline_Uncorrectable 0 - # # 199-UDMA_CRC_Error_Count 0 - # # # # # # # # # # # ############################################################################################################################ # SMART overall-health self-assessment test result: PASSED # ############################################################################################################################ Stopped @ 86% --> FAIL: Post-Read verification failed. Your drive is not zeroed. ############################################################################################################################ # # # unRAID Server Preclear of disk WOL240387533 # # Cycle 1 of 1, partition start on sector 64. # # # # # # Step 1 of 4 - Zeroing the disk: [13:17:15 @ 125 MB/s] SUCCESS # # Step 2 of 4 - Writing unRAID's Preclear signature: SUCCESS # # Step 3 of 4 - Verifying unRAID's Preclear signature: SUCCESS # # Step 4 of 4 - Post-Read verification: FAIL # # # # # # # # # # # # # # # # # ############################################################################################################################ # Cycle elapsed time: 13:32:20 | Total elapsed time: 13:32:21 # ############################################################################################################################ ############################################################################################################################ # # # S.M.A.R.T. Status default # # # # # # ATTRIBUTE INITIAL STATUS # # 5-Reallocated_Sector_Ct 0 - # # 9-Power_On_Hours 46 - # # 194-Temperature_Celsius 30 - # # 196-Reallocated_Event_Count 0 - # # 197-Current_Pending_Sector 1 - # # 198-Offline_Uncorrectable 0 - # # 199-UDMA_CRC_Error_Count 0 - # # # # # # # # # # # ############################################################################################################################ # SMART overall-health self-assessment test result: PASSED # ############################################################################################################################ --> FAIL: Post-Read verification failed. Your drive is not zeroed. ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 6 3 Spin_Up_Time 0x0027 100 253 021 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 2 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 190 156 000 Old_age Always - 303 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 70 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 2 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 1 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 30 194 Temperature_Celsius 0x0022 122 117 000 Old_age Always - 30 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 2 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0
-
[support] gfjardim's Docker Repository
My LogitechMediaServer stopped accessing mysqueezebox.com. Was working earlier this week, now it doesn't. When I ping from a shell, I get an amazonaws.com result. Is there a way to config the IPAddress that works on my windows machine? this from the docker log file: 15-05-17 12:31:31.0962] Slim::Formats::XML::gotErrorViaHTTP (311) Error: getting http://www.mysqueezebox.com/public/opml/ec03feb2ed34195c539e1a809d1eb920d47625ea/favorites.opml Couldn't resolve IP address for: www.mysqueezebox.com [15-05-17 13:10:52.8731] Slim::Networking::IO::Select::__ANON__ (131) Error: Select task failed calling Slim::Web::HTTP::processHTTP: /etc/resolv.conf: Permission denied at /usr/share/perl5/Slim/Networking/Async/DNS.pm line 87. ; fh=Slim::Web::HTTP::ClientConn=GLOB(0x7930e20) [15-05-17 13:12:19.0048] Slim::Formats::XML::gotErrorViaHTTP (311) Error: getting http://www.mysqueezebox.com/public/opml/ec03feb2ed34195c539e1a809d1eb920d47625ea/favorites.opml Couldn't resolve IP address for: www.mysqueezebox.com [15-05-17 13:16:06.0026] Slim::Utils::Timers::__ANON__ (273) Error: Timer Slim::Networking::SqueezeNetwork::__ANON__ failed: /etc/resolv.conf: Permission denied at /usr/share/perl5/Slim/Networking/Async/DNS.pm line 87. [15-05-17 13:36:19.1865] Slim::Formats::XML::gotErrorViaHTTP (311) Error: getting http://www.mysqueezebox.com/public/opml/ec03feb2ed34195c539e1a809d1eb920d47625ea/favorites.opml Couldn't resolve IP address for: www.mysqueezebox.com
-
cache_dirs - an attempt to keep directory entries in RAM to prevent disk spin-up
Is it possible to use the 'exclude_dir' setting to exclude an entire drive? I have a non-array drive on the system that'd i'd rather not cache. Thanks, Joe, for another useful tool!
-
rsync
Thanks to this thread, i am able to backup my main unRAID to a separate machine. I have one issue, tho. rsync creates directories ahead of the file copying process, and my disks are rather small 250G/300G, so i end up with tons of empty folders on each drive that were created before the files filled up the drive and the user share automatically moved to the next disk. Is there a way to stop rsync from creating a folder before it is needed for a file, or an easy way to clean the empty folders after the first bulk run? tia found this on the web: find -depth -type d -empty -exec rmdir {} \; (Joe's solution -next msg - is a bit clearer)