dogfluffy

Ok rebuild is complete. It looks like I have disk13 recovered. It looks like there may be corruption as I can't view disk13 it just hangs up and times out eventually. Also I have a lost+found of 4.26 TB on disk 9. Disk10 unformatted and disk11 is 3TB blank. It also appears my shares are broken. Quite a mess all in all. Hmm yes now the console is fast scrolling inode locked errors over and over. Should I stop the array and shut it down?

OK, I believe I followed that excellent explanation. Now I still don't know how to get myself out of the mess I created, but hopefully you have an answer for that as well. I was chasing a random red ball disk error and thought unraid functioned differently, so if the repair command hadn't made any changes, (which I also logically should have ran read only) then re-assigned disk10 would have been OK? It probably doesn't matter ultimately, but I'm learning tons about how this works. Do you think the original disk10 file bits are still recoverable? Thanks for all your help with my chaos! I felt like Walter White chasing the fly on this one... so I was trying crazy things, in retrospect. I don't have to try hard to sound like an idiot. I'm super curious to see what disk13 contains, and how my 2 spare disks fit into the complete data set. I probably don't deserve to get lucky and lose nothing.

Lol yeah it's @ 8% now, but moving nicely. I was just trying to wrap my mind around the parity being out of sync, and how you could know what files it was actually synced to. Probably academic, rebuild and copy the data is just faster I assume.

No, I don't believe I ran reiserfsck on disk10...but I can't be certain. Yesterday I did unassign disk10, then in unMENU I mounted and tried to browse it, which showed blank. I re-assigned disk10 before assigning disk13 and rebuilding this morning. I'm not sure I'm using the optimal method to try and view files. I was wondering whether you can view what files are on the parity drive or whether it's just abstract data.

Yes it's terminology. When I say formatted or wiped, I mean I would suffer data loss on the disk during the data rebuild. I will have to see what gets written to disk 13 after the rebuild. I have an empty disk 11 and an unformatted disk 10, also empty. I have 2 disks with data, hopefully matching.

I already swapped the disk 13 for the blank disk and added it to the array so it is rebuilding now. You said during the rebuild of disk 13 the data would be formatted off or wiped. I don't understand what is the difference between emulated and the original. I have both original disks 10 and 13...I believe. I at least have 2 disks with data on them and 2 that are blank and now both added to the array. Disk 10 is added but still unformatted file system.

Ok gotcha. Yes, the terminology makes explaining this a bit complicated. So I do need to pull my case installed disk13 with data on it and replace it with the blank "disk 13" then assign it and start the array so it can rebuild. I believe I'm up to speed now, except for understanding the parity right now. Meaning how do I figure what "parity" will do to disk 13 before it happens? You seem to know it will start formatting and disk13 will be erased and wind up blank, and I don't understand why exactly. It might be academic however, if I swap these disks and replace 13 and 10, I still think I have the data that used to exist in parity on the original disks 13 and 10. I suppose this highlights my misunderstanding because I would have thought a 13 with data would simply replace to the back to the parity drive with no data loss or formatting. It's a little confusing what holds the master record of files or parity. I've got work to do and I'm going to try and label and organize these for the future. Thanks.

OK I think I am very nearly up to speed with how this works, finally. Luckily you didn't run out of clubs to beat it into me with! So I couldn't mount or even file system check disk 10, basically says it's missing a superblock. I also believe I found the missing disk 10, labeled it and set it aside. It sounds like the only real question is whether to shut down and yank the assigned WDC disk 10, replace it with my labeled spare disk 10 and restart with this disk 13, once it's back added to the array. Maybe a question of sequence, or just use the one installed in the case already and copy the spare drive data after it rebuilds and adds a superblock? Anyway...I think I have a handle on my chaos now. I might print up some fancy numbers to mark these for easy access in the morning before I put this all back to sleep. Thanks for all the help, I was misunderstanding how it worked and you cleared that up nicely.

