blu3_v2
-
Posts
54 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by blu3_v2
-
-
After blowing apart the server again, rechecking and re-seating all drives and connections I sat down and read through any logs from the Diagnostics.zip that I could decipher. I could not find any errors in SMART reports etc. and the syslog captured showed no errors, and the server had started up successfully and was ready to start with a Valid Array prior to logging in via Telnet and issuing the Poweroff command.
I then set about troubleshooting any other potential issues and thought I would try reboot my Modem/Router, and all wireless iOS devices that I use to access the server on my LAN. After booting up the server (again) I was able to access the GUI, Start the Array, and access all Dockers etc. (all using my original Cache Drive so all Dockers and Data were preserved including in-progress downloads). So it appears that it was simply a LAN issue (IP conflict, hardware issue with Router???).
-
Firstly a little about my setup:
- HP N40L Microserver running unRAID 6.7.2 with 6 Data Drives (8Tb Parity, 1 x 8Tb Data + 4 4Tb Data) and 1 Cache Drive (500Gb)
- System is used simply to download and store media files on my local network, and is attached to APC UPS and hardwired directly to Wi-Fi Modem/Router, otherwise all access is via Wi-Fi via various devices (iOS)
- Dockers: just the basics - Plex Media Server (LimeTech), ruTorrent (Linuxserver.io) and Sickbeard (all up to date with latest versions)
- Uptime prior to Crash was 52 Days, and Parity was last checked only 2 Days ago, with 0 errors. System has been rock-solid and I have never encountered any major problems.
The Incident:
Last night I arrived home from work, opened up ruTorrent and added a couple of magnet links. After adding the links ruTorrent became unresponsive. Seeing that there have been issues with various versions having 100% CPU usage and I often see the docket reboot itself I was not too concerned. I waited a couple of minutes and tried again but could not reach ruTorrent so I tried unRAID Home with the same result - no GUI access. I fired up Termius and logged in via Telnet successfully, so issued the 'Poweroff' command so shut down the server (stupidly forgetting to save a Syslog or Diagnostics as I did not initially think much of the freeze).
On reboot I was able to access the GUI, the Array was valid and all Array Drives present but I noticed that my Cache drive was missing from list of available Drives. I initially thought that maybe my old spinning rust disk had died, being the cause of the crash. I tried opening the syslog from the GUI but it had become unresponsive again. I figured that the 'dead' disk was causing slow reads/errors so logged in again via Telnet successfully and shut down again.
I opened up my server and replaced the Cache Drive with a (Brand) New SSD I had in the cupboard and booted back up. When I first booted I opened the GUI successfully but noticed multiple Array Drives missing. I quickly shut the server down (via GUI), opened it backup and checked/re-seated all connections. On rebooting I was sucessfully able to access the GUI and confirm that all Disks were present, Array was valid, and new Cache Drive detected. I assigned the new Cache Drive and clicked Start to start the Array but the GUI did not respond. At this point I was becoming seriously concerned. I thought maybe my motherboard had grenaded and was dropping disks, so tried to connect via Telnet but this did not respond initially either. After trying again I was able to access the server via Telnet and confirm that all Disks were present and detected using the ls -l /dev/disk/by-id command. I then shut down again, and did some research online about what steps to take.
I rebooted the server (again) and this time was unable to access the GUI at all (previous times I had been able to load the unRAID Home page, but it had not responded to commands), but could still Telnet in. I saved a copy of the Syslog and Diagnostics, which I have attached to this post (Note: on issuing the Diagnostics command I received a few lines of errors referencing missing info and giving line references to dynamix files etc, but the command completed successfully).
I am seeking the help of the unRAID community in diagnosing/fixing this issue. I have always found the community super-helpful and have been able to resolve any minor issues I have had in the past. At this point I am not sure what hardware is to blame (Mobo, RAM, USB/Boot Drive), or if it could be a Software issue with a corrupt file(s).
Could someone more knowledgeable than me take a look at the attached Diagnostics, help diagnose the cause(s) and/or let me know if there are any other steps I should take.
-
I also tried downgrading due to the previously mentioned CPU usage issue, however, since doing so my RSS Feeds no longer automatically update and files/folders are no longer automatically moved to their Tagged Directory (ie. TV/Movies) once downloads complete. I can manually Refresh Feed and downloads start fine.
I have so far tried restarting the Docker and returned to the latest build and these problems persist. I am guessing it is a permissions issue - could someone please some advice on what to check or how to fix permissions (I thought this was performed automatically on Docker start).
Update: Deleted Docker and reloaded from template (Latest) and the issues seem to have been resolved for now.
-
54 minutes ago, johnnie.black said:
Disk dropped offline, it's on a Marvell controller and these are know to drop disks in some cases, disk4 is on the same controller, has it been there for long and without issues?
Disk 4 has been on the same controller for a few weeks and has undergone a change from ReiserFS to XFS, as well as a complete Parity Check without issues. I set Disk 5 as No Device rather than attempt to add the old Parity back to the Array for now as it was giving errors while trying to Spin Down, and even now when Unassigned. I will unplug it until I can source a new SATA card and/or cabling.
-
47 minutes ago, blu3_v2 said:
My old Parity Drive was perfectly healthy, and I can now report that it was correctly recognised as an Unassigned Device once I shutdown the server and triple-checked all cabling (turns out it must have a loose/intermittent connection to my PCIe SATA card). It is now undergoing a Preclear just to be safe before being added as an Array Disk.
Looks like I spoke too soon. Shortly after starting the Clearing process I received Read errors and the Process Aborted. Have posted in General Support section as unrelated to this plugin.
-
On 2 April 2018 at 7:27 PM, hawihoney said:
I'm not sure if my failing drive was a parity drive before. But as it's SMART values are ok I bet it was.
I don't swap data drives if SMART values are ok. But I swap parity drives with perfect SMART values if I need a bigger one.
My old Parity Drive was perfectly healthy, and I can now report that it was correctly recognised as an Unassigned Device once I shutdown the server and triple-checked all cabling (turns out it must have a loose/intermittent connection to my PCIe SATA card). It is now undergoing a Preclear just to be safe before being added as an Array Disk.
-
2 hours ago, hawihoney said:
Yes, wipefs did the trick. Double check that this drive is not part of the array. Double check the correct device name. Issue "wipefs /dev/xxx" (replace xxx by correct device) without any additional parameters to check the current FS. This step is not necessary. It's just to check if it gives a non-unRAID-FS output. Finally "wipefs --all /dev/xxx" to wipe the disk. Lasts a second or so. After that I could attach the disk immediately to UD.
Thanks for the tip.
I just shutdown my server to check that it was not a cabling issue, and now when I boot the drive is not recognised at all. Looks like I will have to shutdown and recheck cabling again or remove the drive and see if I can format it from another system before adding to the array. I find it strange that the drive had previously been functioning perfectly in unRAID as a Parity drive, then when installed back into the same system it is not recognised. Maybe it has to do with the fact the the Parity drive contains data without a file-system or partition structure as such.
-
On 26 March 2018 at 8:29 AM, hawihoney said:
This is the output of wipefs. DOS? On a 3TB drive? Last time I used DOS was when using 1,44MB diskettes.
Really weird.
Linux 4.14.26-unRAID. root@Tower:~# wipefs /dev/sdg DEVICE OFFSET TYPE UUID LABEL sdg 0x1fe dos root@Tower:~#
Did you ever get this issue sorted out and your disk recognised?
I have a similar problem, having just completed a Parity Disk Upgrade (4 > 8Tb). When I plugged my old Parity Drive in it is not recognised as an Unassigned Device (from the unRAID Main Tab or when using the Unassigned Devices Plugin). It was seen as an output when I ran ls -l /dev/disk/by-id from the terminal and also showed up in the recently updated Preclear Disks Plugin screen (as device sdh), however, there is no drive/model info attached to the drive and when I attempted a Preclear it failed.
-
Hi,
My unRAID server (WATCHTOWER) has been running flawlessly and is currently on Version 6.3.2, however, I have just noticed the following error being repeated in the syslog since my last reboot:
Watchtower ntpd[1454]: receive: Unexpected origin timestamp 0xdc894add.aeb536f1 does not match aorg 0xdc894b20.ae287975 from [email protected] xmt 0xdc894add.cfcfe1a9
This is the first time I have seen this error, so I have attached the diagnostic.zip to this post. Could anyone suggest a fix, or at least let me know if it is anything to worry about.
Thanks in advance
P.S. A bit of background. I have just moved house and plugged into the ADSL modem prior to booting up the server on this occasion. Could this be the cause or contributing to the problem? -
On 3/25/2017 at 11:51 PM, brettm357 said:
Have transferrred from limetech plex to official plex very painless
Would you mind posting the steps you took to transfer?
-
Thanks for the explanation, glad to hear that those permission changes were by design. Now i can try and narrow down the cause of my Plex issue.
-
I apologise if this has come up earlier but I could not find a definitive answer to this question for Tom (or any of the Limetech staff really) - what owner/user should the official LT Plex Docker use?
According to this thread https://lime-technology.com/forum/index.php?topic=41562.0 it is 99:users, however, on the Plex Forums here http://forums.plex.tv/discussion/comment/987463/#Comment_987463 they say it should be unraid-plex:users.
To further confuse matters, after updating Plex to the most recent public version (9.12.8 ) using the Docker Tab in unRAID, my Preferences.xml is changed to nobody:users (even after I did a chown unraid-plex:users and chmod 777 to this file prior to the update following some permission issues).
I am still trying to get to the bottom of some weird Plex behaviour and want to find out the correct information regarding Plex and updates on unRAID. Thanks
-
Anyone got any ideas?
What PSU are you using for your Pi? Apparently this is common symptom of low-power.
I had a similar problem which was fixed by upgrading from a 1.0 amp iPod adapter to a more powerful 2.0 amp iPad adapter/PSU.
-
Plex notified me that a manual upgrade is required to get the latest version. Is this something I need to wait for a docker update to receive?
Sorry, new to dockers.
I think you will need to wait for Limetech to update their docker.
When I updated last time I clicked on 'Check for updates' on the Docker tab, then clicked on the Plex icon and selected 'Update' and unRAID took care of the rest.
-
Can someone please offer some advice on how permissions should be set for Plex config folders, how to check my permissions and then correct them if needed.
Using putty I have logged onto my server and checked folder/file permissions using the ls -l command.
It appears that the official Limetech Plex is setup with owner unraid-plex and group users (unraid-plex:users). However, a couple of folders and files had been changed to nobody:users during the recent update.
To restore permissions I did the following after navigating to the Plex folder:
chown -R unraid-plex:users <folder/file name> chmod -R 777 <folder/file name>
I hope this is the correct procedure, however, it appears to have fixed some of my issues caused by the last update. I can now access the server settings from other devices, access the server from iOS devices and view thumbnails for content.
Hope this helps anyone else having permissions issues with Plex caused by updates. Can anyone suggest how these permissions may have been broken during the update?
-
Can someone please offer some advice on how permissions should be set for Plex config folders, how to check my permissions and then correct them if needed.
From a post on the Plex forums I have been told I have some permission errors (see below)
I can see some permission errors in other log messages in the log and may be there is a permissions issue - you need to check that for all directories below.
/config/Library/Application Support/Plex Media Server/
Aug 03, 2015 19:24:17 [0x2b7a7bc01700] ERROR - Error opening file '/config/Library/Application Support/Plex Media Server/Cache/PhotoTranscoder/bd/bd6fef76ab2f479a36eb2084ab42a2c129a44ae4.jpg' - 13
Aug 03, 2015 19:24:17 [0x2b7a7bc01700] ERROR - Failed to open file for streaming: /config/Library/Application Support/Plex Media Server/Cache/PhotoTranscoder/bd/bd6fef76ab2f479a36eb2084ab42a2c129a44ae4.jpg
Error 13 I believe is this error
#define EACCES 13 /* Permission denied */
-
I recently updated my Plex docker using Limetech's Official Repo and have noticed some strange behaviour and was wondering if anyone else has noticed these issues or have any suggestions.
NB.Everything was working perfectly prior to updating.
Following the update I can still scan and update with new metadata for new items but after updating I notice the following:
- TV Show & Movie thumbnails are all blank on Home screen/On deck/Recently added and when browsing individual libraries. However, when I enter a TV Show Season folder I see thumbs for the last couple of episodes (some scanned prior to update)
- New items added to library correctly and can be browsed/watched fine
- Unable to find server using iOS app. Can browse using PlexWeb using the same device but within the app nothing shows up
- Unable to access server settings from any device 'Server settings are unavailable' message displayed
From reading the Plex Forum https://forums.plex.tv/discussion/170436/server-settings-are-unavailable I gather I may need to delete some bundles from the Plug-Ins folder, however, my symptoms don't seem to match those described in the support article https://support.plex.tv/hc/en-us/articles/201119258-Resetting-System-and-Framework-bundles
Has anyone else had these problems and offer any advice?
[6.8.0] Array Devices Blank after Update
in General Support
Posted
I have a HP N40L Microserver running 6.7.2 with no issues.
After installing the 6.8.0 Update via Update OS and rebooting, my Array Devices in the Unraid GUI are all missing/blank - even my boot USB. Strangely the GUI reported Configuration Valid, however, instead of attempting to Start the Array I captured Diagnositics and downgraded back to 6.7.2 until this Issue can be explained/resolved.
Daignostics
Diagnostics.zip
Before
After
This is the first time I have had an unsuccessful Update using Unraid, and would like to update to the current stable version rather than remain on a deprecated release. Could someone please take a look and provide some advice.