SKAntoniou

Sorry been a long time, Just want to give an update. So it was a hardware issue as you guessed. Replaced Motherboard, CPU, RAM and PSU and used that stuff for a normal computer. Disk 2 was still acting weird so did this (as suggested by you guys): Booted in Maintenance mode, used xfs_repair -v /dev/md2, log was inconsistent used xfs_repair -L /dev/md2, fixed used xfs_repair -v /dev/md2 to check all good stopped array and started normally and everything is back to normal Thanks for the help. Was very useful.

nice, yeh sadly don't have another cpu + motherboard, going to be moving to a thread ripper build in the future so might buy them soon so I can just try get it to work.

ordered a new sas card because fuck it, already wasted a bunch of money, will update when this comes and doesn't work.

thanks for the tip, I tried that but now I am back to crashing. I don't think this is a hardware problem, I have changed my PSU and motherboard, Tested my Ram on memtest for days, under clocked my cpu and swapped the cables for my sas card with motherboard ones and nothing is working. From the brief time it wasn't crashing, I worked out it is mainly crashing trying to mount hard drives which end up being unmountable (or at least thats my best guess). It is really annoying. I have probably lost all my data right?

thanks unbaud-diagnostics-20210412-1618.zip

Ok so got new power supply and put it in, stopped crashes when I add parity drives back to array. Only problem now is since swapping power supply 2 drives are showing up a unmountable. One drive was showing up as unmountable but since adding parity drives another one decided it was unmountable. One drive is showing up with a Red Cross (the new one that won't mount) other is green but isn't mountable. Any suggestions?

oh alright, that sucks. The power supply with this little stuff in the build is a bit overkill, don't know if that is broken. Cpu might be a pain to check but il try run some stress tests on it, if not under clock it a bit.

thanks il try remember that.

ok was close, added parity drives and now it crashes when I try parity sync it, any clues?

Oh my god, everything works now, xfs_repair -v /dev/sdh1 fixed it. thank you for continued support JorgeB, literally couldn't do it without you. now just going to add back parity disk and everything should be okay. weird had to make a new array then xfs repair the drive after it to fix it but all is sorted, thank you.

the log showed this Apr 7 16:09:16 unBaud kernel: XFS (sdh1): Corruption warning: Metadata has LSN (2:769339) ahead of current LSN (1:0). Please unmount and run xfs_repair (>= v4.3) to resolve. Apr 7 16:09:16 unBaud kernel: XFS (sdh1): log mount/recovery failed: error -22 Apr 7 16:09:16 unBaud kernel: XFS (sdh1): log mount failed Apr 7 16:09:16 unBaud unassigned.devices: Mount of '/dev/sdh1' failed. Error message: mount: /mnt/disks/ST4000DM004-2CV104_ZFN2Z9C3: wrong fs type, bad option, bad superblock on /dev/sdh1, missing codepage or helper program, or other error.

So that actually worked pretty well, Started with one drive formatted it, (one that was never in the array). worked Then unplugged that drive, moved to putting old drives back in worked out well but dumb me didn't take a picture of what drive was where before starting this process. So out of my 7 drives ( 2 parity) 4 are in perfectly but 3 drives show as unmountable. 2 I am guessing are because they were parity drives but the one is the weird one. The drive log I posted before about disk 4 shows what drive was meant to be in the array but sadly is showing unmountable, does this mean I lost everything on that drive? any option to save that?

thanks

if I use a different drive to start an array to test if it works, can I later bring all the drives back and restore my original array?

thanks, I just started it in maintenance mode, and was looking at drive logs, spun down a disc and then spun it up and crashed soon after. I am not getting instant crashes though when I start normally, takes like 20 seconds now until crash, some progress. Also all my plugins are gone, would that be a sign of anything? any chance my usb drive is failing? doesn't show that on the webui but who knows what's happening. I just installed community apps and common problems again to see if they show anything but sadly not. will keep trying things, thanks.

any suggestions would be great, really annoying at this point, would rather not lose all the stuff on it as it is the opposite reason of why I built this.

Replaced motherboard, took ages to get delivered. can start without gpu in it but still same issue as before. still returning old motherboard because the whole can't start without gpu in wasn't good.

still crashes when array starts up with gpu configuration. Motherboard or cpu must be faulty.

any* idea what is broken and what I should do?

So I have a feeling the integrated gpu on my cpu is dead, or cpu is dying or motherboard is dying. I don't know which but it has to be one of them. shorty after the tests the other day, my pc went from showing bios start up screen to not showing anything. When I took the gpus out and everything, still no bios screen. tried different hdmi, still nope. install one gpu and bios screen showed up. and idea what is broken and what I should do. I don't have a spare cpu to narrow it down anymore. my unraid was using my cpu gpu as webui interface so need that working for my system to work.

Hey, so at work on break. When I get home I am going to take out all stuff for VMs like graphics card, usb card etc and clean everything. Then reset motherboard because think something weird is happening with it. Then will have bare essentials installed only for array to test it properly. Will do loads of tests then, may update my bios so no worries if can’t you can’t reply tonight because might be late when I finished everything.

Don't know that was the most up to date diagnostics literally downloaded it right after it crashed. Every time I do something now something different happens, right before it crashes. new log from xfs repair on device 2. That is as far as it got. I dont really understand what is causing the crashes but I guess it doesn't get logged. Last diagnostics were right before I did this and il add the diagnostics from right after when I got it restarted. I start work early tomorrow so will be on earlier. Linux 4.19.107-Unraid. Last login: Wed Mar 17 19:20:45 +0000 2021 on /dev/pts/0. root@unBaud:~# xfs_repair -v /dev/md2 Phase 1 - find and verify superblock... - block cache size set to 3055776 entries Phase 2 - using internal log - zero log... totally zeroed log zero_log: head block 0 tail block 0 - scan filesystem freespace and inode maps... sb_fdblocks 14537429, counted 21352345 - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 bad CRC for inode 2170963486 bad CRC for inode 2170963486, will rewrite free inode 2170963486 contains errors, corrected - agno = 2 unbaud-diagnostics-20210317-1943.zip

new diagnostics unbaud-diagnostics-20210317-1923.zip

Ok so I don't understand, after doing the xfs -L, went back to array to start it. I stopped the array and was about to start it then disk 5 was missing plus a drive that was used for unassigned plugins. I rebooted the server and tried just starting not on safe mode, crashed. Start again in safe mode, disk 5 and unassigned device is there. don't know if the drives being missing for a brief moment is useful but that's what happened.

did at the bottom, log below, tried it again aswell new error, gonna try start the array as new things are happening. root@unBaud:~# xfs_repair -L /dev/md2 Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being destroyed because the -L option was used. xfs_repair: libxfs_device_zero write failed: Input/output error root@unBaud:~# xfs_repair -L /dev/md2 Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... totally zeroed log xfs_repair: libxfs_device_zero write failed: Input/output error root@unBaud:~#