OK great. I am completely lost, although I think I followed your explanation. I was concerned if I add this disk 13, that during the rebuild it might blank the data already on it. I suppose I need to try and index these disks as best I can to piece together what I have first. Then I can try to read the existing unraid drives, find the missing data to make sure it's preserved and added later. I had been thinking I could find and add the original disk back into the array, as opposed to just copying the data back afterward. I figured out how to mount and browse these in the Umenu file browser outside the array. I have 2 spare disks with data, the one installed in the case and ready to assign #13 has data. Another spare is blank. Another spare has different data than the first it appears at cursory glance. I think as long as starting with this disk installed doesn't delete anything, I found my missing data set...hopefully. Then I just need to make disk 10 browseable and copy to the blank disk I believe right? So basically what you were saying about adding the disk 13 wouldn't be destructive. I added a blank disk and it remained blank? I'm only confused about the parity being out of sync now, since I don't know what it missing once the array starts up. Thanks for all your help and I'll tackle this with fresh eyes in the morning. I guess I should unassign the blank disk to try to mount it, then re-assign it afterward.

I'm sitting here with 3 disks, none of which are currently added to the array. They all have been previously, at some point. I would like to attempt to ID these disks, to find their original spot in the array, if possible. It would need to be off the data contained on them, serial numbers won't help to ID where they previously had been installed. Like if it had a configuration file unraid reads to assign them as disk 10 for example. Knowing the serial number of current 10 is useless to me. The data set is too massive to do it the way you suggest. I can't possibly find what is missing from 42 TB. The best I can hope is to figure out what 3 puzzle pieces of data these disks do contain, then if I can ID them back to the original slot and sync in time with the unraid array...that would be ideal. I have to work backwards to do it. Meaning if my Spare1 contains X data, Spare 2 contains Y data and Spare 3 Z data, then array once started is missing Y data but has Z data...I at least know I can blank out the Z drive and recover the Y data later. I have an unknown missing data set right now, and 3 unknown disks. I also have a "hole" in my array containing a blank disk, as well as some sort of sync issue.

Is there someone who can answer my questions regarding trying to ID these disks before I start adding unknown things to the array? I thought my lesson, beyond backups, was to stop and gather info before proceeding. I'd like to try to figure out if this is possible first.

I don't know how I could back up 42 TB, and I don't know what is missing because of the way Unraid spans across the disks. I don't have a comprehensive backup, sorry. Only what is stored on these disks, and now I have 2 'extra' disks for swapping or recovering data as necessary. So I am hoping the backup is stored on a disk and I can re-sync the array.

I would like to save files if possible. I have all 3 original disks. I'm not sure which disk is which, or what data is on them. O whether it was the original 13. I was hoping there was a way to read software raid configuration data from the drive. It could be the original 10 or 11 or wiped and re-formatted already. I only saw a folder structure. I have 2 other disks I haven't tried browsing yet. I guess it's the array being out of sync I'm sort of trying to figure out. It seems like I added a disk to the array, and instead of copying files it just added blank space to the array. So I wanted to try to assess what is on my disks first, maybe get them labeled and organized with the hope it would add the lost data somehow. In other words, I think I added a disk incorrectly and blanked the file system out during the rebuild. But I also think the original red balled disk wasn't actually bad, so I was exploring the possibility of re-syncing the array to the original disk.

So my new disk 13 has at least a data structure on it, when I browsed it. I'm not keen on the idea of blasting data by formatting to begin. I'd like to find out what I actually have and what is rebuildable if possible. I'm not sure if it's useful data, it only seems to have the folder structure, but maybe that's because the array was out of sync? I'm trying to find the blank spots in the array, but ultimately would like to see what data is still on these disks, if any. My memory is fuzzy but I think I may at least have the original disk 10 or 11, which I think is now added to the array by empty. Does that make sense? Ultimately what I think is happening, or was, I thought I had failing disks because they kept redballing. It was only when I was connected to the UPS they were failing though, I would yank, rebuild on my bench all fine for weeks, then fail again. So...I think all 3 of my disks are ultimately sound, but likely dirty, data wise. I was hoping there was a way to ID a disk to the software raid assignment, because I'm sure I got mixed up somewhere.

I don't have a new server to build. The screenshots look identical to the original ones, as the server sat idle. I added the unmenu as it had different options because someone mentioned 5.0.5 was vague, but it's showing the same thing. I'm ready to try to recover and rebuild this system now.

I don't know what the SNAP plugin is, but I have the unmenu I think? I also have a USB to SATA controller I could connect to try and read what is on these other disks. I don't know which disk is number 13 until I can read the serial number inside the case, it's a tight stacked horizontal layout. And I suppose with a sharpie, I've got a new project next time I'm yanking disks.

