crakhed

So I'm a casual unraid user for about 8yrs now. Current server is 50TB. No cache drive, 6xST8000DM004, 1 of which is the single parity, 2xWDC_WD40EZRZ, and a single 2TB Hitachi "deathstar" Deskstar (that will be replaced with another ST8000DM004 soon), running on an old recycled GA-MA790XT-UD4P board with a Phenom II X3 710 and 4GB DDR2. It runs great as a home media server and semi-dependable backup of non-critical stuff. Anyway, I say casual because I don't download directly to the server, my hoarded digital post-apocalyptic archive is very manicured and curated for personal use, so I don't need apps modifying anything, I don't convert/transcode any media that I add, and I don't even know how to effectively setup/utilize VMs for anything. I imagine something I use this passive server for might benefit from some kind of VM, but it's all greek to me. Now I've upgraded my main gaming desktop to a CrosshairVIII Hero/3950x and have my old CrosshairV FormulaZ/FX8350 to move over to the server. I've done a lot of reading here, googling, and duckduckgoing but haven't found the kind of specificity I need to feel comfortable just swapping boards in the server like last time. The last board in the server 4yrs ago was a P5QPro/Q9400 (legendary 12yr old mobo, I've had 5 of them and 4 are still running in gaming rigs btw including the old unraid base), and swapping in the current gigabyte board at the time was a 1hr cake walk since they were similar generations. Now that I have this significantly different-featured CV-FZ board, does anyone have any particular advice/warnings for setting up the bios to minimize setup time/headaches for the swap? I also have an OCZ Vertex4 128GB SSD and a Mushkin (trash?) Callisto 40GB SSD leftover from my desktop that I was was wondering if either or both would be useful in any way as cache drives. I basically just keep a pretty big archive of movies, tv, music, apps, and game isos on there and use plex to access video, and mediamonkey to stream music. Everything works great right now, just looking to boost write times when I move my downloaded stuff to the server from my desktop, and get rid of the little bit of 'lag' when my wife, the kids, and I are all accessing the server at once on rare occasions. Just wanna perk it up a bit, ya know? I know this was a lot to read, so thanks for taking the time, and thanks in advance for any ideas any of you might have. Let me know if you want screens or logs of current setup for reference.

Well it's a (Halloween?) miracle, and I have no idea why, but I got it to work. So I switched SATA cables with the parity drive on a whim, just to rule out bad cable/controller. Then I reconnected the physical disk1 and booted server. Of course, array had forgotten disk and now sees it as replacement. In maint. mode under unassigned devices, there is now a mount button and share toggle (maybe these only show for 'replacement' drives?). I totally expected to slam into a brick wall of failure, but being a glutton for punishment, I clicked mount. It ...mounts? Then I toggle share. Open explorer and there is it, a network share named after the drive serial. All data accessible. All 1.6tb is now backed up to this desktop and I'm about to flush the failed disk1 from the array and add a brand new 8tb and start migrating the other drives to xfs. Thanks for your help, folks. Lastly, is there any quicker method of fs conversion besides my plan to: add new 8tb as empty xfs disk1 dump rfs disk2 to disk1 (prolly thru midnight commander w/ PuTTY) format now empty disk2 to xfs repeat for rest of array?

So what are the best options for recovering the data? I have almost no experience with linux if that's required. Are there any windows apps that are capable of repairing/accessing it? There is irreplaceable stuff on there like family photo archives and whatnot. And of course, I was planning to add in another drive and start migrating each drive to xfs, but looks like I didn't start soon enough.

Yes, I did it through the webUI from the disk1 settings page. Should I maybe do it manually with the terminal html window, or even PuTTY? It is currently running in maintenance mode as in the image. The rest of the array though, when mounted, IS accessible and all shares appear properly except for disk1 shares/disk share are absent. Doesn't it usually say "Emulated" next to the warning/disk on the main tab?

I tried but it returns reiserfsck 3.6.27 Will read-only check consistency of the filesystem on /dev/md1 Will put log info to 'stdout' Failed to open the device '/dev/md1': Unknown code er3k 127 and if it's being emulated, it's still not appearing in explorer.

Checked bios, it's still configured properly. I'm glad because I know undoing that specific 'corruption' is a pain. One thing I'm noticing is that with the physical disk unplugged, the webUI still has 'Unmountable disk present: Disk 1 • ()' under array operation with the checkbox and option to format. Is that normal?

