toby9999

@Joe L. I was running 1.11 :-( Have downloaded 1.12beta now and will see how I go. I ran pre... -t /dev/sdc (another drive already precleared by 1.11) and it didn't find a valid signature (see attached image) - I'll obviously have to redo every drive, no problem. As the 6 drives all reported absolutely no problems (1 pass), I might use the -n switch to skip the pre/post reads on those drives. I'll contact BJP999 re: the drivedb issue, thanks. Many things are in flux at the moment with the new versions of unraid, support for 3TB drives etc. --- On another note ... I know the suggested method for running multiple preclears simultaneously is via screen, but I was just wondering if it wouldn't be easier to have that capability included in UnMenu? Or would it be too dangerous if the interface was too easy? Hmmm.

Hi I precleared 6 drives (sda, sdc-sdg). Then I installed latest unmenu/screen to do the rest (another 16 drives). In MyMenu, sda didn't show as a precleared drive (it's icon = "+") and it's number of writes showed quite a different value to the other 5 precleared drives. I then used screen to kick off preclearing sda again as well as the remaining 16 drives (sdh-sdw). I refreshed the MyMenu page and it showed every drive EXCEPT SDA as a precleared drive, and the usage column showed the progress of the preclear. I then noticed the last line of the syslog saying ... Tower unmenu[18653]: Precleared disk sda not found in drivedb[] (Drive related) 1) how do I fix this problem? is there a way to manually add sda to the drivedb? 2) since sda has started the preclear again (pre-read, step 1), is it safe to cancel the preclear and will it retain the precleared signature ready for when I add it to the unraid array? Thx! Cheers Toby