H72b NAS Disks Problems

Explanation

Videos and Pics

Firmware update

• SC60 Seagate Ironwolf
• Write Cache Disabled
• https://www.seagate.com/de/de/contacts/

Further Background:

• https://community.synology.com/enu/forum/17/post/47575
• https://www.google.ru/search?q=SC60+IronWolf+Write+Cache&oq=SC60+IronWolf+Write+Cache&sourceid=chrome&ie=UTF-8
• https://blog.quindorian.org/2019/09/ironwolf10tbfirmwarefix.html/

• https://nascompares.com/answer/outdated-firmware-sc60-for-ironwolf-drives-which-has-the-write-cache-disabled/
• Problem only when > 1 MBit Network https://nascompares.com/answer/outdated-firmware-sc60-for-ironwolf-drives-which-has-the-write-cache-disabled/
• https://www.seagate.com/de/de/support/kb/does-my-drive-need-a-firmware-update-206091en/
• Enable: Yes or No
• cache ON: a bit faster when writing, but higher possibility of disk corruption in case of power loss
• cache OFF: safer in case of power loss, but some penalty performance while writting lot of data

Hardware Defaults

QNAP

• How to check for hardware issues

Disk Checks on Windows

The best tests can be run on Windows, for example Hard Disk Sentinel.

Problems with Partition

If you check the text description of Hard Disk Sentinel, it suggests to please read the following page: (available also from
www.hdsentinel.com -> Support -> Frequently Asked Questions -> What is a weak sector? How to repair weak sectors? )

Usually one runs ChkDsk if the partition shall not deleted.

Given that it is a no longer used NAS Disk, we can delete the partitions using Partition Wizard

Then we should restart the

Weak Sectors

Usually, weak sectors can be caused by

• real drive failure (error with internal memory, problem with drive head or surface)
• power loss (the write operation could not be completed because of power loss)
• power failure (weak power supply or not stable power line)
• data cable failure or improper connection (usually cause also communication errors )
• system memory or motherboard problem
• overclocking
• general overheating of the motherboard, chipset, hard disk controller

Step1: Verify power loss, failure, etc.

Step 2: Antivirus

Step 3:

Re-initialize disk with Hard Disk Sentinel.

The standard edition allows for a simple override.

Re-initialize via Windows

• How to reinitialize a disk, which is not accepted for the storage pool  (source)
  
  Sometimes you may experience one of following symptoms, if you try to add or readd a hard disk, which is currently not part of the Windows Home Server storage pool:

  • the disk is not listed in the console
  • the disk is listed in the console, but cannot be added to the storage pool or as server backup disk

  In both situations the disk is present for the operating system, if you check the Disk Management Console. To do this, perform following steps:

  • Login to the Windows Home Server desktop locally or via Remote Desktop client.
  • Click Start/Run, type diskmgmt.msc and click OK.

  Your new disk should be visible in the lower area of the Disk Management Console.
  (If the disk is not listed here, it is either not properly connected, physically broken or you need to add drivers for the mass storage controller, to which the disk is attached.)

  In some cases such disks could be detected and added successfully via console after recreating the Master Boot Record (MBR) and deleting old volumes on it.
  (You should not try this with a disk, which has known bad sectors.)
  To do this, attach the disk to a system (can be a client PC or Windows Home Server), open a command prompt and enter following commands:
  diskpart
  list disk
  Check the output of this command carefully and try to figure out, which disk is the disk, which could not be added. If you are not sure (this can happen especially on a server with multiple disks), you may wish to perform this action on a client PC with only one normal disk to avoid an erratic identification.
  select disk x
  Replace the x with the number of the volume, which represents the disk you wish to reinitialize.
  Stop here, if you are not fully sure, since the next command will wipe all data from that disk!
  clean
  ex