MasterPepe Posted March 10 Share Posted March 10 Hello all, I have since a short power failure problems to start my array again. Since this is the first test server, I decided to install everything from scratch again. I wiped my hard drives with the precleaning tool and formatted them with xfs. I also did an extended SMART test on all the hard drives. This was also error free. I must say that I have a somewhat unusual setup. There is a cache pool with 2 mirrored SSDs installed. In the array I have 8 hard disks. Of these, 4 are connected in the server enclosure via SATA2 and 4 are connected in an external enclosure (Fantec) with USB3. One of the internal disks is used as parity. The first time I installed it, it worked fine. And since I address the hard disks individually, it even runs relatively performant. After a short power failure I got the error that 4 hard drives (the USB3 connected) showed an error. They could no longer be connected to the array. Now I'm standing there and can't get the array to run with empty disks. It starts to write the parity, after 0.8% it aborts. It comes the message with errors and the logfiles are overfilled. Apparently there is an abort at the USB. I can't stop the array then either. The disks are shown twice. Once in the array and once as Unasignd Mounted. I can only get to the disks when I reboot the server. This is still possible via the UI. I will leave the diagnostic and the logfile here. Hopefully someone can help. I would be very disappointed if I had to split the array. Thank you all for the help. MP syslog.txt.zip tower-diagnostics-20230310-2114.zip Quote Link to comment
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.