Syco54645

Wouldn't using new config and placing a drive in the wrong location cause data loss? I do not trust myself to not mess up somewhere along the line with 10 drives to convert. Yes please if you can give advice I would greatly appreciate it (I am on 6.9.0 if it matters). I have posted on the reddit community multiple times and was told that I basically must use unbalance to move all of the files off of the drive then use new config to change the format of the empty drive. This video was given to me as the basic method, just not following the encryption bit.

So I am sitting here with an server that was setup when ReiserFS was still the recommended file system and am looking for a simple way to convert these drives to XFS and am coming up empty. It seems that ReiserFS will eventually be fully abandoned in favor of other file systems. The issue is all of the current processes require the somewhat dangerous tasks of creating a new config. Would it be possible to create a feature to aid in this process?

So I am using this for 7 days to die and am trying to disable automatic updates to the server. i see mention of doing it but not instructions. can someone please help me out?

Yes at this point just going to wait for the lsi. Nothing else is going to get me up and running I think. Probably will swap to the lsi card and start the array, making sure anything that may write to the array is stopped and allow the parity sync to happen. The errors were only cropping up last night during a sync.

I have an LSI card on order, just waiting for it to arrive. I am seeing that Marvell is not recommended for Unraid. This card was recommended to me by someone in #unraid on freenode, not that it matters just giving my reason for purchasing. I thought one of the Marvell cards was bad as when I moved the drives to the onboard sata and the other card the errors went away, till I tried to rebuild then I got a bunch of read errors. I have done multiple extended smart tests on the drives that are having said problems and they check out fine every time (except for disk 9). Physically my server is a 4u rackmount rosewill case and the drives are all in Norco ss500 cages. Card0 had 8 drives on it and card1 had 4. Cage0 and 1 were on card0 and cage2 was on card1 I do not think the issue lies there as I was first having issues with all drives on card0 which were in cage0. The 5th drive was working fine, it was plugged into the onboard sata ports. I have removed drives from card0 and moved the drives that were having issues to onboard sata. The other 4 to card1 and I am now having issues with the drives originally on card1. Because of this I do not think the issue is in the cages as I am having issue across all three. How would you suggest I test for stability? Create a new server on a different stick and toss drives in it? That actually does not sound like a bad idea to me now that i say it. I have a pile of drives that were pulled for age but were still performing well. i can create a new server with those on the current hardware and see if I have the same issues. essex-diagnostics-20191115-0106.zip

Well I read more docs and it seemed like new config was the way to go. I did it and everything seemed fine till it wasn't. Started getting new read errors on completely different drives. Swapped the PSU for a brand new one and it did not make a difference. Here are the diagnostics files. They are not from when read errors were occuring, at least I do not think that they are... essex-diagnostics-20191115-0106.zip

Will try to accurately and completely explain what happened and the state that I am currently in. I have a server with 12 drives and dual parity. The parity disks are 8tb drives. Yesterday the power company stopped by to let me know they would be replacing a pole in front of my house. I shut down my server and went to lunch. When I got back the power was back on so I started my server. Upon booting I had alerts that drives were missing, 5 to be exact. The array did start somehow, not sure how. Docker was also started and a few containers were running... Anyway I stopped the array and the drives were not detected by the os. Thought perhaps it was a random issue so restarted. The drives all came back and the array restarted but 2 were marked disabled and emulated. Then I started to get read errors on 6 drives (including the 2 that were "disabled" so I once again shut down. Checked the layout of cables and turns out all of the drives were all on the same SAS controller. Removed the SAS controller and everything boots fine, all drives present but still the 2 drives are disabled. That would be fine but now I am getting a SMART error of "Current pending sector" with a value of "1" on another drive (it was connected to the SAS controller and one that was tossing read errors). I ran an extended test on the 6 drives that were having read errors and all appear fine except for the one still having the pending sector error. As far as Unraid is concerned I have two failed drives. With the SMART error I am worried about rebuilding parity and having an issue there. I want to throw out that that the two drives that are disabled are a 4tb and an 8tb. I cannot be sure that no data was written to the array when I booted as docker had started and a few containers were running... How would you proceed here? Would it be better to do the new config route and hope that the drives are matching parity? Would it be better to remove the drives then add them back and allow it to rebuild? If so should I add them both at the same time or would it be better to do individual? Would the 4tb rebuild faster than the 8tb? If so that would give me the benefit of only having 1 failed drive if something else happens in this time period. Worried I may have to start a manual recovery of files here and that is going to be a mess...

that would be perfect if there was a place to buy it...

So I am trying to find a case with top to bottom 5.25 external bays. Anyone making those any more? Something like this. https://www.newegg.com/p/N82E16811112261

I used wget to download it here /boot/config/plugins/preclear.disk/ then mv <script> preclear_disk.sh. I gave up and am just running it in screen.

It's the only one in the dropdown list? yes

so i followed the instructions in the first post and it still says the script is "gfjardim - 0.9.6-beta". is this to be expected?

ugh. i read the post multiple times and somehow missed that line. thanks

is there a way to use this from the gui?

does anyone know which previous version worked?

Actually we could use comskip as long as we have mkvtool as well. Here is some info for it. http://forums.plex.tv/discussion/232408/postproccessing-usage-examples/p1 Would love to see this make it into the docker.

So just saw talk of Plexpy, any chance of getting a plugin for that? Seems pretty awesome for monitoring Plex.

I can try to get them later. busy with work right now. The FFMPEG supplied with Emby seems not to work anymore with they way this plugin is setup, but no worries, I had included my version of FFMPEG a while back. I have updated the start command for Emby to use this copy instead. Update the plugin to the newest one, restart Emby, and all should now work. Now emby starts but there is nothing in the server at all. Where are the useful logs for emby located on unraid? logs are located in /configdirectory/logs i believe. No changes that I made would impact that part of the app, just added a switch to point it to ffmpeg. It may be a bug, as I had to rescan my library and then everything was back to normal on my test machine. That appears to have fixed the problem. Now to see how emby compares to plex. Now that I know the log location I can be of more help in the event that something happens in the future.

I can try to get them later. busy with work right now. The FFMPEG supplied with Emby seems not to work anymore with they way this plugin is setup, but no worries, I had included my version of FFMPEG a while back. I have updated the start command for Emby to use this copy instead. Update the plugin to the newest one, restart Emby, and all should now work. Now emby starts but there is nothing in the server at all. Where are the useful logs for emby located on unraid?

I can try to get them later. busy with work right now.

Can confirm that videos are not playing.

It is appreciated. Like I said I started to look at the script to see what the issue could be and how I could bypass it (with emby) but lost interest. Something about working 15 hours a day programming already that causes you to hate computers. Go figure...

Exactly. I have had nothing but issues with plex lately. That is why I wanted to try Emby.

Never considered that happening. That would be very not good in my household...

Not sure if this helps in debugging the issue but the file Embyserver-PhAzE-3.0.5781.2-src.zip appears to be corrupt. I do not know enough about how your install scripts work to know of anything more to do (and I do not have time to trace through a 1200+ line bash file).