rsutter

The box is right below the router (Orbi NetGear) and I used a brand new cat5 cable and plugged into one of the ports of the ORBI instead of one of the switches next to the router.

I did try that! The result when I loaded UNRAID from newly made USB detected NO IP. I will change the cat5 cable and plug into another port to cross check. After changing the cable, the system did boot up with a static IP. I need to buy another license for this box!

I did try that! The result when I loaded UNRAID from newly made USB detected NO IP. I will change the cat5 cable and plug into another port to cross check

The attachment is from a monitor that is hooked up to the NAS. I just created a new USB and changed the static IP to .44 The gateway is the IP of my router and the DNS server is 1.1.1.1. I have allow UEFO boot as checked. When the NAS boots from the USB and I prompted for login, I enter root enter and receive the same thing root@SutterStuff:~# SutterStuff is the server name. If I use CMD to ping the IP anding in .44 I get this Pinging 192.168.1.44 with 32 bytes of data: Reply from 192.168.1.9: Destination host unreachable. Request timed out. Reply from 192.168.1.9: Destination host unreachable. Reply from 192.168.1.9: Destination host unreachable. Ping statistics for 192.168.1.44: Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),

In the past, the static IP that I used was in range. The UNRAID is not on - I cannot log into it. on my desktop I pinged 192.168.1.144 Pinging 192.168.1.144 with 32 bytes of data: Reply from 192.168.1.9: Destination host unreachable. Reply from 192.168.1.9: Destination host unreachable. Reply from 192.168.1.9: Destination host unreachable. Reply from 192.168.1.9: Destination host unreachable. which makes sense. thank you for your help!

If I go to a browser and enter the IP, I don't get a connection. I remember in the past at that UNRAID screen I can now create a UN/ PW. I DID ENTER PING (IP) and i get a series 64 bytes from IP icmp_seq = numbers.

I needed to do some updates to the NAS that I use for UNRAID. I bought a new USB thumb drive and have used to USB creator to boot up. I created a static IP and when I start up with the USB I am prompted with login. In the past , the login would simply be username: root with no password which would load UNRAID. I have done this a few times but only get this: login: root Linux 6.1.74-Unraid. root@sutterstuff: # which I believe is wrong. Can someone suggest to me what I might be doing wrong and how to get UNRAID to load on my NAS? Thanks

I replaced a WD RED HD with a Seagate IronWolf in my RAID recently because my dashboard displayed SMART errors. When I added the new drive, I encountered multiple errors with this IronWolf. Seagate told me to get a replacement HD since it is brand new. Is there an issue to mix WD RED and Seagate IronWolf HDs to create a Parity using UNRAID? I also replaced a WD RED 10 TB as Parity disc for a Seagate IronWolf 12 TB for this raid in a QNAP TS-464 enclosure because the 10 TB also displayed SMART errors and is also under warranty! Any thoughts?

Jorge, Thanks for the quick reply but my NAS system is a QNAP TS-464 which doesn't use SATA cables. The attributes table for the PARITY drive shows many of the attribute name types as either Pre-fail or Old Age though the drive is only one year old!

I am migrating from a custom NAS to a QNAP-TS464 and utilized the same HDSs that I had with the other case. The UNRAID version 6.12.8 detects the array to have SMART errors for both the main parity drive - WD Red 10 TB which is only one year old and one of the 4TB Red drives. I have included a diagnostics file to help detect what issues I am facing. I do have a new Seagate Ironwolf 12 TB that I bought as a parity drive as well as another 4 TB Ironwolf for one of the discs that UNRAID detected with SMART errors. I appreciate any comments to help me detemine next steps. unraid-diagnostics-20240310-0707.zip

I got this error in FixProblems: Your server has detected hardware errors. The output of mcelog has been logged. Post your diagnostics and ask for assistance on the Unraid forums. Can someone give me an idea what is being detected and what I can do to get this cleared up? Thanks sutterstuff-diagnostics-20240105-1548.zip

I got this error in FixProblems: Your server has detected hardware errors. The output of mcelog has been logged. Post your diagnostics and ask for assistance on the Unraid forums. Can someone give me an idea what is being detected and what I can do to get this cleared up? Thanks sutterstuff-diagnostics-20240105-1548.zip

I have a UNRAID NAS that I have loaded the PMS docker on it. The reliability of the connection is not very high. I have had to stop the array, reboot the NAS, and then rebuild the libraries onto Plex too many times in the last month. When it runs, it is awesome but as I mentioned it is unreliable. The NAS has the latest version of UNRAID as well and the PMS is up to date. I do own a lifetime copy of PMS ( Version 4.108.0 ). The NAS is a ASRock J3710-ITX MB, 8GB DDR3, no GPU. I have a 10TB WD Red for the parity drive and 3 4TB WD HD for the raid. I do not have a cache drive though I do have a 1TB SSD that could be used as a cache if I assign it to be one. Would I be better off buying either a TerraMaster, QNAP, or Synology NAS and scrapping what I made or can I do something to optimize the NAS that I made? At the moment I am reloading my library with the files that are on the NAS to the PMS docker. This is perfect and after everything loads up, in time, I lose connection to the files for no reason. I am not sure if there is a router/port issue that is causing this to happen. I hope someone can decipher what is the root cause of my issues and appreciate your help sutterstuff-diagnostics-20231019-1230.zip

