Jump to content

tjsyl

Members
 View Profile  See their activity

  • Posts

    26

  • Joined

  • Last visited

 Content Type 

Report Comments posted by tjsyl

    raid 6.12.2 hangs after one day. No ping

    in Stable Releases

    Posted

    On 7/6/2023 at 11:58 PM, tjsyl said:

    So, I've been going at this for 3 weeks now and my poor disks are on their (IDK for sure) 10th parity check...  After doing all I can gather from forums, checking hardware and changing from MACVLAN to IPVLAN the issue still persists.  I've moved to new hardware (HP-Z820 to a Supermicro X9DRi-F) and replaced the flash drive.  New flash drive started with 6.12.0 and upgraded to .1 and .2 to see if helps resolve this issue but to no avail.  

     

    Original config was 9 drives. 7- 4TB drives in the array and 2- 8TB drives in a mirror. I've replaced the 2 parity drives with 8TB drives and 2 of the 4TB drives with 8tb drives(one at a time letting it rebuild the drive).  So as it sits I've got 11 drives in a 44tb array and the 2 original 8tb drives in the mirror still.  I am trying to use UNBALANCE(stopped all docker containers) to move the data from the mirror to the array then plan on adding those 2 drives to the array.  It keeps locking up at some point during the process of the move and I am forced to hard reboot.  I am still able to access via IPMI but at the physical console or IPMI console Unraid is unresponsive. 

     

    I would love to see this issue get figured out but I am considering copying the config folder and reloading the flash drive with 6.11.5.

     

    I just enabled syslog and mirror to flash and now going to start the copy again.  Yesterday I came back from a lock up and hard reboot and about 45% into the parity sync it happened again.  I've got the Diag from one of the instances but they don't have shit, I dug through each file and found nothing while I was waiting for someone to chime in on another topic I created and now found this one to tag along in.  If and when it happens again I'll post the diagnostics.  Only docker container I have running is the TwinGate connector. It's really useful with this because I get the notification when it goes offline. 

    Well, found out one of the 16GB ram sticks was indeed bad. $14.13 later and its been solid for well over 24 hours. One parity sync down and 2.2 of 5.5 TB moved so far.  

    raid 6.12.2 hangs after one day. No ping

    in Stable Releases

    Posted

    So, I've been going at this for 3 weeks now and my poor disks are on their (IDK for sure) 10th parity check...  After doing all I can gather from forums, checking hardware and changing from MACVLAN to IPVLAN the issue still persists.  I've moved to new hardware (HP-Z820 to a Supermicro X9DRi-F) and replaced the flash drive.  New flash drive started with 6.12.0 and upgraded to .1 and .2 to see if helps resolve this issue but to no avail.  

     

    Original config was 9 drives. 7- 4TB drives in the array and 2- 8TB drives in a mirror. I've replaced the 2 parity drives with 8TB drives and 2 of the 4TB drives with 8tb drives(one at a time letting it rebuild the drive).  So as it sits I've got 11 drives in a 44tb array and the 2 original 8tb drives in the mirror still.  I am trying to use UNBALANCE(stopped all docker containers) to move the data from the mirror to the array then plan on adding those 2 drives to the array.  It keeps locking up at some point during the process of the move and I am forced to hard reboot.  I am still able to access via IPMI but at the physical console or IPMI console Unraid is unresponsive. 

     

    I would love to see this issue get figured out but I am considering copying the config folder and reloading the flash drive with 6.11.5.

     

    I just enabled syslog and mirror to flash and now going to start the copy again.  Yesterday I came back from a lock up and hard reboot and about 45% into the parity sync it happened again.  I've got the Diag from one of the instances but they don't have shit, I dug through each file and found nothing while I was waiting for someone to chime in on another topic I created and now found this one to tag along in.  If and when it happens again I'll post the diagnostics.  Only docker container I have running is the TwinGate connector. It's really useful with this because I get the notification when it goes offline. 

×
×
  • Create New...