Naustradamus

🫡

Thanks for the info! And, also, sorry. It's not like there's any important update in the new version, but I've recently dived into Glance, and added a docker release page ... and, well .... I've triggered another OCD. Maybe I should remove it... 😅

There's probably a reason that I'm not aware of, but why isn't this docker updating to the newest version? The official has updated to 6.1.1.10360 almost a week ago, yet binhex one is still on 6.0.4.10291 ... is it due to some processing or conversion between radar and binhex repositories?

Hello, This maybe the wrong place to be, but as it relates to unraid directly, I wanted to ask. I'm still currently using using plex, and with it using ram transcoding to /tmp location. All seems working fine (128gb ram) I've been wanting to dip my tow in jellyfin, but I rather not use SSD or HHD transcode. I know reliability is good and cost of ssd keeps going down, but I have lots of ram, 2160p vids would normally be directly play, so at most I can see transcoding from 2160p down to 1080p, or 1080p -> 1080p due to codec issues, etc. I'd rather then use ram if possible, I do have lots. I'd read before that jellyfin doesn't well support ram transcode as it normally transcoded the entire video rather then segments, and didn't always clean it's temp folder as well, also throttling transcoding after reaching the buffer amount (I like 240 seconds myself) didn't always happen. From https://github.com/jellyfin/jellyfin/pull/8744, it seems it was to be pulled into the long waited 10.9 release. Does anyone know if ram transcoding is viable, and if ffmpeg's segment deletion works well with it? I've been searching threads for this subject since the update, but all I find is older stuff of people setting up ram transcode, then people responding that it doesn't work well. Probably should just try it but yeah, kind of scared to simply try things sometimes, sorry about that.

Hi, sorry for the delay in responding. Saw your reply while at work, and was busy after that. Thanks for the advise! I've done so, disk rebuilt too. Hope it's not the backplane though, the other 3 drives on it weren't affected, though it was the one farthest from where the power cable plugs in. Again, very much appreciated!

Hi, Looking for help/second opinion please. Last night, a HDD got a read error and has been disabled by unraid, being emulated. I started a extended SMART test at the time. I'm not able to due much more yet, cause this happened during a Parity drive rebuild (changed drives to increase parity capacity). I shut down all dockers and services for now. The extended SMART test came back no errors. From what I can understand from the results, I'm planning on restarting the server once the party is done rebuilding, and keeping and eye on it going forward. That said, I don't understand all aspects of the results, so though I'd ask here incase there's other things that indicate that it is indeed failing. So bellow is both the diagnostics made now (sorry, didn't think it creating one last night when it happened) and ethe ext SMART test for the drive specifically, incase it's not in the diagnostics. Any and all advise and help is appreciated! oracle-diagnostics-20230419-1411.zip oracle-smart-20230419-1411.zip

For those that use/still use Plex and wants them to support ARC for transcoding: https://forums.plex.tv/t/intel-arc-gpu-support/832586 As pointless as it'll probably end up being.

Lovely Ah well lol, thanks again for the help. I'll skip the formatting of it then, try the warranty. Thanks again, your help was GREATLY appreciated!!

Thanks! Dang, looks like I might be out of luck, cause yeah, error happens again once I start the container. To be fare, I don't think the container was the problem, just that due to the setup listed above, it was the only container that accessed the SSD. For the moment in time, I'll move the files onto my main cache drive, and run the container from there. If that works, I can try and re-format the nvme ... see where it goes from there. Not the vacation I was expecting, oh well. It's only been over a year, still under warranty if needed. Thanks again. Incase you notice anything further, I'm adding one more diagnostic, after the container runs and causes the issue. oracle-diagnostics-20230302-1010.zip

Thanks for replying! Sorry for the delay, had went to bed. Posted bellow. Restarted, kept dockers off as the error seems to happen after a certain docker opens and attempts to use the nvme. For further info, this nvme is plex dedicated. Was trying to get the thumbnails, scroll preview, metadata and all to be on SSD to make navigations and such very responsive. Not sure if that info helps, but yeah. I didn't see any error in the new diagnostics, but most likely I don't know what I'd be looking for. Thanks again for the support. oracle-diagnostics-20230302-0928.zip

So as I've been looking into it, I had found this post linking to this. Am having a problem with step 2, as dumb as it sounds, I don't know how to create a folder on a single drive outside of a share. I'm assuming it must be while unraid is in maintenance mode, but I'm not sure of that either. On side note, found some btrfs commands and tried rescue fix-device-size, no device size related problems found. Bellow was the second command I tried, and what returned. Tried clear-space-cache v1 and v2, long shot at has noting to do with the error message I think but yeah, still same error on btrfs check. Not sure if a --repair would fix the type of issue, or if it is the nvme going bad. Unless someone advises me to try the repair, think my next step is the restore method but me being me, not getting the steps to get things ready before 'btrfs restore -v' Just updating to where I'm at currently

Hello, Sorry, am a user but not a very technical one, so this has just happened and not very sure of how to resolve yet. Fix Common Issues plugging has reported to me that a drive, not my default cache drive but a second one is read only. As in the title: "unraid Drive mounted read-only or completely full. Begin Investigation Here" I think I found in the system log the error it's mentioning, yet I don't know how to decipher it. I attacked the diagnostic zip, as well as a txt file for what I see when I click on the disk log info for the drive. Don't think it helps at all, but made sure the drive was balance and scrubbed, did also perform a filesystem with the following (--readonly): Was thinking of doing a filesystem check with "--repair", but from what I could find, it's very much advised to avoid, plus I wouldn't know how to enter it in, cause I think it wants a input after to confirm, so either would need to do it from the console, or something like "--repair -y" My apologies if if this seems a easy thing, just not the most technical. Also worried it's the drive, it's a Samsung 970 evo plus 1tb, a bit over a year old. Am planning on adding another for parity this year, just figured they'd last longer (I did read recently about samsung drives failing, but thought my model was in the clear) Thanks in advance for any assistance provided, though I'll thank you again in the replies. oracle-diagnostics-20230301-2036.zip nvme0n1p1.txt