mathomas3

Also there is this error... Jul 29 12:10:01 Tower kernel: Buffer I/O error on dev md11, logical block 1953506608, async page read Jul 29 12:10:01 Tower kernel: Buffer I/O error on dev md8, logical block 1953522944, async page read Jul 29 12:10:01 Tower kernel: Buffer I/O error on dev md8, logical block 1953522945, async page read Jul 29 12:10:01 Tower kernel: Buffer I/O error on dev md8, logical block 1953522946, async page read Jul 29 12:10:01 Tower kernel: Buffer I/O error on dev md8, logical block 1953522947, async page read Jul 29 12:10:01 Tower kernel: Buffer I/O error on dev md8, logical block 1953522948, async page read Jul 29 12:10:01 Tower kernel: Buffer I/O error on dev md8, logical block 1953522949, async page read Jul 29 12:10:01 Tower kernel: Buffer I/O error on dev md8, logical block 1953522950, async page read Jul 29 12:10:01 Tower kernel: Buffer I/O error on dev md8, logical block 1953522951, async page read Jul 29 12:10:01 Tower kernel: Buffer I/O error on dev md6, logical block 1953506608, async page read Jul 29 12:10:01 Tower kernel: blk_update_request: I/O error, dev loop2, sector 41942912 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0

Hello all, I think I had a little power flick or something, but I noticed that my server's fans starting spinning a little bit quicker for a second which prompted me to check the server. After pulling up the page disk 8 is red balled and all ther other disks have 300-400ish errors. Wanting to prevent further errors I tried to stop the array and that's where it's stuck. ' lsof | grep /mnt lsof: WARNING: can't stat() xfs file system /mnt/disk8 Output information may be incomplete. ' Before any of this happened I suspected that disk 10 was on the way out due to 114 read errors that happened yesterday, though an extended SMART diag came back good... And now the parity drive is red balled... HELP! tower-diagnostics-20220729-1405.zip

I currently run 8tb drives... and from the start I have always used fill-up with 100gb min free space... it's been working well for me... just to give you an example

After reseating the card validating everything was plugged in... it still didnt work... unless someone knows about how these cards work... perhaps it requires a monitor to be connected at start? The card I bought was from dell at T400 at this point I think it's a dead card... thoughts?

In looking into the IOMMU groups... unless im mistaken... I am not seeing the T400... sure sure how that is possible... ill double check the hardware physically...

Hello @ich777 I just got in the T400 and plugged it in... Problem is that we have driver issues again... I did confirm that the 515.57 drivers should be used via NVIDIA support page tower-diagnostics-20220702-1555.zip

That and also I would run it without your VMs being powered on... Default bios settings and Unraid (without VMs) Run it like this for a day or so. In order to get MacOS to run on this hardware, I would assume that you had to make a number of modifications to get it to run, could you explain what changes those might have been

As a first thing that I would do... reset the bios to factory settings... this feels like a power save setting of sorts... When the system does become unresponsive have tried to access the console physically?

What is this 'server'?? you have 2 500gb m.2 drives attached... This is a gaming rig more then anything... If you are using unraid as the host OS... why?

I think I followed this parity/data swap guide that Jona is talking about years ago... and it worked at the time... but again that was a long time ago when I was using 6tb drives

Diags for me takes a few minutes... depending on the logs and the number of drives and dockers/plugins... that number will vary... but please give them a chance to complete...

Reading the notes of the guide... You are Correct! (even after using this software for nearly 10 years... I still have much to learn) So OP... Please lean to Jona's suggestion with the swap guide... As a side question Jona... would it be possible for OP to build a second parity drive(using the 8tb drive) and then rebuild the failed data drive with a 8tb one?

While this could work... wouldn't the safest way forward be replacing the failed drive first and then replacing the parity drive? While this guide suggest 2 steps in one... doing each step separately be the safer option?

IMO follow this guide first... and then do the parity swap... https://wiki.unraid.net/Replacing_a_Data_Drive to put things simply... shut down the array... replace the failed drive... power on the machine... stop the array... select the new data drive in place of the failed drive... start the array... this will rebuild the failed drive(this will take around 12h or more)... after that's done... then and only then would i proceed with the parity drive replacement... But again... BEFORE doing anything please read the guides and be sure that you have all the information and questions(answered) before proceeding... and also echoing Jona attaching Diags would help us understand what is happening, so that we can best help you

I would echo what Jona says here... Replace the failed drive first and then replace the parity drive second

I cant answer your question... but Congrads, you are one of the few that read the manual(s) before doing updates. Have a virtual beer on me

If I could ask... are you planning on using larger disks down the road? I would suggest moving to them sooner rather then later IMO. I at one time had a good number of 3tb and 5tb drives(around 8 at the time) all of them have died over time except for 2 5tb drives... These were mostly green and red drives, Since then I have moved to only 8tb enterprise drives, with a mixed bag of new and used drives. None of these drives have failed as of yet and im up to 14 of those... So to sum it up... I would suggest 8tb enterprise drives the next time you are in the market

My thinking is that when the parity check is running, the power draw is at it's highest, thus drawing too much power. if your PSU is less then 450 watts I would suggest getting a larger one... but let us know what hardware you have

I havent looked at the logs... but kinda sounds like a PSU issue... what hardware are you using?

Just did the update and downloaded the recommended driver and it works great! Thanks!

Im always a little squeamish when it comes to updates and new features... I like to sit back and let the bugs get hashed out before updating... perhaps it's time

How would I got about using this specific driver? The current list of drivers listed in the plugin doesnt list it. I also put in an order for the graphics card that you recommended! Thanks again for the help!

Diag are attached tower-diagnostics-20220624-0545.zip

Hello all once again... I have just built a new system to try hardware transcoding once again... before I was not able to because of IOMMU groupings... So this build is a GeForce GT 710 2gb running on a HP ProLiant DL360 G7 server... I am able to get video out via the graphics card and everything works well... Just not nvidia graphics... When running nvidia-smi I am getting "NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running." even when trying different drivers... also have rebooted, downloaded drivers now, and restarted docker... I have good IOMMU groupings to include " IOMMU group 34:[10de:128b] 09:00.0 VGA compatible controller: NVIDIA Corporation GK208B [GeForce GT 710] (rev a1) [10de:0e0f] 09:00.1 Audio device: NVIDIA Corporation GK208 HDMI/DP Audio Controller (rev a1)" Suggestions? Also ich777 I want to tip my hat to you for your continued support for everyone here... I would be happy to buy you a beer should we ever cross paths

If pure speed is what your looking for, TrueNAS might be worth looking into... it's more of a enterprise setup with a number of limitations... The key one for me is the inability to add disks to the array... I have been using UnRaid for around 10 years now and it has been a very solid system that has expanded a lot over time. My one tip for you is to consider a larger case then you currently need... I started with a 8 bay case and migrated that over to a system that could hold 18 drives and just recently decided to move to full-on enterprise (recycled) hardware using a DAS that can hold 28 drives... Something to consider Oh and label your drives before putting them into your case... makes finding a failed drive ALOT easier!