So yesterday i posted here because i wasnt able to gain access to my server gui through the server network.

 

i originally never was able to view my server directly using a monitor so i purchased an adapter to allow me to do so.

 

i logged into the server gui and finally was able to get to my server, but theres a HUGE issue.

 

seems like almost everything was deleted. my shares and VMs are gone, but it still has the plugins saved for some reason like PLEX for example.

 

can i get some help on how to fix this issue?

are my disks corrupt?

tell me what information i need to provide you with to further speed this solution

 

thanks

 

below is the most recent log information:

 

Dec 9 19:13:35 HARMNAS kernel: XFS (md1): Metadata corruption detected at xfs_inode_buf_verify+0x8b/0xb1, xfs_inode block 0x60

Dec 9 19:13:35 HARMNAS kernel: XFS (md1): Unmount and run xfs_repair

Dec 9 19:13:35 HARMNAS kernel: XFS (md1): First 64 bytes of corrupted metadata buffer:

Dec 9 19:13:35 HARMNAS kernel: ffffc90003034000: 49 4e 41 ff 03 01 00 00 00 00 00 63 00 00 00 64 INA........c...d

Dec 9 19:13:35 HARMNAS kernel: ffffc90003034010: 00 00 00 0b 00 00 00 00 00 00 00 00 00 00 00 00 ................

Dec 9 19:13:35 HARMNAS kernel: ffffc90003034020: 00 00 00 00 00 00 00 00 58 31 5e e9 24 31 82 86 ........X1^.$1..

Dec 9 19:13:35 HARMNAS kernel: ffffc90003034030: 58 31 5e e9 24 31 82 86 00 00 00 00 00 00 00 93 X1^.$1..........

Dec 9 19:13:35 HARMNAS kernel: XFS (md1): Metadata corruption detected at xfs_inode_buf_verify+0x8b/0xb1, xfs_inode block 0x60

Dec 9 19:13:35 HARMNAS kernel: XFS (md1): Unmount and run xfs_repair

Dec 9 19:13:35 HARMNAS kernel: XFS (md1): First 64 bytes of corrupted metadata buffer:

Dec 9 19:13:35 HARMNAS kernel: ffffc90003034000: 49 4e 41 ff 03 01 00 00 00 00 00 63 00 00 00 64 INA........c...d

Dec 9 19:13:35 HARMNAS kernel: ffffc90003034010: 00 00 00 0b 00 00 00 00 00 00 00 00 00 00 00 00 ................

Dec 9 19:13:35 HARMNAS kernel: ffffc90003034020: 00 00 00 00 00 00 00 00 58 31 5e e9 24 31 82 86 ........X1^.$1..

Dec 9 19:13:35 HARMNAS kernel: ffffc90003034030: 58 31 5e e9 24 31 82 86 00 00 00 00 00 00 00 93 X1^.$1..........

Dec 9 19:13:35 HARMNAS kernel: XFS (md1): Metadata corruption detected at xfs_inode_buf_verify+0x8b/0xb1, xfs_inode block 0x60

Dec 9 19:13:35 HARMNAS kernel: XFS (md1): Unmount and run xfs_repair

Dec 9 19:13:35 HARMNAS kernel: XFS (md1): First 64 bytes of corrupted metadata buffer:

Dec 9 19:13:35 HARMNAS kernel: ffffc90003034000: 49 4e 41 ff 03 01 00 00 00 00 00 63 00 00 00 64 INA........c...d

Dec 9 19:13:35 HARMNAS kernel: ffffc90003034010: 00 00 00 0b 00 00 00 00 00 00 00 00 00 00 00 00 ................

Dec 9 19:13:35 HARMNAS kernel: ffffc90003034020: 00 00 00 00 00 00 00 00 58 31 5e e9 24 31 82 86 ........X1^.$1..

Dec 9 19:13:35 HARMNAS kernel: ffffc90003034030: 58 31 5e e9 24 31 82 86 00 00 00 00 00 00 00 93 X1^.$1..........

Dec 9 19:13:35 HARMNAS kernel: XFS (md1): metadata I/O error: block 0x60 ("xlog_recover_do..(read#2)") error 117 numblks 32

Dec 9 19:13:35 HARMNAS kernel: XFS (md1): log mount/recovery failed: error -117

Dec 9 19:13:35 HARMNAS kernel: XFS (md1): log mount failed

Dec 9 19:13:35 HARMNAS root: mount: mount /dev/md1 on /mnt/disk1 failed: Structure needs cleaning

Dec 9 19:13:35 HARMNAS emhttp: err: shcmd: shcmd (25): exit status: 32

Dec 9 19:13:35 HARMNAS emhttp: mount error: No file system (32)

Dec 9 19:13:35 HARMNAS emhttp: shcmd (26): umount /mnt/disk1 |& logger

Dec 9 19:13:35 HARMNAS root: umount: /mnt/disk1: not mounted

Dec 9 19:13:35 HARMNAS emhttp: shcmd (27): rmdir /mnt/disk1

Dec 9 19:13:35 HARMNAS emhttp: shcmd (28): sync

Dec 9 19:13:35 HARMNAS emhttp: shcmd (29): mkdir /mnt/user

Dec 9 19:13:35 HARMNAS emhttp: shcmd (30): /usr/local/sbin/shfs /mnt/user -disks 2 -o noatime,big_writes,allow_other,use_ino -o remember=0 |& logger

Dec 9 19:13:35 HARMNAS emhttp: shcmd (31): rm -f /boot/config/plugins/dynamix/mover.cron

Dec 9 19:13:35 HARMNAS emhttp: shcmd (32): /usr/local/sbin/update_cron &> /dev/null

Dec 9 19:13:35 HARMNAS emhttp: Installing Plex Media Server...

