troymeredith Posted April 14, 2019 Share Posted April 14, 2019 Disc issues - again!! My HDDs range from approx 4 to 18 months old and two of them are now unassigned on my microserver. The last time this happened, the issue was power-related, and I checked the cabling (disconnected then reconnected) until I got a positive result. I've done the same thing now, but to no avail. Is more checking of cables required, am I impatient by posting this, or is there something wrong with my discs? I have attached a diag in the hope that someone can immediately spot the problem and offer some guidance. TIA tower-diagnostics-20190414-0722.zip Link to comment
JorgeB Posted April 14, 2019 Share Posted April 14, 2019 Array is in a strange state, you'll need to provide more info, like: Was there a parity 1 disk? Is it missing or you were only using parity2? Both parity2 and disk are assigned as new disks, do you know for sure which disk was which? Link to comment
troymeredith Posted April 14, 2019 Author Share Posted April 14, 2019 using parity 1, never was a parity 2 disc Link to comment
JorgeB Posted April 14, 2019 Share Posted April 14, 2019 Then why did you assign it as parity2? Also do you know for sure (by the serial numbers) which disk was parity and which was disk1? Link to comment
troymeredith Posted April 14, 2019 Author Share Posted April 14, 2019 really? unintentional! allow me to check the serial numbers... Link to comment
troymeredith Posted April 14, 2019 Author Share Posted April 14, 2019 Last 4 chars of the 2 discs in question: Parity: EN6T Disc 1: 4XAC Link to comment
trurl Posted April 14, 2019 Share Posted April 14, 2019 Not really very important, but your syslog is filling with these: Apr 14 07:06:03 Tower emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Basic.key (-3) Apple ecosystems seem to drop these annoying ._ files on everything they touch. You should delete that file from your flash after you get everything else fixed. Parity and parity2 are NOT interchangeable. Post a screenshot of Main - Array Devices. Link to comment
JorgeB Posted April 14, 2019 Share Posted April 14, 2019 If you are absolutely sure about those serials do a new config, re-assign all disks and check parity is already valid, then run a parity check, if you're not sure also do a new config but assign all disks as data disks, there should be one unmountable disk, that will be parity. Link to comment
troymeredith Posted April 14, 2019 Author Share Posted April 14, 2019 1 hour ago, trurl said: Not really very important, but your syslog is filling with these: Apr 14 07:06:03 Tower emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Basic.key (-3) Apple ecosystems seem to drop these annoying ._ files on everything they touch. You should delete that file from your flash after you get everything else fixed. Parity and parity2 are NOT interchangeable. Post a screenshot of Main - Array Devices. Link to comment
troymeredith Posted April 14, 2019 Author Share Posted April 14, 2019 Additional question - any way to remove the "Parity 2" entry if it's not needed? Link to comment
trurl Posted April 14, 2019 Share Posted April 14, 2019 1 hour ago, troymeredith said: Additional question - any way to remove the "Parity 2" entry if it's not needed? When the array is stopped and it is ready to allow disk assignments as in your screenshot, then it will allow you to assign parity2. If nothing is assigned to parity2 then when the array is started parity2 doesn't appear. Link to comment
troymeredith Posted April 14, 2019 Author Share Posted April 14, 2019 20 minutes ago, trurl said: When the array is stopped and it is ready to allow disk assignments as in your screenshot, then it will allow you to assign parity2. If nothing is assigned to parity2 then when the array is started parity2 doesn't appear. gotcha - man thanks! Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.