BobNik

Members
  • Posts

    35
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

BobNik's Achievements

Noob

Noob (1/14)

4

Reputation

1

Community Answers

  1. Thank you. I will upgrade at some point for sure.
  2. Is this plugin still available for someone like me running a 6.8.3 version? Where to get it and how to install if CA is old too? Why still on 6.8.3 you ask? Simple - everything I have is working just fine. And that brings me to another question...I see version 6.9.15 is now current...is this one of many RCs for a new major release (7.0?). Is there a roadmap defined? Cheers. Bob
  3. would like to wish a Happy New Year to all members and specially the moderators who are tirelessly helping everyone and keeping this product ticking. I have started with version 3 and now close to the latest and will stay for a long time with unRaid. Thank you for all the work and effort. Regards BobNik
  4. My thinking exactly. Thank you for the replies.
  5. The log looks ok to me....is it safe to add this disk? - not new, used on other system for 2 years with no issues. What you think? Thank you preclear_disk_log.txt
  6. Parity completed with 0 errors...everything is back to normal. Thank you JorgeB for the help.
  7. Update: All cables checked and rebuild of disk2 completed with no errors from any other disks. Currently running parity check (with correction on).
  8. Thank you. Will follow your steps later tonight.
  9. Nothing was written since the rebuild. The rebuilt disk2 looks fine; same with disk5 that have read errors. I will check the cabling but dont know how to rebuild again.
  10. Diagnostics attached as requested tower-diagnostics-20221116-1329.zip
  11. Thank you JorgeB, No, I have not rebooted yet. What would be the next step? Your help is appreciated.
  12. Hi, been Unraid user for 10+ years, from version 3 or 4 and now on 6.83. One of my disks failed (disk2) and I started a repair from the parity by introducing a brand new disk; nothing new for me, did that in the past. Now, during the rebuild the other disk #5 started reporting read errors: Nov 15 22:21:08 Tower kernel: print_req_error: I/O error, dev sdg, sector 473325040 Nov 15 22:21:08 Tower kernel: md: disk5 read error, sector=473323952 Nov 15 22:21:08 Tower kernel: md: disk5 read error, sector=473323960 Nov 15 22:21:08 Tower kernel: md: disk5 read error, sector=473323968 Nov 15 22:21:08 Tower kernel: md: disk5 read error, sector=473323976...... with the total of 77,056 errors. The rebuild completed and all disks and array is green. Now, I am running a parity check (with NO correction) and getting same read errors: Nov 16 08:15:47 Tower kernel: md: recovery thread: P incorrect, sector=473323952 Nov 16 08:15:47 Tower kernel: md: recovery thread: P incorrect, sector=473323960 Nov 16 08:15:47 Tower kernel: md: recovery thread: P incorrect, sector=473323968 Nov 16 08:15:47 Tower kernel: md: recovery thread: P incorrect, sector=473323976..... The parity check will complete in next couple of hours however not sure if I want to repeat the parity sync again with the correction or start looking for disk5 replacement? The smart report for Disk5 is attached. Please advise. regards Bobtower-smart-20221116-1259.zip
  13. Unfortunately I didn't keep them. The question is more generic in nature.
  14. Over the year or so I have accumulated a couple of 'failed' drives from my 12 drives Unraid. They all are replaced with the new ones, one at the time, and am wondering what to do with them. Keep as unmounted drive (reformat first), introduce them back to array if format goes with no errors, or discard them completely or..?