Jump to content

magic144

Members
  • Posts

    99
  • Joined

  • Last visited

Everything posted by magic144

  1. Can anybody on here comment as to whether or not the preclear add-on (I.e. the script, NOT plugin) is still working OK after the jump to unRAID 6.4.0-Stable? Or if any new updates that are required for it have come to light??
  2. Hi, can you tell us what changes are in the 2017.03.31 recent update?
  3. Thanks for the reply, RobJ - I didn't see the other thread. Probably try it again next time with JoeL up-to-date script under the covers. It doesn't seem to be maintained anymore, so I wanted to migrate to the latest/greatest. Might just have been bad luck something else went wrong to leave my preclear stuck at 80%... Takes so damn long to clear/test these monster drives!!
  4. Just wanted to follow-up comment after GreenDolphin's post. Curiously their reported behavior seems *very* similar to my own (what with the write/zeroing cycle's dd "failure" and the the subsequent continuation of preclear scripting, even though a dd error was detected) I also noticed that GreenDolphin's write cycle also seems to have failed EXACTLY with the same shortfall as mine (2097152 bytes) - even though we are dealing with different sized disks. Seems like too much of a coincidence. I wonder if there is possibly something wrong with the write command or the calculation there-in - perhaps the author of that script (gfjardim) can comment? FYI, the follow-up preclear attempt I just performed using Joe L's script (with all the latest fixes) has finished just fine.
  5. Looks like the write_disk function in preclear_disk.sh is NOT returning a non-zero value even though dd_exit IS (1).
  6. Tried to use this plugin (up-to-date, version 2017.02.16a using default script) for the first time this weekend... everything 'seemed' to be going OK - had gone through read and zero phases, was in final post-read phase (I'm running unRAID 6.3.2 on a LimeTech-built MD-1510/LI - I don't have a ton of add-ons - Nerd Tools and Preclear Disk only) ...until I noticed this AM that the disk being pre-cleared (sdb) had reverted to green (not-busy) LED and the preclear process seemed to be stuck at 80% unfortunately, I didn't save the syslog (although I looked at it and couldn't find anything notable) and have since re-booted but I do have the preclear log (IIRC, the dd process of the Post-Read (pid 7569) was NOT present in the ps list when I checked, which makes sense given that nothing was happening) what surprises me is that even though a dd failure in the Zeroing phase was listed as a failure in the preclear plugin's log, the main plugin never seems to have noticed/acknowledged this and just carried on - is that supposed to happen?? here is that log: I'm currently re-running the most up-to-date Joe L. cmdline script on that drive in a screen window, as per my previous workflow Mar 10 10:13:00 preclear_disk_WD-WX21DC59ACN7_26175: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --notify 1 --frequency 4 --cycles 1 --no-prompt /dev/sdb Mar 10 10:13:00 preclear_disk_WD-WX21DC59ACN7_26175: Preclear Disk Version: 0.8.4-beta Mar 10 10:13:00 preclear_disk_WD-WX21DC59ACN7_26175: S.M.A.R.T. info type: default Mar 10 10:13:00 preclear_disk_WD-WX21DC59ACN7_26175: S.M.A.R.T. attrs type: default Mar 10 10:13:05 preclear_disk_WD-WX21DC59ACN7_26175: Pre-Read: dd if=/dev/sdb of=/dev/null bs=2097152 iflag=direct Mar 10 10:13:05 preclear_disk_WD-WX21DC59ACN7_26175: Pre-Read: dd pid [28700] Mar 10 23:30:10 preclear_disk_WD-WX21DC59ACN7_26175: Pre-Read: dd - read 6001175126016 of 6001175126016. Mar 10 23:30:10 preclear_disk_WD-WX21DC59ACN7_26175: : 0 Mar 10 23:30:11 preclear_disk_WD-WX21DC59ACN7_26175: Zeroing: dd if=/dev/zero of=/dev/sdb bs=2097152 seek=1 conv=fdatasync,noerror oflag=direct Mar 10 23:30:11 preclear_disk_WD-WX21DC59ACN7_26175: Zeroing: dd pid [28345] Mar 11 12:34:15 preclear_disk_WD-WX21DC59ACN7_26175: Zeroing: dd - wrote 6001173028864 of 6001175126016. Mar 11 12:34:16 preclear_disk_WD-WX21DC59ACN7_26175: Zeroing: dd command failed, exit code: 1 Mar 11 12:34:19 preclear_disk_WD-WX21DC59ACN7_26175: Post-Read: dd if=/dev/sdb bs=512 count=4096 skip=1 iflag=direct Mar 11 12:34:20 preclear_disk_WD-WX21DC59ACN7_26175: Post-Read: dd pid [7548] Mar 11 12:34:20 preclear_disk_WD-WX21DC59ACN7_26175: Post-Read: dd if=/dev/sdb bs=2097152 skip=1 iflag=direct 2>/tmp/.preclear/sdb/dd_output | cmp - /dev/zero &>/tmp/.preclear/sdb/cmp_out Mar 11 12:34:20 preclear_disk_WD-WX21DC59ACN7_26175: Post-Read: dd pid [7569]
  7. Can I delete these (previous-unRAID-OS) files though? /boot/config/plugins/NerdPack/packages/6.X
  8. Hi, quick question - hopefully easy answer! There seem to be old/previous OS variants of NerdPack files under /boot/config/plugins/NerdPack/packages i.e. 6.1, 6.2 (am now running 6.3 and there is also a 6.3 subdir present) Can I delete the 6.1 and 6.2 folders now? It's about 244MB on my flash drive. Does that have to be (should it be) done manually? Any reason it isn't automagically cleaned up on upgrade? Or just for safety? Thanks in advance
×
×
  • Create New...