- Closed
- Annoyance
Hello,
pre-cleared 2 drives over 42h
took array offline
added the two new drives (new to array but used drives, hence why I wanted the stress test = zero issues)
brought array online and Clear starts
Unraid documentation here: https://docs.unraid.net/unraid-os/using-unraid-to/manage-storage/array/adding-disks-to-array/
says:
"6. Start the array. Unraid will automatically start a clear operation on the new disk, filling it with zeros to ensure it's ready for use while maintaining data integrity. The clear operation runs in the background, so you can still access your array. The disk won't be usable until the process is complete. If you've pre-cleared the disk, Unraid skips this step."
Well I can say that right now Clear is running right after I added the new disks. So unraid did not skip this step. I did not format the disks. I did exactly the steps above.
Side 'annoyance': the log entries like "Buffer I/O error on dev md5p1, logical block 0, async page read" should be filtered if these are to ignore. Since this just raises eyebrows everytime for a normal user. I add disks maybe every few years and will not remember this and hopefully search for it and find that answer again before opening a ticket. You can not rely on a normal user to just know that after years. There should be measures to mitigate such tickets.
googled and found this: https://forums.unraid.net/topic/137937-strange-errors-buffer-io-error/
Thank you.