fred jones

Will do! Is -v --verbose the highest debug level? I can "kinda" read C/C++ code (I am an FPGA engineer not a SW guy!) so I dont mind adding some extra debug stuff if necessary to track down what's going on.

Hi All, I need some advice on how to proceed. I recently moved my Snapraid setup from a local PC with a SAS Controller card connected to a home made mess of drives crammed into an empty PC case via a SAS expander card. I decided to try and make the setup a little more "normal" so I bought a SuperMicro Servo (12 drives and two SAS controller cards) and a Netapp Diskshelf (24 drives and and a builtin SAS expander (IOM6). There were two data drives I could not move so I copied the files over to a new...

Thanks! The "autosave" was my issue! I had it set way too high! 50000! That's 50 TB, correct? From the example configuration file - Automatically save the state when syncing after the specified amount of GB processed (uncomment to enable). Exactly what does that mean? Is that the number of bytes read from a data disk that have had their parity calculated and written to a parity disk? Example - say I have two drives, each 50000 GB in size and autosave is set to 50000. Does that mean that Snapraid...

Interesting! The font looks much better after posting!

Well, this bites! sync -F failed at 27%, my fault though. But again snapraid status says all is good. Do I need to restart the sync -F and let it finish w/o stopping? It's just hard to keep this system up for 50+ hours straight! Here is the printout showing status says it's OK but sync -F stopped at 27%. I think I am just wearing out the array! Sorry about the non-mono font making things look messy! I dont see a way set the font! Any advice on whether I have to run this non-stop is appreciated! Using...

Hi All, I added a parity disk and ran sync with the "-F, --force-full" option. It said the time to finish was about 50 hours. I stopped it around 10% to update some SW which required a reboot. I later ran sync without the -F option and it said nothing to do. I checked and sure enough, the new parity disk had a parity file that was the same size as the other parity disks. How is that possible? It was only 10% done. Do you have to let sync -F finish w/o interruptions? That's a long time to go w/o something...

BTW - I recently migrated from four eSata multiplier (x4) boxes and 8 drives in a desktop to a Huge desktop case I found at Goodwill. All 24 drives are in the new case and are controlled w/ a SAS expansion card with the main SAS (HBA Mode) controller on the old computer. I have a single cable between the two boxes. I guess I could have shelled out a few more bucks and got one of those used 24 drive bay rack mount unit on ebay but then I would have missed the fun of assembling this one! Of course...

Interesting, I think that thrashing around would not be a good thing! I just added that new 8TB drive I mentioned above as a parity and it's going to take 50'ish hours so making that slower is a bad idea!! I think I will just add a 2nd snapraid instance as suggested but start w/ 16TB drives and slowly migrate - heck this all started as a way to use up old junk drives and turned into a real hobby! Thanks for the input!