helpermonkey

roger! and we're off.

Cool! does it look like i'm good to go to start this thing back up again then? i'm assuming it won't lose any of my data after all the prep but just want to make sure.

okay guys - thanks so much for your help up until this point. Soooo ... i think i'm ready to fireup the server ... here's the status page... also - fyi - i've started getting more of those UDMA errors that I thought was cable/card connected ... johnnie helped me get that equipment swapped out - however, now i'm getting errors on ones that are connected directly to the mobo AND when they were in other locations, were not showing errors (nor were the drives in the existing slots showing errors). Is it possible this is just a symptom of all the changes going on? Is there a way to double check or test these things otherwise? Disk 1: 199 UDMA CRC error count 0x000a 200 200 000 Old age Always Never 3522 this is the new 8TB data drive. When i first inserted this drive, i was doing a preclear on both the parity drive and this drive at the same time. However, I realized (after reading) that these were problematic so i stopped the preclear on Drive 1 and then ran it alone and from the begining after that.... the errrors have always showed up. Disk 2: 199 UDMA CRC error count 0x0032 200 001 000 Old age Always Never 331 Disk 3: 199 UDMA CRC error count 0x0032 200 196 000 Old age Always Never 2567 Disk 5: 199 UDMA CRC error count 0x003e 200 199 000 Old age Always Never 8 (this is the one plugged into the new card with the new cables). So a) can i fire this up again and start the parity sync-data rebuild? b) what do i do about these errrors?

sweet - that did the trick. Okay - now i've gotta wait on my new sata card and then when I get everything else confirmed i'll post here before i restart the array just to make sure i've fixed all the problems. One other quick question - would it be advisable at some point to move the data on disk 3 (which is almost full) to disk 1 now that it is 8TB? If so - how would i go about doing that? Since I'd want to keep disk 3 in the array but just give it more space.

perfect - thanks.... so just: "rsync -av /mnt/disks/ST2000VN000-1H3164_W1H2RQHS/ /mnt/disk1/"

here ya go.... root@Buddha:~# rsync -ah --stats --max-delete=100 --delete-before --force -n /mnt/disks/ST2000VN000-1H3164_W1H2RQHS/ /mnt/disk1/ Number of files: 55,462 (reg: 51,455, dir: 4,007) Number of created files: 123 (reg: 97, dir: 26) Number of deleted files: 20 (reg: 9, dir: 11) Number of regular files transferred: 98 Total file size: 1.96T bytes Total transferred file size: 94.41G bytes Literal data: 0 bytes Matched data: 0 bytes File list size: 1.57M File list generation time: 0.091 seconds File list transfer time: 0.000 seconds Total bytes sent: 1.62M Total bytes received: 1.90K sent 1.62M bytes received 1.90K bytes 1.08M bytes/sec total size is 1.96T speedup is 1,210,386.29 (DRY RUN)

ha - that would make a difference.... here is the end of the list.....

Looks like i got some error ....

So I SSH'd in and copied the directories ... when i came back to it finished the directory sizes don't match.... the drive on the left is the 2TB and ther drive on the right is the 8TB. Should I just delete the music and videos off the 8tb and try to recopy them? or is this good enough that when i put back in the parity drive and start the array that unraid will figure out what's missing from where?

Okay so i obviously don't know what the fudge i'm doing still... so i loaded up MC navigated to the disks directory and the disk1 directory .... and went to copy by using F5 but it doesn't seem to do anything. I tested in another directory using F8 to delete and that worked like a chanp... what am i doing wrong?

roger that - so i'll go ahead and do the copy and then get back with y'all once my new card gets here and i can replace that. Going to be a few more days i suspect 🙂

cool - thanks. it's not good but kind of expected right now - the SATA card i've got in there is bad (part of the reason why i moved drives around physically to test) and i'm waiting on a new card to come in. So so while I wait for the new card if i move down the tree disks displays the directory as the identification info for the drive (aka ST2000VN000-1H3164_W1H2RQHS). so should i copy /mnt/disks/ to /mnt/disk1/ or should i copy the directory one layer down?

okay - so - i unassigned the parity drive, removed it, inserted the 2 TB drive, started the array, ... restarted the computer, and mounted the 2 TB drive. Since the drive mounted - it sounds like it means i indeed have the correct 2tb drive. okay so then i launched MC via the start menu and read amongst other things. however, as you will see from my setup - i don't see the drives listed - only directories. i want to copy from the unassigned drive to the drive in disk 1 slot but can't figure out how to get that to work ...as in my reading i was told you can only copy disk to disk and share to share. here's a screen cap of the drives. Also notice how it says one of the drives is unmountable? I dunno what's up with that. and if i stop the array it tells me disk 5 is unmountable not disk 4. Meanwhile, just to make sure - you mentioend that a disk won't mount if it's duplicated already and since the unassigned drive mounts - does that confirm that i'm using the right drive?

