J0my

Members
  • Content Count

    22
  • Joined

  • Last visited

Community Reputation

1 Neutral

About J0my

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. @itimpi thanks for your input, I did the repair from the Unraid GUI. It is scheduled to do the next parity check at the first of every month so I might just leave it for now. Thanks again to @johnnie.black it was a great help ❤️
  2. @johnnie.black ok took it down from Maint mode and started the array and it seems to be present and working now with the files present. Is it after that you meant to now put it back into maint mode and do the -vL or leave it as is now. Then final question should I do a parity check again or is that not necessary (as it was disk 1 and not the parity drive that was having the problems).
  3. @johnnie.black here is the result of doing the -v xfs_repair status -v.txt xfs_repair status -v.txt
  4. @johnnie.black Apologies, just the wording sounds a bit odd, that I don't quite understand. Are you just telling me to use -vL or are you saying do -v and then do -vL?
  5. @johnnie.black Thanks for that, as per the wiki I ran -nv and it gave me these results, I put it in a txt doc to save this page getting super long xfs_repair status -nv .txt I am not going to pretend I know what any of that means so if possible what would the next step be based on its findings?
  6. Hello, earlier this month one my drives was spitting out errors and unraid ended up disabling it (Disk 1) tower-diagnostics-20190502-1415.zip, after previous issues with this happening and on recommendations from other members I replaced my raid card with an LSI 9211-8i. Once I got it installed and went through the process of de selecting the drive, starting then stopping the array, reelecting the drive and rebuilding it tower-diagnostics-20190521-1004.zip has had this "Unmountable: No file system" in its details (see attached screenshot). Being relatively new to unraid
  7. So even though I have erased the flash memory, everything says to not reboot, but for what ever reason I am unable to get it to execute the commands, but maddeningly it let me do the erasing one. Hi thanks for the link, just not sure it can help all that much as stated above when ever I do the "sas2flsh.efi -o -f 2118it.bin" it just gives me the syntax error and will not let me do anything. Still have the machine on in case there's anything that can be done.
  8. uhg this is likely in the wrong section of the forums for this also >_<
  9. Hello, I have spent all day following guides on how to flash a LSI 9211-8i into IT mode via USB as I had just bought the card. I am unable to do the flashing via BIOS due to the PAL errors which from everything I have read means the Mobo is UEFI (Gigabyte Z170N-WIFI). I had also tried every way online on how to try get my usb key set up to UEFI but for what ever reason the computer just would not enter the shell, I would get the option to load the USB in UEFI but it would just flash and go back the menu on boot devices (Rufus>FreeDOS>Fat32 etc etc and the usb drive is only 8GB) or if I s
  10. Thanks for expanding on that point, it is really helpful :)
  11. Done, it is all back and present *deep sigh* thank you very much mate, you really are a life saver as I am not really knowledgeable in this stuff so I really appreciate your patience with me. One last question just for a general knowledge thing, when doing a Parity-Check, should the "Write corrections to parity" box be checked or not and what is the recommended frequency of the checks? Will deff be looking to buy a new raid card or just use the 4 sata ports on my mobo and not use a cache drive for the time being.
  12. Ok have done that and now have this Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being destroyed because the -L option was used. - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno
  13. removing the -n flag gets me this Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this.