darkastorm
Members
-
Joined
-
Last visited
-
1. Create a new VM with debian nocloud qcow2 works fine. 2. Changing the vDisk using FROM VIEW to use another file or the same file but renamed. 3. The configuration changed a lot, not just the vDisk file name, resulting a none working VM. Restart VM always going to UEFI interactive shell.
-
Hello Guys, Just past the schedule party check, you guys are right, after the PSU was replaced, no more party disk error. Thanks.
-
Hello guys, Replaced the old PSU to a 800W PSU, now 4 drives and 1 parity drive, passed the first parity data check. Let's keep it running till next parity check to look how it goes. Thanks again you for the suggestion.
-
The PSU is an unknown brand, label marked it as 550W. I will get another PSU to try anyway. Thanks for you suggestion, will post the result here after I have replaced the PSU.
-
Hello there, Could someone help to try to find out what is the problem of the parity disk error? The situation is I have 4 drives, all the same model HGST Ultrastar HC320 8TB 1 is parity drive. 3 drives in the array work just fine, no error. The parity drive threw out blk_update_request I/O error randomly. Sometimes it works fine until the schedule parity check, sometime it just threw out blk_update_request I/O error randomly and I need to remove it from the parity drive list. But when I run the smart shot / long test, no error found, preclear disk a dozen times without error. I have tried to change the SATA cable, SATA power cable, SATA port with no luck, so I assume there might be some problems of the drive anyway. So I bought another one, preclear the new drive without error. Then the same blk_update_request I/O error happens again when I change the new drive as the parity drive. I really have no idea what is wrong / what to do next. Any help is appreciated. tower-diagnostics-20220629-1947.zip
