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.

Actually I am getting an entire new system, flash and all. So this new box will have no knowledge about my old system. Humm do I need then maybe just the super.dat and disks.cfg file copied off the old flash and placed on the new system once it arrives then?

So Tom is awesomely replacing my new 1510 because it has locked up a couple of times. Is this the correct way to replace the 2 data drives I have in the system sofar? Both of my data drives and one parity disk were pre_cleared before they were added to the array. Both data drives obviously have been formatted and are active in the array as of now. Am I correct in thinking that when I place both of these back in the new system I will be able to readd them to the new box without reformatting (since they have reiserfs and have been already initialized by unraid)? If not, I could just insert a 3rd data disk, add it to the system, mv the data off of the already (old) drives which arent readded to the unraid gui, just mounted by hand somewhere, then once the old drive has been emptied I could properly add it back to the system. Am I thinking about this correctly? I haven't had a whole lot of time yet to learn all of the ins and outs of unraid yet and am having to ship this back tonight or tomorrow so just had a couple of questions... Thanks

This looks alot like Suns Thumper series of storage, but just much cheaper. Very cool. The only iffy thing is how you must access your data: Going to read the whole thing through once I get home, looks pretty interesting.

yup. 720 works just fine for me it looks perfect. stuff in 1080p just seems to waste disk space for me and i cant tell any difference.

Here is a quick rundown: http://en.wikipedia.org/wiki/X264 http://en.wikipedia.org/wiki/Matroska basically x264 is an open source encoder for the H.264 format, which is a standard video compression for HD content. matroska is a relatively new audio/video container format, like mpeg4 or avi, but is open source and very full featured. alot of highdef content you will come across is encoded in x264 + matroska you can get a bluray disc encoded down to ~4-8GB @ 720p and looks amazing. handbrake has a crap load of options to it to support this, but i think there are presets to do a generally good encode, check out the preset formats such as: I dont use handbrake all too often, and only use the cli version on linux, but the documentation should lead you the right way, just look around for x264 presets.

I copied about 1TB of data to the box over the weekend and it didnt lock up at all. this was not using my gig switch though. i am copying about 300 more GB using the gig switch now to the unraid box and it seems ok sofar. i added this to /etc/modprobe.d/forcedeth.conf options forcedeth max_interrupt_work=20 i updated my initramfs on my ubuntu box and rebooted, and now rsyncing the data isnt causing the error message above. also i dont have any TX/RX errors via netstat -i i am not sure what happened before, if this network issue caused the network just to crap and i thought it was the unraid box or not, but i did have a kbd and mouse hooked up to the thing before it stopped responding, but i dunno....but things look ok as of now.

x264 encoding is amazing. i can watch a 720p HD movie and it is about 4G in size and looks amazing, with DTS or 5.1 sound. 4-8G for a 720 or 1080p is fantastic. mkv's are my new fav video format.

Check out Handbrake also, it is a great transcoding app for linux/osx/windows http://handbrake.fr/

What does everyone think would be the best way to do this? specifically I don't want: anongid=0,anonuid=0,all_squash I want to enforce unix uid/gid perms so that I can chown stuff to root and make it a-w (like my movies directory) to prevent anything stupid from occuring like an rsync with the --del option that points to the wrong source dir etc. All of my file movement is done by my non-priv account so I would like to respect these things. Does anyone think this is a bad idea due to the way unraid is working, or can I set this across reboots somewhere so when I add a new share I dont have to mess with this manually in the future? Thanks alot.

I am trying once more to just do a big initial copy of all of my data to the box. if it messes up at all i am going to send an email...