Gsusking2

Hello, last night i believe one of my SSDs in my cache pool died. I mistakenly shutdown before grabbing the logs. I have attached logs after a scrub and reboot. Would just replacing the cache drive just trigger a rebuild off the mirrored drive? Any insight would be amazing. Thanks you! tower-diagnostics-20250529-1006.zip

Hey man, Im having a similar problem with a failed disk and all these errors in 7.0.0 RC1 should i just sacrifice the disk, already removed but being emulated.

Hey, im currently running 7 rc1 and i am having the same problem when it comes to assigning dev/dri/ to my plex container (linux-Server io). do you think this is a container problem or a greater problem? Figured it out forgot the initial forward slash. Apologies for this, its late

I have attached Diagnostics here, Im not sure what is going wrong. tower-diagnostics-20240704-2104.zip

Thanks, I'm just gonna buy a new disk and hope for the best and add 22 to the array after. Thank you again Jorge, If you're ever in Canada let me know ill hook you up. in the mean time ill buy you a beer through your link. You are always so helpful, patient and kind in these situations. You're a true gem

Thank you Jorge! Can i use the 10tb that is in the array? am i able to remove it from slot 22 and make it new disk 6? Let me know if i have to reset the config or something to make it happen.

Disk 6 is still showing a red x when i start the array after the xfs file system check. Edit * attached diagnostics tower-diagnostics-20240618-1500.zip

My mistake here is the output. I will continue with the steps described. and post again. Check File System Output - Disk 6.rar

Thank you, I have done above here is the output from the file system check Check File System Output - Disk 6.rar

Hello, I followed the steps above and this is the diag output tower-diagnostics-20240618-1326.zip

Ok, lets give it a shot. If you could give me a quick guide on what to do i have done stuff like this before with my server (see post history) and im very capable of following instructions. Background: disk 22 was being added to the array and had just finished its preclear. When i went to format it via the GUI, it was hanging and not responding, i then initialized a restart of the server. as i clicked the button i noticed the red x on drive 2 and parity. hence why i dont have the original diags

please see result of extended test of disk 6 tower-smart-20240618-1137.zip

Thank you, will update after the extended test.

Hi Jorge, After starting the array i now have another disk that threw an error and is showing a non supported file system Please find attached diags, tower-diagnostics-20240618-1102.zip

Thank you for the reply Jorge, when i remove the disk (sdc), i am unable to start my array. I have posted the Diag after boot with removed (sdc). Let me know if you need any other info. tower-diagnostics-20240618-0953.zip

Hello, I checked on my server today and had a red x on a data disk and on a Parity drive. They both showed the same error count, so i assume some CRC power error threw them both out of wack. My question is how do I proceed, Do i replace the data disk and start rebuild? do i repair the disk (XFS) and then replace the parity? Is it possible to just reseat the 2 disks and see if they throw errors? I had to reboot before i could get the diags, here are the diags after a restart. tower-diagnostics-20240617-1617.zip

did you find a solution to this bug? i am experiencing the same thing. It only seems to happen when using the domain name. but this is an issue for me as i travel a lot.

Thank you, That worked. Now disk 1 is constantly throwing CRC errors. Im gonna try to reseat it and put it into my JBOD on a different power supply etc. If this doesnt work. How do a move forward with 2 disks needing a rebuild and disk 1 being a jerk.

I have since stopped the rebuild and restarted. here are the diagnostics after restarting after what happened above. tower-diagnostics-20230331-1426.zip

Ok so i got to the step where i stop the array unassigned the disks, then restart the array in normal mode (it says Disks missing please replace asap). I stop the array reassigned them. and now its doing a data rebuild and disk 1 is immediately throwing errors. and its saying disk 5 and 14 are unmountable file system or no file system. when i start in maintenance mode i am no longer able to check the file system on these disks.

Ok i would be interested in this information. (the re-enable of disk 1) If disks were to keep dropping could i just remove and replace said disks loose a lot of data and keep going? I really appreciate your help with this. Let me know if there is a link i can use to buy you a beer.

here is the diagnostics of 3 emulated disks. 1 5 14 1 is a red X 5 and 14 each have the Triangle exclamation point. In this case what do i do. Data preservation on these disks isn't crucial (all replaceable data) tower-diagnostics-20230331-1238.zip

ok so basically disk 1 has become unmountable now. So currently i have disk 1 - 5 - 14 down. I started the array it started the rebuild process and now im not able to access my webgui. I shut down the server blind and will post new diagonostics IF anyone needs to shut down their server blind 1 Plug in a keyboard 2 put in root (enter) password (enter) 3 enter command "shutdown -h now"

in this scenario, if im unable to rebuild because of another disk failing. is the array toast? i have 2 parity drives. Should i run the sync (data rebuild) in maintenance mode?

Ok this makes sense. During rebuild a random disk will start throwing read errors and will completely kibosh the rebuild process. first it was disk 8 now its disk 1.