gfjardim

Community Developer
  • Posts

    2213
  • Joined

  • Last visited

  • Days Won

    1

gfjardim last won the day on August 25 2018

gfjardim had the most liked content!

5 Followers

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

gfjardim's Achievements

Rising Star

Rising Star (9/14)

95

Reputation

  1. Please send us your diagnostics file, because the preclear log didn't revealed anything.
  2. Please send me your diagnostics file (you can PM me if you wish)
  3. Yep, it's the same controller so the odds the other port has problems are not negligible. HBA is host bus adapter: In computer hardware, a host controller, host adapter, or host bus adapter (HBA) connects a computer, which acts as the host system, to other network and storage devices.[1] The terms are primarily used to refer to devices for connecting SCSI, Fibre Channel and SATA devices.[2] Devices for connecting to IDE, Ethernet, FireWire, USB and other systems may also be called host adapters. Enviado de meu SM-G985F usando o Tapatalk
  4. Logs show a bad drive and/or a bad controller card. Hard to tell which is the faulty one because of mixed syslog entries. I would try to put the testing disk into another controller's SATA port to eliminate the HBA from the suspect list.
  5. Thanks for answering this so promptly. Is there anything that Preclear can change to show Unraid that the disk is currently working?
  6. This is not a problem with Preclear itself, but with Unraid and the mechanism it uses to track unassigned drives usage. Let's see if@dlandon have a clue of that's going on here. Enviado de meu SM-G985F usando o Tapatalk
  7. Hi @Josh.5, I've found that the driver for new Intel generations aren't available for Ubuntu Bionic, only for Focal. Just sent you a PR addressing this issue. Thanks in advance.
  8. Please send me tour diagnostics file, can be by PM. Enviado de meu SM-G985F usando o Tapatalk
  9. Just released a update trying to patch this bug, please update and report if it's fixed.
  10. This approach was needed before, when disks controllers lacked advanced firmware functionality. Like you said, if a block is read and it doesn't check against its CRC, the firmware tries to recover the data from its CRC, and if it fails, it will mark the sector as a pending sector. When you write the sector again, it will store the value in a new spare sector designated by the firmware to occupy its place, and mark the old one as a reallocated sector. That's why you don't need fancy random patterns to test modern disks. That's why we read the disk in the pre-read, to force the disk to detect defective sectors and mark them as pending sectors. After that we write to the disk to force the firmware to map new spare sectors to the pending sector's place and mark them as reallocated sectors.
  11. If it's marked as mounted, then it's mounted. Depending the settings in Unassigned Devices, it auto mounts USB disks when plugged.
  12. You're wrong again. You need a code to run this command, code to stop it, code to detect if a sync command is issued and pause the operation to prevent a docker container from hanging on stop, code to collect/compare SMART attributes, code to send notifications etc. So believe me when I say it's not just a button. Enviado de meu SM-G985F usando o Tapatalk
  13. Your post wrongly assumes that every new drive is empty. Many USB drives people use to shuck comes formated in NTFS from the factory. So no, not every new drive is wipe clean from factory. You can't also guarantee that the disk don't become magnetized if it is exposed to a strong magnetic field prior to installation. And you wrongly assume every drive added is a new empty drive, not a drive prior used in FreeNAS, Openvault etc. Other wrong assumption is that every bit written into the disk is a zero. Look at this topic and see many problems in zeroing that occur because of defective RAM. I'm pretty sure Unraid doesn't verify its cleared drives, so this can led to errors in the parity check if you have a bad RAM stick. As it is now, you can use Erase and Clear Disk to write randomized data into it. It reads the disk prior to write, but if you think it's important to random fill the drive prior to the first (surface) read, it can be easily adapted. It's not written to be a test tool, but in many cases this script behaves like one. I look into the statistics sent and I see loads of disks that have increased pending and reallocated sectors after the preclear, and many disks that fails preclear because of uncorrectable sectors and other hardware problems, so I know it can be a valuable tool. Obviously, if you think the plugin is redundant you can always skip it's use and rely in the built-in Unraid functionality. Enviado de meu SM-G985F usando o Tapatalk
  14. Probable. Enviado de meu SM-G985F usando o Tapatalk
  15. Your root filesystem is getting full and the script stopped to prevent any possible problems. Try to reboot and then start it again.