fespinoza831

is there a way to check a disk for error while its not part of the array?

Sorry here it is. plexserver-diagnostics-20231008-0508.zip

i tried adding a disk with a new config but the disk said it was unmountable /unknown file system, but before hand i was able to mount the disk and view its contents. Is there a way to run a filesystem check on a disk that isnt mounted, meaning prior to mounting so that I dont run into these error when trying to add a disk and run a parity sync after the new config? Does this mean this Parity sync will be no good?

Parity Sync is about to complete with no errors. as far as adding back the other disks, will I need to create a new config again? or add a new blank disk and start transferring data to the array?

Ok I just put in the new card hooked it all up and started up the server checked, repair the filesystem for each drive and made a new config. Parity is running but it says its going to take 73 days. in the process of writing this one of the disks is showing errors during the parity sync. Am I missing something? how do I fix the error is the drives are good? or are they bad? plexserver-diagnostics-20231005-1933.zip

Just got the new card but was wondering about one of the plugs on the cables and one on the card. what are these for?

What price range should I be looking at? does this work? https://www.amazon.com/SVNXINGTII-SAS9300-16i-9300-16i16-Port-TrueNAS-SFF-8643/dp/B0C6QG9NPH/ref=sr_1_5?crid=2XR2XXA4P2NHU&keywords=SAS3+lsi&qid=1696276868&sprefix=sas3+lsi%2Caps%2C135&sr=8-5&ufe=app_do%3Aamzn1.fos.18ed3cb5-28d5-4975-8bc7-93deae8f9840 https://www.ebay.com/itm/385805168557?hash=item59d3c7afad:g:gPEAAOSwszlkufmF&amdata=enc%3AAQAIAAAAwD%2F3EjAIYHESN2BDggly14Ncs%2BPCFni%2FWAKDsLgLE1bL82w%2FLkIEl2C6Unlt%2BOkITGWFZ%2FhROZU5EJXjaKNJCxXQp9qv6WvOPBUf2LQnUyv0gsAx3I9Np85vJxy%2B2cAPHAREbvOzgztXVQNGIklX9vfPP0iuTh7z0UetsmrhxjO9N05TgUuN79YSNeKraL%2FwuerYs6UBLxX20RPUvScCTbvMtsABch1OpFYviZhbQbUhkMkXe2w9vHfADN67ZoK9hA%3D%3D|tkp%3ABk9SR_rOz5_eYg

I dont have another LSI HBA but Im ready buy one. Which do you recommend? wierd that drive is connected to the same power cable as 2 other drive after it and to the same data cable/card as 3 other drives.

Here it is. I created a new config eliminating the 3 drives that were getting disabled and they aren't currently connected to the server. the Parity sync is currently at 57% but just noticed that disk 9 is showing errors. I guess I just made my situation worse. plexserver-diagnostics-20231002-0635.zip

So Im now at 3 disks being disabled and I believe its going to be a bad HBA card. I didnt have any issues prior to upgrading to Unraid 6.12.4, could this be just a coincidence? since my parity drive was the first to be affected i know i just cant rebuild the drives, how should I proceed once I have a replacement card and what card do you recommend? Parity sync is finally running with no errors and should be done in about 15 hours which is normal for me. was wondering how to recover the data on the disabled drives. can i plug them into another pc to pull the data, can it be done in windows or does it need to be on a linux machine or can unraid do that?

it just completed but it says it was successful but like I said two drives are currently unmounted.

i have removed 2 drives that seem to always fail after i have swapped the cables. but when i run the parity sync it says its only taking 30 minutes. so how to i confirm theres no read errors before the parity sync?

At this point im willing to pay someone for help.

Parity drive seems fine now but it only took 30 minutes to sync which i thought was odd. but disk 1 is not installed any time i add it its starts acting up. how would I go about using disk 1 as a 2nd parity drive and finding out what I lost on disk1. i really just want to make sure Im protected and make sure these issue were resolved. plexserver-diagnostics-20230930-1027.zip

i got more disks with errors now. What should I do?

Disk 1 is now disabled and im still trying to run the parity sync, am I going to loose what was on disk 1 and if so is there any way to find out what was on it. plexserver-diagnostics-20230930-0717.zip

Restarted, checked all cables, all drives appeared good one it was up again. Started the parity sync, but I still get errors on disk 1 once the parity starts. not sure how to proceed. plexserver-diagnostics-20230930-0645.zip

Even though the errors are on disk1 and not the parity drive?

Parity is still running but there's tons of issues There are no exportable user shares /var/log is getting full (currently 100 % used) and the paths below dont exist /mnt/user/appdata/ /mnt/user/system/docker/docker.img plexserver-diagnostics-20230929-1505.zip

Well the parity sync is at 10 % now so it seems to be moving along. But disk1 is showing tons of errors. how should I proceed once the parity sync is complete? both of my cards are the ones below. what would your recommendation be in regards to the cards. any way to determine if it is the card? can I still have docker enabled during a parity sync to watch Plex? I currently have it disabled. 9207-8i PCIE3.0 6Gbps HBA LSI FW:P20 IT Mode ZFS FreeNAS unRAID 2* SFF-8087 US

I checked all cables and reseated both of my HBA cards. Currently on a 2nd try at running a parity sync the first time it stooped but its now showing disk1 is also having errors. am I in danger of losing data? no sure how to proceed. plexserver-diagnostics-20230929-0951.zip

So I shutdown the server and swapped the cables and now I can actually rebuild the drive. Yesterday it would not rebuild it was just running a check.

Only power cable or data cable as well?

3rd time this happens to DIsk1 twice with a previous drive and now with a drive that has less than a week in the system. its rebuilding now. just wondering what's causing it plexserver-diagnostics-20230911-2127.zip

They share the same power cable but so do all of the rest of the drives. I powered off the server and made sure the power cables were firmly pressed in all the way. Powered back on and started the rebuild process and it worked. I did add a drive the other day so I guess I could have loosened up a cable maybe..