bjreich

Quick update. Disk 2 does still have filesystem issues after it's rebuild, its online but files complain about being read-only and have permissions issues. Unfortunately, reiserfsck recommends a --rebuild-tree to fix some of the issues. That is still running now, so we'll see. I have the old Disk 2 safe and sound in case I need to repair it and compare results. Many of the issues with the current Disk 2 may be from differences in Parity rather part of the initial filesystem issue it had.

Well it's not rebuilding my parity (great) and it is rebuilding disk 2 (even better), so far so good. Thank you VERY much for your help Johnnie Black, its definitely appreciated. I'm just having a look through the emulated data now. I'll let you know what the end result is when its done.

Just waiting for the array to mount now and see what happens. Very nerve wracking ignoring all the warnings that I'm doing the opposite of what I want. If disk 2 is lost at least I have the old one to put into a caddy, filesystem check and hopefully recover data from it.

I'm about to perform the process above fingers crossed. Luckily, disk 6 is 100% full so there shouldn't have been even any emulated writes to it. When I upgrade my discs next I'm going to spread the data out so I have no more than 90-95% full per disk. Two weeks was a long time, I'm kicking myself for not immediately dealing with it. My unraid box is just SO stable and problem free I became too complacent. Lesson learnt!

No I don't have notifications setup, which is bad bad bad (I'm an IT guy). The array was running for about two weeks I ( I was busy and totally forgot about it), but the day before the incident I logged in and saw the Dashboard still said missing, the next day Disk 2 had an error and Disk 6 changed to unassigned. 1 day since then.

Thanks for your help Johnnie, I'll give that a go tomorrow afternoon when I have the replacement disk in hand. That's sounds like a promising process because I get to keep the old disk 2 untouched in case I need to try and do recovery on it later. Do you mind if I ask what the mdcmd set invalidslot 2 29 does? It sounds like it tells the unraid layer to invalidate and rebuild disk 2 but what about the "29" part? Regardless of what happens I'll let everyone know how I go.

Hi everyone, I've found myself in a potential data loss situation and I'd appreciate some expert help before I do anything that might make it worse. I had a drive (Disk 6) go missing on me after moving my unraid box due to a cable that came off. Regrettably I didn't immediately deal with the situation because then a real disk fault occurred on Disk 2 (unrecoverable write followed by unmountable filesystem declaration by unraid). The moment that happened Disk6 went from missing to unassigned (but parity hasn't been re-checked since that happened so it is still calculated with Disk 6 in the array). My plan was to use the "Trust my array" procedure to re-add Disk 6 since I know the parity is in-line with it being there and being just a cabling issue that occurred while the system was turned off, I know the data hasn't changed and that the parity is still calculated with it being part of the array. Then I was going to replace Disk 2 and let the parity rebuild it. But if I try to remove the parity, I can't then start my array to make it forget the parity (too many missing disks) so I can re-add with "My parity is valid" ticked. If I just try to re-add Disk 6, it's detected as a new disk even though I'm fairly certain its fine. I didn't start my array with any of these experimented changes and put everything back the way it was - so the parity drive is still assigned and disk 6 still unassigned, the array is stopped (I don't let it auto-start so it always starts stopped). I've attached my diagnostics, I'm hoping someone is able to guide me down the safest path- if there is one. TLDR Disk 2 is faulty, Disk 6 is unassigned, Parity should still be valid except for the failed write to Disk 2 that started this scenerio unfolding, Unraid reports too many missing disks to start the array without the parity drive. Thanks in advance for any help anyone can provide. storage-diagnostics-20180926-1800.zip

Hi, I'd also appreciate a likely release date for beta7. It sounds like everything I need to progress with my new unraid build, especially if it has the latest kernel included. I have all my hardware, including my 780ti for gpu passthrough so I'm excitedly awaiting the next beta. I could proceed with Fedora or Arch with unraid in a VM, but really that's an extra OS layer, when I could be using unraid as my hypervisor OS.

I just wanted to say thanks to the LT team for the direction they are taking the product. From some all of the negative comments that have been made recently you would think that Unraid was a mess that no one in their right mind should use - which is absolutely not correct. I'm an IT professional of 22 years, IT Manager of 10 and Unraid user of just over 4 years. I've been running an array of 12 disks since the start (up to 25 Tb now) and in the time I've been using Unraid I've experienced ZERO data loss. In that time I've lost 6 disks and Unraid has saved me every time. And more importantly Unraid did this with almost no effort whatsoever, which appeals to the side of me that feels I already do enough IT work at work. I currently have a gaming PC, HTPC, Unraid server running SAB, CouchPotato, AirHD, Plex and Sickbeard, and my son is now old enough to need a PC to game with me on, as well. Over the last couple months I've researched, researched, and then researched some more before carefully choosing a set of hardware to use unraid to virtualise them all onto. When your next beta is released it should be at the stage for me to KVM my various PC's under unraid with SAB and all my other services bundled into dockers, which is the sort of efficiency and service isolation my IT mind loves. Helping users select the correct hardware for making this all work will be key to people having a good experience with all the virtualisation technology. I suggest picking a hardware set that you are using (that is also commonly available) and documenting that as a template for less experienced users to copy and have a seamless experience with. Thanks again for all your efforts and direction, Unraid is getting even better with every new beta.