Dec 9 19:13:39 HARMNAS emhttp: Install failed: Unable to create install directory

Dec 9 19:13:42 HARMNAS emhttp: Starting services...

Dec 9 19:13:42 HARMNAS emhttp: nothing to sync

From the snippet, disk 1 has corrupted information on it and you need to run Check Disk File Systems but you really should post your diagnostics

i just downloaded the diag where/how should i post it?

i just downloaded the diag where/how should i post it?

It the forum will allow it (ie: it's not too big), just attach it to a reply in this thread.  If not, upload it to something like dropbox and attach a link here

 

here it is

harmnas-diagnostics-20161209-2001.zip

Only problem is on disk 1 and you need to follow the steps in the link previously posted.

 

But you also most likely have to reassign that 120G Sandisk as your cache drive, as you don't have one assigned at the moment (which is the real reason why nothing is quite working right)

so should i reassign the sandisk first or run the check disk first?

 

also will i be able to recover my data?

so should i reassign the sandisk first or run the check disk first?

 

also will i be able to recover my data?

Should have no problem recovering.  The order of the sandisk vs the check disk doesn't make a difference

 

should i post results from the check here? im slightly confused on what to do from here

 

just in case to speed this procees here is the xfs_repair_Status

 

removed

Clicking on Help on the UI gives this

 

Check Filesystem will run the xfs_repair program to check file system integrity on the device.

 

The Options field is initialized with -n which specifies check-only. If repair is needed, you should run a second Check Filesystem pass, setting the Options blank; this will permit xfs_repair to fix the file system.

 

After starting a Check Filesystem, you should Refresh to monitor progress and status. Depending on how large the file system is, and what errors might be present, the operation can take a long time to finish (hours). Not much info is printed in the window, but you can verify the operation is running by observing the read/write counters increasing for the device on the Main page.

 

 

Im sorry if im kind of slow, but i seriously need some help so bare with me please.

 

the quote below is the message i received. i was searching on how to mount the filesystem (which i thoguht was to start array and then set it back to maintenance-mode), but i received the same message. what steps should i take to complete this error

 

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.

 

thanks you so much btw

Im sorry if im kind of slow, but i seriously need some help so bare with me please.

 

the quote below is the message i received. i was searching on how to mount the filesystem (which i thoguht was to start array and then set it back to maintenance-mode), but i received the same message. what steps should i take to complete this error

 

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.

 

thanks you so much btw

Put -L in the options for the check disk.  Usually no loss of data occurs

how do i know when the system is fully repaired or the files have been recovered? is it if i dont receive any error or corruption messages in the check?

how do i know when the system is fully repaired or the files have been recovered? is it if i dont receive any error or corruption messages in the check?

The status window should tell you as it goes through the checks after you hit the check button

 

Sent from my SM-T560NU using Tapatalk

 

 

so it should read something saying successful or just no errors or what?

 

edit:

 

i think i have everything fixed now. im lastly attempting to reassign the cache disk. ive already turned off the array and set to cache and started it again and its giving me unmountable. is this supposed to be how it is or do i also need to run a check on it?

so it should read something saying successful or just no errors or what?

 

edit:

 

i think i have everything fixed now. im lastly attempting to reassign the cache disk. ive already turned off the array and set to cache and started it again and its giving me unmountable. is this supposed to be how it is or do i also need to run a check on it?

Try explicitly setting the file system on the cache drive to xfs or Btrfs instead of auto.  If that doesn't work then set it to what you think it was and run the file system checks on it

 

Sent from my SM-T560NU using Tapatalk

 

 

so i changed the cache to xfs and ran a check on it and received this message:

 

 

    Phase 1 - find and verify superblock...

    bad primary superblock - bad magic number !!!

 

    attempting to find secondary superblock.........................

    Sorry, could not find valid secondary superblock

    Exiting now.

 

any idea where i should go from here?

so i changed the cache to xfs and ran a check on it and received this message:

 

 

    Phase 1 - find and verify superblock...

    bad primary superblock - bad magic number !!!

 

    attempting to find secondary superblock.........................

    Sorry, could not find valid secondary superblock

    Exiting now.

 

any idea where i should go from here?

Yeah, wait for @johnny.black to hopefully notice this thread.  Out of my comfort zone now.  (Assuming you were doing this all through the GUI, and not the command prompt - If via the command prompt, then you probably forgot the partition # in the identifier.  EG: /dev/sdc1 and not /dev/sdc)

 

(Assuming you were doing this all through the GUI, and not the command prompt - If via the command prompt, then you probably forgot the partition # in the identifier.  EG: /dev/sdc1 and not /dev/sdc)

 

I have no idea what you mean by this. I've been searching the forums for solutions as well as the wiki and don't fully understand what to do. Do you mean in the command line above check? Where I put in -nv? I'm using the unRaid GUI. Also can you direct johnny black to this post if necessary? Thanks again

Cache was unassigned on previous diagnostics, set the filesystem back to auto, try to start the array and post new diags.

 

Cache was unassigned on previous diagnostics, set the filesystem back to auto, try to start the array and post new diags.

 

here is new diag

harmnas-diagnostics-20161211-2108.zip

No filesystem is found when trying to mount the cache disk, if you are sure what it was you can chose that and try to run the appropriate repair tool, but I'm not very optimistic it will work, you'll probably need to format it and start over.

What would reformatting it do? What info was even on it I honestly don't even know.

Possibly your appdata folder, any share that was using cache could have some data there until the next mover run.

Alright so if irrformat it all I have to do is reassign it?

 

Also I have this issue which started happening after this problem. Basically whenever the server shuts down I need to login to the unRaid GUI every time. Before this issue it would automatically login using regular unRaid what can I do to fix that issue as well? Was it caused by this problem I'm having?