Yeah this project went down the rabbit hole in a hurry. I can't tell what I was trying to do in reverse, and I've forgotten what happened and why exactly. What really caused my problem was a weirdly bad UPS, so when I was getting disk errors I would disconnect and move the server to test on my workbench, everything would pass, connect back to the UPS and start getting errors again. I thought I had some errors, but they just needed to sync up. Made it all worse, obviously. Finished my remodel project and I dusted off the old server to try and salvage data, but get it up and running again. I had tried upgrading from the version 5, but one of the controllers on my motherboard wasn't recognized. Board is Intel Bx975XBX2 and it has 2 different Marvell controllers I think. I also have an add-in controller, but when I upgraded I was missing 4 disks so it had to be one from the main board. I fired up the server and I'm back where I was before, I also have 2 disks with unknown or no content left. I don't remember where I was or why. I would need to brush up the upgrade and backup process to try a newer version. I'm not sure what is the best idea at this point. Thanks for all your help. I know this doesn't make much sense.

OK, it's weird in that some of disk 13 is actually there, the directory structure seems mostly good with 8 reported missing, but a bunch of files are missing as well. I'm clicking via the browser window, folder icon and the 8 directories missing list on console as: /usr/local/emhttp/mnt/disk13/...missing ...due to locked reiserfs recordtype error message. Also disk 13 and 9 still appear in the listed disks for shares, Disk 10 is not listed as browsable and 10 and 11 have been removed from the shares disks list entirely while 11 is browsable as blank. Disk 11 is again the one I have the original Seagate which ran Seatools and repaired a few sectors, then passed a long generic test. There is also a /mnt/user/lost+found on disk 9 which contains data under coded names and directories. I can browse further via smb shares if that helps.

I meant something like /sdg1, I didn't recall at the time which one exactly. I ran it on /dev/sdh1 or disk 11, the Toshiba, while the array was offline if I remember correctly, but also after I had formatted that same disk. I believe again I had performed the rebuild with the array in maintenance mode which left me with a blank disk after the Toshiba rebuild. I first ran resiserfssck --check which prompted for the --rebuild-tree /dev/sdh1 which I also ran with the array offline. I have the Seagate 3TB which I pulled and replaced with the Toshiba. The WD that now reports as unformatted had been disabled and rebuilt...but I believe while the array was in maintenance mode. I hope that makes sense. I also have 2 more 3 TB disks which have been in the array at some point. I can't recall their exact state currently but a safe guess is they have been precleared.

There are no backups. It's a 42 TB array full of 3TB disks. I have the original disk that redballed in both cases, although the first may have been precleared before I realized what was happening.

I'm not sure which controller it was. I installed 6.0 and a whole series of disks was missing so I used the email an issue feature which said it was uploading a log file along with my email address and the bug description, but I haven't heard back. I'm also unclear where I ended up. I'm still not sure what happened to the original rebuild and have been having dropped disks and rebuild issues every few weeks for awhile now, which prompted the upgrade attempt. Basically unraid would report disks as bad or disabled, I would pull and swap, rebuild and carry on. The disk would then test OK outside unraid so I would cycle them back through again until...

Version 5.05 and I was attempting to update to version 6 prior to this but was unable due to a driver issue with one of my disk controllers. Anyway I'm not entirely sure what happened as it was a routine swap and rebuild. I may have had the disks in maintenance mode during the rebuild, can't recall but after completion I had an empty disk and a new prompt asking me to format. I rebooted a few times and did the format, although I'm not sure why in retrospect. I also have the original pulled disk, I ran Seatools for Windows and repaired some bad sectors, drive tests Good now. After the format as you might expect it shows a blank disk. I also later ran reiserfsck on one of the /dev/sdg1 which after test asked to rebuild-tree which I also did successfully. After checking some disks I restarted the array and one of the WD drives froze and subsequently was re-added to the array, and now it says it has an unformulated partition. I finally dug up my lost account info and figured I better ask for some help. Thanks in advance.

http://www.staples.com/Toshiba-Canvio-Desktop-3TB-Desktop-USB-30-External-Hard-Drive-Black/product_982533 Are these drives any good?