propman07
-
Posts
67 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by propman07
-
-
Got it. Thanks to all for the replies and the information.
-
5 hours ago, dlandon said:
USB is not generally robust enough to do reliable preclears.
Thanks for the reply. Does that imply that a device attached via unassigned devices as an example is not reliable to read/write data from/to?
-
Hi- Trying to get the UD preclear to work, but running into issues. I was able to install the UD preclear plugin and it does show up when I go to Tools>Disk Utilities>Preclear Disk. I clicked on the drive shown (which is attached to my tower running Unraid 6.12.8 via a USB 3.0 enclosure). I select Start Preclear text, and configure the pop up window as shown in the screenshot.
After that, it appears to stall as the status of the preclear never changes from Starting
Any pointers would be appreciated.
Thanks.
-
trurl / itimpi-
Thanks for the replies. Next time, I'll know how to proceed. Thanks again for the help.
-
Parity check completed.
Last check completed on Mon 11 Mar 2024 10:59:41 AM PDT (today)
Duration: 19 hours, 39 minutes, 22 seconds. Average speed: 141.3 MB/s
Finding 6 errorsDiagnostics attached. Thanks.
-
Makes sense. Thanks for the info...running correcting parity check now. Will post results when complete.
-
Thanks for the reply...
I'll run the correcting parity check as recommended. Is it a good idea to shut down all docker containers, or just let the parity check run with them running?
Thanks.
-
Posting an update.
I was finally able to get some new SATA cables installed. Ran not correcting parity check and it returned 6 errors. Diagnostic log attached.
How would I go about determining what the 6 sync errors are?
Thanks.
2024-03-10, 14:15:09 17 hr, 59 min, 14 sec 154.4 MB/s OK 6
2024-02-25, 23:02:12 52 sec Unavailable Canceled 4
2024-01-06, 19:08:41 18 hr, 8 min, 40 sec 153.1 MB/s OK 37756 -
Sorry for late reply. I'll run a non-correcting check after I get the SATA cables swapped out.
Thanks again for the help.
-
JorgeB- Got it. I'll work on ordering cables and run a parity check once I get them installed. If you wouldn't mind, could you point out what led you to believe that there were ATA errors in the log file? I'd like to learn more about troubleshooting these types of issues.
Thanks.
When I do perform the next parity check, should I select the box to write the corrections or leave it blank?
-
Thanks. See attached.
-
Hi-
Running Version: 6.9.2 and the parity check that I have scheduled to run every 90 days threw the following:
Last check completed on Sat 06 Jan 2024 07:08:41 PM PST (four days ago)
Finding 37756 errors Duration: 18 hours, 8 minutes, 40 seconds. Average speed: 153.1 MB/secI have a single 10TB parity drive and four 10TB drives in the array which is at 64.6% capacity. What would the next steps be in order to preserve all of the data on the array. I'm not sure how to figure out which drive(s) are failing / throwing the errors. I checked the individual drives SMART reports, and they all show as completed without errors.
No power outages to report as the server is connected to a UPS device.
Thanks.
Edited to add some parity check history for reference. No recent hardware changes
Date Duration Speed Status Errors
2024-01-06, 19:08:41 18 hr, 8 min, 40 sec 153.1 MB/s OK 37756
2023-10-07, 19:04:22 18 hr, 4 min, 20 sec 153.7 MB/s OK 0
2023-07-01, 19:04:26 18 hr, 4 min, 25 sec 153.7 MB/s OK 0
2023-04-01, 19:07:37 18 hr, 7 min, 36 sec 153.3 MB/s OK 0
2023-01-07, 19:05:34 18 hr, 5 min, 33 sec 153.5 MB/s OK 0
2022-10-01, 19:04:53 18 hr, 4 min, 52 sec 153.6 MB/s OK 0
-
24 minutes ago, propman07 said:
Went to watch a little Plex and found the server to be unavailable. Checked Unraid, and Plex service stopped. Tried to start it, but got a SERVER ERROR message. Latest red entries from log file shown below.
OSError: [Errno 5] Input/output error
2023-08-23 02:24:38,120 CRIT uncaptured python exception, closing channel <POutputDispatcher at 22663105671696 for <Subprocess at 22663099747408 with name plexmediaserver in state RUNNING> (stderr)> (<class 'OSError'>:[Errno 5] Input/output error [/usr/lib/python3.11/site-packages/supervisor/supervisord.py|runforever|218] [/usr/lib/python3.11/site-packages/supervisor/dispatchers.py|handle_read_event|276] [/usr/lib/python3.11/site-packages/supervisor/dispatchers.py|record_output|210] [/usr/lib/python3.11/site-packages/supervisor/dispatchers.py|_log|189] [/usr/lib/python3.11/site-packages/supervisor/loggers.py|log|345] [/usr/lib/python3.11/site-packages/supervisor/loggers.py|emit|227] [/usr/lib/python3.11/site-packages/supervisor/loggers.py|doRollover|264])Any troubleshooting advice would be appreciated.
Thanks.
Looks like the cache drive I was using for Plex has failed...here are some of the log entries for that drive:
Aug 23 02:05:05 XXXTOWER kernel: XFS (sde1): metadata I/O error in "xfs_imap_to_bp+0x5c/0xa2 [xfs]" at daddr 0x1e68a1f0 len 32 error 5
Aug 23 02:06:08 XXXTOWER kernel: ata4.00: exception Emask 0x0 SAct 0x2 SErr 0x0 action 0x0
Aug 23 02:06:08 XXXTOWER kernel: ata4.00: irq_stat 0x40000008
Aug 23 02:06:08 XXXTOWER kernel: ata4.00: failed command: READ FPDMA QUEUED
Aug 23 02:06:08 XXXTOWER kernel: ata4.00: cmd 60/20:08:30:a2:68/00:00:1e:00:00/40 tag 1 ncq dma 16384 in
Aug 23 02:06:08 XXXTOWER kernel: ata4.00: status: { DRDY ERR }
Aug 23 02:06:08 XXXTOWER kernel: ata4.00: error: { UNC }
Aug 23 02:06:08 XXXTOWER kernel: ata4.00: configured for UDMA/133
Aug 23 02:06:08 XXXTOWER kernel: sd 4:0:0:0: [sde] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s
Aug 23 02:06:08 XXXTOWER kernel: sd 4:0:0:0: [sde] tag#1 Sense Key : 0x3 [current]
Aug 23 02:06:08 XXXTOWER kernel: sd 4:0:0:0: [sde] tag#1 ASC=0x11 ASCQ=0x4
Aug 23 02:06:08 XXXTOWER kernel: sd 4:0:0:0: [sde] tag#1 CDB: opcode=0x28 28 00 1e 68 a2 30 00 00 20 00
Aug 23 02:06:08 XXXTOWER kernel: blk_update_request: I/O error, dev sde, sector 510173744 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0
Aug 23 02:06:08 XXXTOWER kernel: ata4: EH complete
Aug 23 02:06:08 XXXTOWER kernel: XFS (sde1): metadata I/O error in "xfs_imap_to_bp+0x5c/0xa2 [xfs]" at daddr 0x1e68a1f0 len 32 error 5
Aug 23 02:06:08 XXXTOWER kernel: XFS (sde1): xfs_do_force_shutdown(0x1) called from line 296 of file fs/xfs/xfs_trans_buf.c. Return address = 00000000814715b6
Aug 23 02:06:08 XXXTOWER kernel: XFS (sde1): I/O Error Detected. Shutting down filesystem
Aug 23 02:06:08 XXXTOWER kernel: XFS (sde1): Please unmount the filesystem and rectify the problem(s)New drive on order....now if I could only remember how I set up Plex to use the cache drive.....and I assume that all of the images that were on the drive will now need to be re-created....
-
Went to watch a little Plex and found the server to be unavailable. Checked Unraid, and Plex service stopped. Tried to start it, but got a SERVER ERROR message. Latest red entries from log file shown below.
OSError: [Errno 5] Input/output error
2023-08-23 02:24:38,120 CRIT uncaptured python exception, closing channel <POutputDispatcher at 22663105671696 for <Subprocess at 22663099747408 with name plexmediaserver in state RUNNING> (stderr)> (<class 'OSError'>:[Errno 5] Input/output error [/usr/lib/python3.11/site-packages/supervisor/supervisord.py|runforever|218] [/usr/lib/python3.11/site-packages/supervisor/dispatchers.py|handle_read_event|276] [/usr/lib/python3.11/site-packages/supervisor/dispatchers.py|record_output|210] [/usr/lib/python3.11/site-packages/supervisor/dispatchers.py|_log|189] [/usr/lib/python3.11/site-packages/supervisor/loggers.py|log|345] [/usr/lib/python3.11/site-packages/supervisor/loggers.py|emit|227] [/usr/lib/python3.11/site-packages/supervisor/loggers.py|doRollover|264])Any troubleshooting advice would be appreciated.
Thanks.
-
Thanks for the reply. I tried to follow the directions at the link provided. I'm running an older version of Unraid (6.9.2) for reference. I was able to telnet into the server using Putty. Logged in using same username/password credentials. Once logged in, I tried the command 'use_ssl no' as directed. I received the following error message:
'-bash: use_ssl: command not foundI was able to get the the GUI by going to https://my_server_ip_address:port. I did get the risk errors from my browser, but I was able to ignore them, and proceeded to the login page.
Now, off to figure out if I'm ready to upgrade from 6.9.2
Thanks.
-
Hi- I was trying to login to my server this evening, and received the following error message:
Hmm. We’re having trouble finding that site.
We can’t connect to the server at sldafjaslfk.unraid.net
I've tried to go directly to the IP address of the server with the same response. I can get to some of the docker containers that are running on the server by going to their specific IP address, but can't seem to get to the server page itself. The My Servers section on unraid.net shows the server is online, but when I click on the remote access link, same results.
Thanks.
-
Hi-
Saw this error on my server: Invalid file (or folder) contained within /mnt. Went to the link provided, and was instructed to post log files for more help.
Thanks.
-
1 hour ago, dabl said:
Who is 'you'?
Either one or both of the guys in this thread?
We're the ones asking the questions!
Maybe you mean the guy at TRaSH Guides?
Either way, point taken about the history of available options re: symbolic links and my characterization of 'completely wrong'. Probably not fair, I'd agree,
For my part I found just getting Sonarr, Radarr, and Prowlarr going and working hugely confusing even with any/all guides available, particularly the torrent client part since the only guide with a walkthrough for that was for QBittorrent and then it turned out the past few versions of that broke a bunch of stuff with Sonarr and Radarr so the docker had to be downgraded etc. But nobody said this stuff was a walk in the park
Re: losing data, to me, rebuilding libraries would be a worst case scenario which isn't that bad. God knows how many times I've done that with Kodi and Plex for who knows how many reasons. Big deal.
I suppose the mention of watched status is a good point though. I use Trakt so in theory that may solve that problem.
I'm really not trying to start anything here....if you read my initial post, I had a hardware issue with an nvme drive which failed due to excessive writes. I put the system online back in 2019, and it recently started to give me issues so I figured that I would come to the experts to see if I can change my configuration for the better, and try to avoid hardware issues down the road.
Losing data/rebuilding libraries would be kind of a big deal for me....but it wouldn't be the end of the world either. I've got my critical data (that would be a big deal if lost) backed up several times over, so if I were to lose that data reconfiguring things in unRAID, it would be painful, but again, I've got backups.
Watched status in Plex is not a big deal to me....I also use Trakt, but I don't believe that it is two way....meaning I believe that when you watch something on Plex, it will mark it as watched in Trakt, but I don't think that it works the other way around (mark watched on Trackt, and Plex will mark it as watched)
I've also been toying around with ways to move the data around to the new folder structure. I was going to try to go the rsync route, but it looks like that involves moving the data to the cache drive, then when mover runs, it will move it to the array. I've found that using Krusader appears to move the folders/files from one location to another without going through the cache drive. It also appears that doing a "move" in Krusader is almost instantaneous.....although I'll bet that transferring data like this is risky (using a move instead of a copy, verify target, then delete source) using Krusader.
Thanks
-
I'm hoping that when I move the Plex libraries (movies, tv shows, etc.) while Plex is shut down, it won't break anything. When I restart Plex, it will have the new locations mapped out, and the files will already be there (I plan on moving the files with rsync so I keep all of the dates intact), so it will still think everything is okay.
I should have checked the Trash guides for Plex setup....I went there, and saw there was a page, but didn't actually visit the page....see the attached image....looks like he hasn't had time to make any updates.
-
dabl-
Thanks for the reply. I figured that I could get the folder structure created, and get the 'arrs re-configured, as well as the download clients. Sounds like that wasn't too painful of a process. I have the same concerns as you....especially when it comes to the movie/TV show files, and what Plex will do when I move them. I'm a little concerned about watch history, but it's not going to be a deal breaker if I lose that. I'm a little behind you in the process, but I plan on moving all of the movies / TV files with Plex shut down. Then, I'll re-configure Plex per Trash's guide to point to the new locations, cross my fingers, and start the Plex docker. I already have the thumbnails/database on a separate SSD, so hopefully that will help things.
-
Hello-
Recently recovered from a hardware failure of my nvme drive (https://forums.unraid.net/topic/126560-copy-data-from-a-failing-cache-drive/) Installed two replacement nvme drives, and looking to make corrections to my folder setup.
I'm planning to use Trash's setup guides, but right now, my folder structure is a bit different. I'm trying to figure out the least painful way of reconfiguring to be inline with the folder structure as described in the guide.
Here is what I have for primary folders structure:
user
└── Media
├── Movies
├── music
└── SeriesHere is what I would like to get to (based on the guide)
data
├── torrents
│ ├── movies
│ ├── music
│ └── tv
├── usenet
│ ├── movies
│ ├── music
│ └── tv
└── media
├── movies
├── music
└── tvThanks.
-
Update:
Finally able to get the server back up and running. I installed the replacement nvme drive, and was finally able to get things back up and running. It looks like I probably lost my VMs, but I can re-create those. I did have some trouble logging into the server once I had the hardware replaced. It looks like the GUI does not like special characters in the password field. I had a "$" in my password, and I was unable to get it to save with that character in the password field. I removed it, and that seemed to be the fix. I'm running about 17 dockers for a total docker.img size of 17.6 GB. Thanks again to all that replied.
-
JorgeB-
Thanks for the reply. I ran through that yesterday. I don't want to lose the other passwords, so I may try the second method shown to remove the characters in between the two colon characters.
Thanks.
-
1
-
-
Here is where I am at.
Installed new cache drive. Booted server. At login screen used username/password combination. Screen said they were invalid? Made a few more attempts only to now be locked out? I went through the My Servers page, and it shows the server is online, but I can't seem to login, even though I did not change my username/password settings prior to the cache drive failing.
Parity check completed Finding 37756 errors...next steps?
in General Support
Posted
Final update-
I ran my scheduled parity check, and it completed with no errors. Thanks to all on the thread for your help.
Date Duration Speed Status Errors
Parity-Check 2024-04-06, 20:21:09 (Saturday) 10 TB 19 hr, 21 min, 8 sec 143.5 MB/s OK 0
Parity-Check 2024-03-11, 10:59:41 (Monday) 10 TB 19 hr, 39 min, 22 sec 141.3 MB/s OK 6