Shadey1

Just wanted to say thanks again, just rebuilding parity but it looks like it's going well. Next thing on the pad is the reiserFS issues, but at least I have a while to sort that!

Ah thank you, that makes sense, I've ordered a drive and I'll get that running asap Typical that it dies the second I buy a new one.

Thank you! So am I right in thinking then that: Step 1 is take out the replacement drive since parity failed. Step 2 replace the parity drive Step 3 New drive to expand space And thank you again for helping, I find I don't have to think about my server for so long that when I do I question all the basics again!

WDC_WD60EFRX-68L0BN1_WD-WX21DC74D05N-20230713-2207.txtWell it jumped from 20% to complete really quickly. Took 90-120 mins Staring at it, I've realised I don't know how to interpret that at all these days!

Cool, I'm running the long smart test on the parity drive now. I'll report back in about 12 hours I guess! Thank you

Finished while I was at work.

Yeah it's sat here, it hadn't failed I just needed more space

That's me being dumb, I thought I had. Sorry about that! wintermute-diagnostics-20230712-0631.zip

I need some help please! Parity ran Sunday or Monday night, and was fine 0 errors. I then replaced a small (and old 13y+ drive) Tuesday, let unraid rebuild and saw this when I checked in this morning. I had some loose cables when I first booted back up, reseated them all and added the drive to the array. That's a lot of errors! WDC_WD60EFRX-68L0BN1_WD-WX21DC74D05N-20230712-0631 parity (sdc).txt syslog.txt

I realise this might be the dumbest question yet...but where do I run the MSR script! open a console? Stick it in extra commands? I got about an extra 500H/s just by running in privileged so I want to see what this ryzen can do 🤪 EDIT: I've installed user scripts, set the query and run it. Restarted the docker image, MSR not set Rebooted a few times and tried it, still nothing. EDIT EDIT: Dumb dumb here just reread the script, it'll show as not loading but will. I have the exact same Hash rate 🤦‍♂️ After some digging at https://monerobenchmarks.info/index.php It's doing about the best it can! Whoop

Very useful! Thank you @ChatNoir I switched it out before seeing this and I've had 0 issues since. I went with a https://www.amazon.co.uk/gp/product/B08J2PK1HF/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1 IO Crest 4 Port SATA III PCI-e 3.0 x1 Card Non-Raid with Low Profile Bracket ASMedia 1064

I'm 90% certain I know what the issue is now as it's got worse and worse at doing this since I updated unraid a few months back, and since the most recent update it's nearly constant. My marvell Sata PCIe card is either dying or just not compatible. The wiki (in it's own words) is out of date but basically avoid marvell cards for Unraid 6.x Time to switch it out

I missed this response at the time! I am pretty sure I picked a supported one, but now you have me wondering as it's done it again lol

Just incase anyone else gets a similar issue this has twice since this post. Both in the last 3 months. The first just dropped while watching something streaming from it, and then after looking at the notes I spun down and it lost the second. A bunch of restarts, removing and adding drives until it could see them both again and it's fixed. I'm certain after a restart/power hiccup it 'loses' the sata card so I'll look to replace that in the near future!

Cool I'll try that thanks, It's a bit of a mess in there so to even get 1 out might take a bit of effort. I'll spend some time on it. Next time 8 port Mobo instead I think

And as if by magic: I'll change it to solved, I'm starting to think the sata card might be a bit screwy

So I've had a look in the bios, the full ID string isn't there, but thankfully the 2 'failed' ones are pretty obviously different IDs, Boot option 8 and 9 which might be on a PCIe SATA card.

