jbuszkie

I think he was more referring to emptying a drive for removal and assumed the drive was still working such that you could move the file off then zero out the drive. And then never losing parity protection..

Not the best way... but could you move it all to the cache disk and then let the mover "rebalance" it with the share set to the correct setting (I forget which one it is..)?

Thanks, Squid! Is there a post somewhere that outlines how to find the offending process that's keeping the drive from being unmounted? I tried the the lsof command but I couldn't figure out what I needed to kill. I'm pretty sure it was something accessing something that was mounted from the docker image. Jim

I needed to reboot my machine yesterday so I stopped all my dockers and then tried to stop the array. It got stuck trying to umount the drives. It was stuck trying to unmount the drive that my docker image was on. I couldn't find any browser or telnet session that was using or pointing to any docker image files. I ended up having to force a reboot from the console. Luckily I was able to restart my dockers on a reboot with no issues. I couldn't find any info in the FAQ.. So what is the proper way to shutdown/reboot when using dockers? Do I need to manually stop the dockers and then stop the docker service? Or if I stop the array will it do everything for me? This will also come into play in a power failure scenario. Will the system shutdown cleanly when the battery gets low. Thanks, Jim

I have a new disk coming online soon. I'll probably have to move more file around. I'll check the permissions before I run it next time. Thanks for the help guys, Jim

I don't recall if I had any permission issues. I think I might have. And I just installed unbalance several days ago! I didn't think to check for an update so soon! :-)

Here is the relevant stuff from the log file.. I: 2017/07/10 20:54:50 core.go:596: _calc:End:srcDisk(/mnt/disk4) I: 2017/07/10 20:55:06 core.go:782: Running transfer operation ... I: 2017/07/10 20:55:06 core.go:814: Command Started: rsync -avPRX "HTPC_Stuff/edrive" "/mnt/disk10/" I: 2017/07/10 23:22:17 core.go:143: Sending config W: 2017/07/11 04:58:25 core.go:886: Command Interrupted: rsync -avPRX "HTPC_Stuff/edrive" "/mnt/disk10/" (exit status 23 : Partial transfer due to error) I: 2017/07/11 04:58:25 core.go:991: unBALANCE - TRANSFER operation INTERRUPTED Started: Jul 10, 2017 20:55:06 Ended: Jul 11, 2017 04:58:25 Elapsed: 8h3m18.906s Command Interrupted: rsync -avPRX "HTPC_Stuff/edrive" "/mnt/disk10/" (exit status 23 : Partial transfer due to error) Transferred 962.2G at ~ 33.98 MB/s And I don't see anything in the syslog around 4:58... What error? hmm...

Great tool! I tried to do a move yesterday from one data disk to another and it seemed to work (a part from seeming very slow...) However when I looked today, it never deleted the source files. They all got copied, but never deleted... I basically used all the stock settings.. Jim

Ok.. I guess that makes sense. I forgot about the tools syslog thing! and now with color coding!! (probably been there for a while I just didn't upgrade!) Now I don't have to use unmenu for that anymore! :-) Kudos to Boniel(sp?) for the continued fantastic job on the Gui developments!! Jim

When I click on the log icon in webgui it only give me like 60ish lines or so.. Is there a way to make that adjustable so I can see more of the past log? I couldn't find anything in the settings area.... Thanks, Jim

Well it didn't work so well in the past! I've switched ports from MB to card and back in the past and I've had to trust parity.. I'm very happy it works really well now!

It did!! like magic!!! New MB. New CPU. New Memory. New storage card. Bam! The array came up ready to run! I was shocked! (and very happy!!!!) Thank You Limetech for making this robust! I remember in the past that the software often times didn't see moved drives very well and we did have to new config and trust parity And then there was that funky command "set something something.."

I just got my new MB/CPU/Mem all set up! This new MB has dual intel nics on board. I tried to set up teaming in Unraid and it mostly failed. It looks like the teaming worked but I couldn't access it the way I did before. The router I have it on supports teaming and, I believe, is set up correctly. I have a Win machine that is also using teaming and I can see everything on that machine just fine. What was really weird was that I COULD see unraid from the other teaming machine... but no other machines on my network. From another win machine I would see the unraid box in the network browser but it gave me an error when I tried to see any of the shares. I also couldn't get to the unraid gui webpage either from any machine other than my other win7 teaming machine, I believe... Is there something I'm missing? I set up unraid for bonding and selected the 802.3ad option. As soon as I turned off bonding, Everything is accessible like in the past. Jim

And that will keep all my shares and settings?

I remember it being more complicated than that!

Well that was easy!

I don't know if I have the latest.. but it was saying 2011.. Maybe I'll look into it to see what's out there and if the release notes show anything "compelling" with the latest release. If it can see my 8T drives and run them at speed, then I'm not going to touch anything! Now I'll have to search the forum again to try to remember how to transfer all my disks to a new machine without losing any data! Jim

I did attach a disk and it saw it fine. I was also able to set the MB bios to not run the storage bios. So I'm back to fast booting.. Now that means I can' boot from this card... But I wasn't planning on that anyway.. Once I get things all set I might re-enable it because I don't care how long it takes to boot if I'm rebooting once a month or less. But for now it was VERY annoying when I'm rebooting every 5 minutes!!! Just for grins I'll try it in another system and see if maybe the UEFI is causing it to run extremely slow (some sort of emulated mode??) I did enter the control section of the card bios and I saw nothing funky.. Question... This card, by default, runs IT firmware, right? I shouldn't have to re-flash it??? And thanks bjp!

1 min 31 sec from first bios print till it says initializing! 1 min 51 sec total till it finishes.

30 to 60 sec before it says initializing after the first bios text And it did show a cd rom drive, i believe, in unraid

I've finally got my new hardware and ran it through the memory tests.. I decided to throw in my sas9201 that I got off of e-bay. With no drives attached it takes forever to get through it's bios stuff. Is this supposed to take this long?

I ran the latest version of Memtest86 (from passmark) in uefi mode multi core.. With the memory OC to 2666 and it ran overnight with no errors. So I don't trust the stock memtest86+ 5.01 in parallel CPU mode... All my frustration was for nothing! :-( Now I can transfer the hardware tonight! Jim

The more and more I read... It seems like parallel CPU testing is not reliable. I don't know which version of memtest86+ equated to which version of memtest.. but as of V4.3 of memtest they made the default multi-cpu test to be round robin Look here So now I start again in round robin mode or at least change the memory range to start above 10M...

Ha! I think it might be an issue with memtest!!! I've tried memtest on two different machines at work and they both give similar errors! not as frequently.. but they do give errors. My work machines are rock stable. The standalone memtest (not memtest+) seems to run fine with 4.7.something.. But it only seems to exercise 4 cores (out of 8 ) I can't get the uefi capable V7 something to run on my newer dell machine at work with more than 1 core. Some UEFI Bios limitation. Oh well.. Maybe my new machine at home will be able to run the V7 multi core version. If anyone is bored and wants to try and duplicate my test.. Try running memtest with an upper limit of 10M and just run test 7 (block move) in parallel CPU mode. Jim

I'm also going to try the latest version of memtest. A much earlier version had problems with the block test. And some other random folks had issues as well with 5.01 Is there a windows stress test I could run? (not that I want to take the time to install windows...) Jim