Three things: 1. Rootfs file is getting full (currently 97 % used). How do I flush this? 2. I cannot update my unraid latest OS. 3. Dashboard shows that two of my hard drives SMART errors. I get this error plugin: updating: unRAIDServer.plg plugin: downloading: unRAIDServer-6.12.4-x86_64.zip ... 34% plugin: unRAIDServer-6.12.4-x86_64.zip download failure: File I/O error Executing hook script: post_plugin_checks I have attached my latest diagnostics to hopefully help with this Thank you sutterstuff-diagnostics-20231006-1139.zip

I recently updated UNRAID to version 6.11.5 hoping that the system would be more stable. Today again I went to my Plex server only to find playback errors. The UNRAID dashboard was not available with the following errors: Warning: session_write_close(): write failed: No space left on device (28) in /usr/local/emhttp/plugins/dynamix/include/.login.php on line 218 Warning: session_write_close(): Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/var/lib/php) in /usr/local/emhttp/plugins/dynamix/include/.login.php on line 218 Warning: Cannot modify header information - headers already sent by (output started at /usr/local/emhttp/plugins/dynamix/include/.login.php:218) in /usr/local/emhttp/plugins/dynamix/include/.login.php on line 222 I have included a diagnostics file to help identify my issue. The array has over 50% available according to the Dashboard. I appreciate any help to get my system online. Thanks sutterstuff-diagnostics-20230805-1238.zip

I

Your server has detected hardware errors. You should install mcelog via the NerdPack plugin, post your diagnostics and ask for assistance on the Unraid forums. The output of mcelog (if installed) has been logged. I read that nerdpack required advanced - can someone guide me with steps to check this and fix? Thanks sutterstuff-diagnostics-20230214-1614.zip

(currently 96 % used) Possibly an application is storing excessive amount of data in /tmp. I have included latest diagnostics and would appreciate assistance to deal with this issue. Thanks sutterstuff-diagnostics-20230214-1614.zip

I tried to log in to my UNRAID and I get this. I have no idea what to do! Any suggestions? Warning: session_write_close(): write failed: No space left on device (28) in /usr/local/emhttp/plugins/dynamix/include/.login.php on line 218 Warning: session_write_close(): Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/var/lib/php) in /usr/local/emhttp/plugins/dynamix/include/.login.php on line 218 Warning: Cannot modify header information - headers already sent by (output started at /usr/local/emhttp/plugins/dynamix/include/.login.php:218) in /usr/local/emhttp/plugins/dynamix/include/.login.php on line 222

My system setting tools (Fix common problems) found an error 'parity is disabled'. I have no idea how this occurred. I clicked begin investigation here but nothing seems to happen. I have included my latest diagnostics file to help and I will do my best to discover through searches how to fix this. Rick sutterstuff-diagnostics-20220724-1806.zip

I have had this before but I am not sure what is actually going on. I appreciate your help! sutterstuff-diagnostics-20220706-1605.zip

I want my PMS to be able to allow people that I have shared access to view remotely on either a TV or device as well as myself typically on my TV. Is the PMS that I currently have the best choice to have PMS on a NAS to view on network as well as remote?

I believe the PMS I am using is plexinc/pms-docker The Docker URL is https://hub.docker.com/r/plexinc/pms-docker/ In regards to the stability of UNRAID etc., this morning when my PLEX was unable to connect, I rebooted the UNRAID NAS and waited for the RAID to reconnect. I attempted to launch the PMS through UNRAID docker and it did not connect. I went to plex.tv and tried to bypass the docker through Unraid and no luck. Less than 5 minutes later, plex was now connected though the media was now unpinned with a triangle. Typically I go to Authorized devices and delete my PMS to then have the system 'find' a new PMS. In the authorized devices my PMS states: Plex Media Server Docker Container Linux 5.10.28-Unraid and is now online.

Interesting... Plex just connected but I had to reclaim plex. I watch plex connect - then disconnect and then reconnect. Now, UNRAID is off with a refused to connect. and about 30 sec without a refresh, it comes back online. I don't have many issues with my network that I am aware of and the NAS is connected directly to my Orbi router and not through a switch

I believe I am using Plex Media Server. Obviously, I am not knowledgeable regarding appdata and system share on my RAID. suggestions?