J1mm1

Members
  • Posts

    4
  • Joined

  • Last visited

J1mm1's Achievements

Noob

Noob (1/14)

0

Reputation

1

Community Answers

  1. Just for the record. I've been able to fix the issue by doing a security-erase with hdparm. I don't think it actually did anything physically as the process was immediate but the disks size has been restored and I've been able to rebuild the array. No SMART errors on both disks so I don't know exactly what happened but now it's fixed... Thank you
  2. Thank you, I did what you've suggested with no success. I don't understand how the SSD could be damaged though, they are new units with maybe 1 month of power on life and very low stress on Unraid. Hopefully new units I'm going to use as replacement won't fail as fast.
  3. Diagnostics attached. Sorry for not doing it in the first post. Thanks jimminas-diagnostics-20240409-1834.zip
  4. Hi Everyone, I'm posting a new thread as i wasn't able to find something identical to my situation. I have an array composed by 5 discs: 2x 2TB HHD as parity discs 1x 2TB HHD (identical to the parity discs) as main array disc 2x 480GB SSD (disk 2 and 3) Everything was working fine until the update to Unraid 6.12.0, right after the reboot both 480GB ssd have started to be seen with a total size of 1GB each, causing of course a mismatch between the expected size and the detected size. I've tried removing the SSDs from the array and restarting it, they add them back but nothing changed. What options do I have? Should I format the disks and restore from parity? Is there a reason why this might have happened and a way I could prevent it in the future? Thank you all.