Jump to content

Checkm4te

Members
  • Content Count

    5
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Checkm4te

  • Rank
    Newbie
  1. The Array works again! It worked exactly as you said. For Short: Start the Array in maintenance mode go in the corrupted disk menu and start xfs_repair option: <-blank for repair if error occures follow the help and run xfs_repair option: -L and after that again start xfs_repair option: <-blank for repair that worked for me. Thank you very much everyone!
  2. I first started xfs_repair with -n as option after that i started to start the repair again with "blank" in th eoption field as described in the help. This gave me the following error report: 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. So as i can't mount my disk I should run xfs_repair with the option -L am I right?
  3. Again the required zip file. I tried to start the array in maintance mode so that works. Should i try to start my array without my disk 2 and/or 7 to check if one of these disk are causing the error?
  4. Thank you for your help Here is the required zip file.
  5. So first of all I'm from Germany I hope you can follow my english. My Problem: I can't start my Array anymore I reboot the server and when I hit the Start Button in the webinterface it ends in an loading loop. When the array isn't started unraid and webinterface works just fine. The first time i was able to reboot the server with putty after that I couldn't shutdown or reboot the server over the console in putty and needed to do an manual forced shutdown through press button method. Only when it isn't in the loop. I have now 2x forced the shutdown so unraid wants to start an parity check when i start the array. What I did before the error occured: I disabled disk 2 in my media share and enabled read& write for my user I moved via Windows Explorer from Disk 2 (2TB HDD) to Disk 7 (4TB HDD) ~300GB Media Files mkv mp3 etc pp... Then the copy process abortet due an "unexpected network error" I don't know what occured it maybe that the windows backup started during the copy process. It also stopped due an "unexpected network error" my media share contains disks (2),4,6&7 my backup share disks 3&5 so there should be no conflict due the disks. What is functional. I can login via putty as root I can restart the Server and the webinterface starts I can ping my unraid server 192.168.xxx.y My Specs: Unraid Server Plus v6.3.3 Intel Xeon 1246v3 32GB RAM 2x480 SanDisk Ultra II SSD as Cache 7 Different sized HDDs all Seagate only one WD 1 Seagate 4TB Parity 2x LAN setup as backup