Firstly I've made this issue myself. I'm acutely aware I am a twit 🤦‍♂️ So over the past few weeks, we've had cable issues, eventually, they come out to replace the modem/router combo and reconnect us to the exchange, tweak the power and get us back into our usual service but the wifi range is shocking. I think 'screw this, I'm off to buy a better router' It'll solve some other issues, like the unraid box being in the study and it connects over wifi, along with the wifi being flakey and slow. So far so good, the new router in, but it can't see the unraid box, I can't //tower or IP it. I stupidly hard power off a few times, and reboot thinking it was the unraid box before I thought to check that the router could see the tower. I left it a good few days before trying again to work it out. This morning I've sorted the subnets out, I can get to //tower, and I'm greeted with this: Panic sets in. My idea was to start it without the disks, turn it off and add them back in, but I can't since 2 are down...but I can't due to the warning: 'Too many wrong and/or missing disks!' Now I could believe the 1TB might've failed but the 4TB is a few months old, sure it could've failed but I've had unraid lose a drive before with power cuts, and readded it fine with it lasting for years after. I've tried digging around a bit and it looks like new config might be my answer but I wanted to ask the experts and see if anyone had any thoughts before I pulled that trigger! Other than that I am stumped! Thank you in advance.

It failed after about 30 mins, I'll try again and if not I'll order another. Left it doing a parity rebuild while we were away and it's been fine for over a day. Must've been the drive dying!

So my parity dropped last night again, nothing other than this I pulled from the quick log function in unraid as it was after I hit reboot that I noticed the issue! unRAID Parity disk error: 07-08-2018 22:46 Alert [WINTERMUTE] - Parity disk in error state (disk dsbl) WDC_WD60EFRX-68MYMN1_WD-WX51D6427226 (sdc) Aug 7 23:03:24 Wintermute kernel: md: disk0 write error, sector=4577544704 Aug 7 23:03:24 Wintermute kernel: md: disk0 write error, sector=4577544712 Aug 7 23:03:24 Wintermute kernel: md: disk0 write error, sector=4577544720 Aug 7 23:03:24 Wintermute kernel: md: disk0 write error, sector=4577544728 Aug 7 23:03:24 Wintermute kernel: md: disk0 write error, sector=4577544736 Aug 7 23:03:24 Wintermute kernel: md: disk0 write error, sector=4577544744 Aug 7 23:03:24 Wintermute kernel: md: disk0 write error, sector=4577544752 Aug 7 23:03:24 Wintermute kernel: md: disk0 write error, sector=4577544760 Aug 7 23:03:24 Wintermute kernel: md: disk0 write error, sector=4577544768 Aug 7 23:03:24 Wintermute kernel: md: disk0 write error, sector=4577544776 Aug 7 23:03:24 Wintermute kernel: md: disk0 write error, sector=4577544784 Guess I'll re-seat the parity again, and see when it dc's but I'm running out of ideas!

Looking good so far! Now to figure out the stuttering that's started on kodi on windows and rpi3 boxes in the past week or so! Can use VLC fine... EDIT: Wifi switch needed restarting... lol

I hope so! Thanks for your help, I'll let you know how it pans out!

It failed once mid parity after just reseating the connections so I took out the sata data cable and replaced it and used a different power cable off another multicable. Be back in 2 days nearly with some more results but here is the SMART while it's 10 minutes into a day day parity check. wintermute-smart-20180804-1154.zip

I'll reseat and redo parity again then run SMART and post back. 2+ days I suspect

Hey all, I bit the bullet last month and upgraded, switching out my old mobo, CPU, PSU and RAM. Updated all the software and for the last two weeks or so I keep seeing the parity fail. I can't work out why, it doesn't help that when I unmount it, and re-add it that it takes 2 days to rebuild parity. It died last night/morning at 06:34 when I checked the server tonight, it was working fine but a kodi box couldn't stream so I wanted to check it wasn't down and that's when I found it tonight. I've attached the full diagnostic, from just before the registered loss at 06:34 but pulled the extract below as it covers the core time, everything previous is an hour before. Looks like preclear is throwing some errors, but I can't imagine that's killing the parity surely? I've even switched sata ports on the mobo last time and that didn't save it. 2 drives are on an expansion card, the parity was one of these until I switched it around. Part of me wonders if it's the sata port card, it was off the old machine, it worked fine then but the errors imply it failed, but I don't know much about them! Thanks in advance! wintermute-diagnostics-20180725-2230.zip