res0nat0r

I'm ftp'ing the data from disk8 to another host as we speak. Here is a github link to a smartctl --test=short for /dev/sdm (disk8) and /dev/sdh (disk11) https://gist.github.com/res0nat0r/721afbee4a2f5b6723de I don't actually see any reallocated sectors on either of those disks.

Attached is the current state of the array. I can copy the data from disk8 to a new system so that it is backed up safely to a remote location first thing. Also would a short smartctl test of all disks be appropriate for a first look? $ for x in b c d e f g h i j k l m n o; do smartctl --test=short /dev/sd{$x}; done Or would a --test=long be needed? Either way I can post the results of that when it is completed. Thanks for the help sofar everyone.

Actually: Plugging the old disk11 back into the array, I'm able to boot the array now and only disk8 is marked as bad. I need to look into smartctl for both 8 and 11 and see if I can verify if 8 is working and then mark it is healthy and might be able to properly recreate this array.

Thanks for the replies. Yes unfortunately this was something I didn't address right away just due to some other priorities. Thanks for the rebuild info I'll see if I can dd_rescue disk11, which is the only one I believe is bad and create a new array with valid disks from the new consolidated drives.

Hi... Thanks for the reply. I'm afraid you are most likely correct. I'm going to try and gather data from disk11 with dd_rescue, and I'm going to look at disk8 in a bit. A couple of related questions: 1] Is it possible to start the array and just mount the /dev/disk* by themselves? That way I can have an NFS export to easily just access the disks on the network for now? 2] Is it possible to create a new array from scratch with existing data on disks? IE: I consolidate my data to new drives, then tell unraid to make a new parity disk from the existing reiserfs drives I tell it to use, or does it have to format the drives as blank disks? I'd like to be able to just move things to a new set of disks and tell it to just create an initial parity from there, or is that not possible? Since I don't have enough temporary space on another computer to house all my data and move it back to a blank unraid array I have to try something like this, if possible. Thanks!

Actually this is for v5, I've created a topic in the proper forum. This can be deleted.

Hi, I've had a drive fail that I need to replace (disk11) in the screenshot. I've inserted the new disk and need to re-raid, but I also have a disk (disk8) that is marked red, but has been available and working for some time. This has been like this for a little while (disk8), and I've not fixed it before disk11 just died, it appears to be red because it can't get some temp info from the drive, but reads/writes and other stats are just fine. Is the array screwed now and cannot be rebuilt because I have 2 failed disks even though 8 is actually healthy? Before this disk11 failure the array was stopping/starting just fine even though disk8 was marked red due to just temperature info being missing. Or is there a way to tell disk8 to just be marked healthy? Attached is a screenshot. Thanks!!

Hi, I've had a drive fail that I need to replace (disk11) in the screenshot. I've inserted the new disk and need to re-raid, but I also have a disk (disk8) that is marked red, but has been available and working for some time. This has been like this for a little while (disk8), and I've not fixed it before disk11 just died, it appears to be red because it can't get some temp info from the drive, but reads/writes and other stats are just fine. Is the array screwed now and cannot be rebuilt because I have 2 failed disks even though 8 is actually healthy? Before this disk11 failure the array was stopping/starting just fine even though disk8 was marked red due to just temperature info being missing. Or is there a way to tell disk8 to just be marked healthy? Attached is a screenshot. Thanks!!

I tried this a bit back too and it seems to be ignored. i will look into it more here soon and let you know if I can figure anything out. This might work for the /mnt/disk* exports or not, and also maybe not at all on the /mnt/user/* shares. Since that is shfs which is something written internally at limetech it might be hardcoded in there somewhere to do that. It might be the same for the /mnt/disk exports too, not sure.

OK. I will see what I can find out and report back!

Anyone, Bueller?

I have my new array back now, and would like to see if this is doable. Can I get unraid to export my user shares like normal nfs exports? IE I want to enforce uid/gid perms and only uid's with the proper perms can write/read to dirs, I dont want everything to be remapped to root that connects. Thanks

Joe, Great! Thanks alot for your answer, this will save me a bunch of time, obviously I did save my drive info, I have stickies and also the S/N's of each on where they were in the array, so I will be good when I get the new box.

This seems to be like the question I had a bit back. I am awaiting a new server from Tom. I had to exchange my old one, but I had 1xParity and 3xData drives in the box. I have saved my setup and know which serial numbers goto which slots. But will this matter? I am receiving an entirely new system here in the next couple of days. I want to save the data on my data drives. I guess I should have, but I dont have any super.dat files or anything from the old flashdrive. If I readd the 3xData drvies to the new array will it think they are brand new and do a mkreiserfs on them? I do have one extra unformatted disk as of right now which was never added to the array which I can use to juggle this data around. Will I have to: 1] Preclear pristine disk. 2] Add to array 3] Insert old disk w/ data on it. Do not add to array. 4] Manually mount old disk somewhere like to /a 5] Copy all data from drive outside array to drive added to array. 6] Unmount /a 7] Add it to array and have a mkreiserfs run on it (which is fine because the data has been already copied to another drive in step 5) 8] Repeat for two remaining data drives. Thanks! Stefhen

actually right now i havent even been able to calculate parity since the box keeps locking up during the procedure, so it is running protected as of now anyway. this is good, i will just keep track of my two data drives, put them in the new box in the two data slots and also put the parity drive back in its slot in the new box once i get it, then just recalc parity. i was just hoping i wouldnt have to copy all of my data back over to the box again. and it doesnt look like i do, which is good.