Another thought I just remembered while reading other related posts, my motherboard DOES have that copy-bios-to-disk backup feature, but I carefully made sure to disable that when I migrated everything to this new setup and haven't had a prob, but it's a headless box and I'm wondering if I should grab a monitor/keyboard and boot to bios to make sure the setting didn't 'reset' when the power originally went out. Would that setting suddenly being enabled on board cause this kind of behavior from the drive if the board modified it out of the array with its bios backup? Just a thought.

oops forgot diag babel-diagnostics-20191005-0930.zip

Unplugged physical drive, started normal mode, no emulation. Stopped and started maint. mode, still no emulation, same error on filesystem check from webUI.

So I'm not sure if it was caused by a power outage (we had one a few days before I noticed any problems), but suddenly disk1 wouldn't let me write to it. I checked the webUI and saw that disk1 was being emulated (should've gotten the data off it and replaced with a spare while it was 'accessible' but I didn't). After poking around other forum suggestions and trying the filesystem check from the webUI in maintenance mode (which returned "Failed to open the device '/dev/md1': Unknown code er3k 127"), I rebooted the server (the old off/on again trope) the disk now shows "unmountable - no file system" with no emulation or samba access. This is the original first disk I installed when I first started using unraid 7yrs ago, and has some pretty important stuff on it. It's old, but SMART diag seems fine (no errors, but then a lot of it is greek to me). I have a few working spares from when I upgraded a few of the newer, smaller disks; is there any way to get it at least back to 'emulated' so I can retrieve data and just flush the disk or replace it? I'm assuming that since the array is starting, that the data is at least backed up in the parity, but I also gleaned from reading that just swapping in a new disk will just replace the corruption as-is to the new disk. Again, the physical disk is of little consequence and will definitely be replaced after all this, but I really need the data if there's any way to get at it. Thanks in advance, gurus. babel-diagnostics-20191005-0905.zip

Just wanted to update, I went on a quest. I dug up a cool program called Trid http://mark0.net/soft-trid-e.html for identifying and renaming (adding a coherent extension) all the loose files. Copy-pasta'd some automated script commands and am happy to report that it is chugging along nicely at least identifying mp3s. And it seems that the id3 tags are preserved so, thanks to a super customized version of Mediamonkey and an archive index to check against, I'll be able to reorganize them properly with a few scripts. Thanks a lot again, this was almost worth the learning experience.

Well the drive is accessible now, although EVERYTHING on it was relegated to the lost+found folder. Some of it is recoverable, but most of this drive was a big chunk of my music collection, and it's been almost completely thrashed. Also, I'm seeing 3 undeletable files that are impossible... 1 file showing a size of 300 petabytes, and 2 showing 900 petabytes, which alone is 1 million times the size of the drive, lol. Should I run a parity check with it like that? Or should I salvage the stuff I can and reset/preclear/reassign this drive as new? Maybe Tom has unlocked the ultimate file compression? I'll just proceed with sorting through the other 18,000 unidentified files/folders. At least a few 2nd level directories were preserved, but not many. I've looked around here a bit, are there any good tools for at least identifying some of this stuff? Anyway, I guess this can be tagged as solved. Thanks a lot for the help. I definitely learned my lesson about trying to fix it myself, next time I'll be quicker at asking for help.

It's like I don't have permission to the disk at all, none of the user shares appear on disk2 ONLY the lost+found, which I can't access. The rest of the server is fully functional at disk level, but each top level share folder is still missing the files that are specifically on disk2. So do I run newperms /mnt/disk2 via telnet on disk2, or do I run the script on the whole array through the webui button?

Well I just got up to get ready for work and it finished. Stopped/started server and it mounts proper now. However, when I browse to \\TOWER\disk2 the only directory is lost+found, and I get a permissions error trying to open it. I has a size of 0 (probably due to the permission error), even though the webui shows disk2 as 90% full . Should I reboot? Fix permissions? I did notice a lot of what looked like permission corrections/adjustments during the --rebuild-tree process.

Running now, about 10-12 hours to go I'm guessing. I work 11p-11a tonight, so it'll be tmrw afternoon before I check back. Thanks again, guys.