cool - i'll read up on that then!

got it - it will take me a bit to get this executed (since it sounds like i'll need to configure Krusader) and then see how long it takes to copy.

okay so here's how i set it up this time: am i ready to turn this back on and let the drives sync? just to be clear - the 8 tb parity drive was properly rebuilt. disk 1 is empty (and should have data contained on a 2 tb drive sitting outside of the. disk 2 was never touched (other than being relocated) disk 3 was never touched (other than being relocated) disk 4 is the old parity drive that i replaced in the array (up from 2 tbs) disk 5 was never touched (other than being relocated) by relocated i mean just moved to a different slot in the case and then given a different disk number in unraid. so am i ready to hit start?

thanks so much! going to try this and if i get to a part where i'm stumped i'll throw something up again.

right right - that is where i currently have the 2 tb disk that I didn't properly get over to the 8tb disk...so i'm pulling that out and putting in the 2 tb disk that was properly dealt with.

man - i really know how to screw simple things up okay so .... thanks for your patience with me :-). step 1: shut down array. step 2: disk 1 is the blank 8tb.... current disk 5 is the 2tb drive that has the "missing data on it." so pull out disk five and replace it with the 2 tb drive that is all set. so the array will be as follows: parity - 8 tb that is all set. disk 1 - 8 tb that is blank (missing the data from that 2 tb drive that is now unplugged). disk 2 - 4 tb that is fine disk 3 - 4 tb that is fine disk 4 - 4 tb that is fine (albeit with that strange message). disk 5 - 2 tb drive that is fine. step 3: go to tools>new config> select preserve settings for parity and cache drive - select "yes i want to do this", then hit apply. step 4: start the array and let unraid take it from there?

So i keep going farther down the rabit hole.... i took a camera shot real quick before i started this step... I started the parity check swapped out disk 5 for the old 2 tb (this is before i went to replace the parity drive like you said).... but in any event the array is running in maintenance mode and now it's telling me there's no file system on drive 4.... thoughts?

gotcha ... thanks!

so i don't think option a is possible since i've already taken the original 4tb parity and used that to replace a 2tb drive. so i'm going to disconnect the parity drive then and use that slot for the old drive to copy old data off of :-).... one last question - i'm 99% sure which of the 2 tb drives is the one i need to swap but in the case I copy the wrong drive over - what happens when i fire this thing up and it sees 2 data drives that have the same data on them but are different in capacity?

okay - so just to be extra clear ... cuz as you can see i know how to screw some ***t up :-)...as I don't have any extra drive slots right now - take out one of my other data drives - replace it with the old 2 tb that has the right data ... fire up the array and mount that 2 tb drive but don't put it into the array - then get something like Krusader up and running and just copy data? when that's done - shut down the array, replace the 2 tb drive that i just got data off of with the original 2 tb drive and fire the array up?

so basically just pull out the 8tb drive 1 and replace it with the old 2 tb drive - mount it and hit rebuild? then when that's done - i can reinstert the 8tb? also - do i let this parity check finish?

Hey folks, So in my infinite wisdom - lates nights combined with not a complete understanding of everything I'm doing ... i think I messed up. Here's what's going on and wondering what I should do in case I'm about to hit a point of no return. Running 6.7 btw. Original setup: 4 Tb Parity Drives 1,2,3 - each 2 tb Drives 4,5 - each 4 tb. Cache drive hasn't been touched nor has my flash drive. I bought two 8TB drives. Ran a preclear on one, then replaced my parity drive - did a rebuild. all good there. Pulled out one of the 2 tb drives, replaced it with the original partiy drive... did a rebuild...all good there. Pulled out another 2 tb drive, Pre cleared my second 8 tb drive. Then that's where I think i went off. So once the preclear finished - i powered down the server and literally rearranged the drives (drive five actually doesn't fit in the cage for example, so i put the 2 tb there and then moved the other drives into the box. I then powered on the server and then rearranged the drives in main tab. I got a whole bunch of "wrongs* - which made sense and i understood (it seems incorrectly) as a new config. I went to new config - preserved the assignment for just my parity drive and then hit apply (remember i still had not rebuilt that second 8tb drive). So when i went to restart the array - i saw a warning that my parity drive would be overwritten. but i also saw a check box that basically said - check here if the parity drive is valid so i did that. In any event, I fired up the server and it's now doing a parity check but i have a sneaking suspicion (since my docker failed to start and seems to be missing some paths now) that I have potentially FUBARed my system. Have I? Here is my diagnostics file - but would love some advice on what to do here in case i can still get this thing back online pretty simply. Also - not sure if this helps but the disk i have in slot 4 is also somehow listed under historical devices ... same serial number and everything. so i dunno what that's about. buddha-diagnostics-20190529-0711.zip