Jump to content

RobinG

Members
  • Posts

    26
  • Joined

  • Last visited

Everything posted by RobinG

  1. Got my data back using some free software I found on this sub Free XFS File Recovery Software. Thanks for all the help trurl, I actually learned a lot. Backup your server, parity isn't a backup.
  2. I appreciate the encouragement and the assistance. I should have been more patient waiting for your response but was on a time crunch. I'll let you know if I was able to recover any data.
  3. I should have waited for you, yes it is mounted. and has only 87gb on it now not 3ish tbs.
  4. i should have copied the data over while it was unassigned, really bummed about that decision.
  5. well, i took disk1 out of the array and into unassigned. formated disk 3 cause it didnt have any data. never formated disk1. I am assuming when i moved it back to the array it started doing a data-rebuild of the "emulated" disk 1 which had no data...
  6. i think i did upload old diagnostics skynet-diagnostics-20240129-2033.zip
  7. I didn't new config, I stopped the array and moved the disk to unassigned, the xfs repair gui worked, i saw the 3tb on the drive then stopped the array and moved the disk back to the array, started the array and noticed it was rebuilding data.
  8. got you, i stopped the rebuild right away and moved disk1 to unsassigned.
  9. i saw the 3ish tb on the drive when i had it in unassigned devices , moved it to the array and now there is nothing...
  10. yes, disk 3 had no contents so i am not concerned with that one.
  11. used the the webUI, it fixed the file system. put it back in the array and now it is doing a data-rebuild. should i let it do that or is it overwriting all the old data?
  12. yes, you are right i don't need a 2nd parity drive.
  13. Got about two hours left on the parity-sync. I moved all the disks back to their previous slots.
  14. i have no copies, i will update you after parity sync.
  15. Just two drives both of the 500gb dirves in newcache pool
  16. i did this within the last hour, i did notice my bad nvme drive
  17. My original array had one paity drive a 12tb, I wanted to add another parity dive the 12tb ending in MM. I moved a couple files off hard drive MM so I can use it as a parity drive. I created a new config and must have selected the incorrect old parity drive which must have been the 12tb ending in 76. I'm about 4 tbs of data lost now. Sorry if i'm not explaining well i'm freaking out a bit.
  18. It was a disk that was in the array that I tried to move to parity. skynet-diagnostics-20240128-1608.zip
×
×
  • Create New...