Jump to content

Two Weird Things


Recommended Posts

OK, first off, sometimes when a torrent is downloaded, the permissions are changed so that any users, can't read or write to the directory, but guest can read, but has no write, and i either have to do the "new permissions" thing on the control panel or chmod 777 from terminal... weird.

 

Shut down to move UPS location and now Disk 3 (a 6 month old 6tb drive) is saying unmountable? I shut down correctly and am confused because there is nothing obvious to me in SMART data or otherwise that makes that drive seem any bad at all.

 

Please help :)

mondo-diagnostics-20200708-2239.zip

Link to comment
1 hour ago, Raz31337 said:

I ran xfs_repair on /dev/sdh

Why? From the FAQ johnnie.black linked, you should have run it on /dev/md3 assuming we are still talking about disk3.

Quote

Preparing to run xfs_repair

Start the array in Maintenance mode, by clicking the Maintenance mode check box before clicking the Start button. This starts the unRAID driver but does not mount any of the drives.

Running xfs_repair

Now you are ready to run the XFS file system test. At the console or in a terminal session with SSH or Telnet, type this: (Note: the following example refers to Disk 1, as /dev/md1. You will need to substitute the correct drive for your case. For example, if it is your Disk 5 that you are testing, then substitute md5 for md1.)

xfs_repair -v /dev/md1

 

Link to comment

root@Mondo:~# xfs_repair /dev/md3
Phase 1 - find and verify superblock...
Phase 2 - using internal log
        - zero log...
Invalid block length (0x0) for buffer
Log inconsistent (didn't find previous header)
empty log check failed
zero_log: cannot find log head/tail (xlog_find_tail=5)
ERROR: The log head and/or tail cannot be discovered. Attempt to mount the
filesystem to replay the log or use the -L option to destroy the log and
attempt a repair.
root@Mondo:~# 

Link to comment

root@Mondo:~# xfs_repair -L /dev/md3
Phase 1 - find and verify superblock...
Phase 2 - using internal log
        - zero log...
Invalid block length (0x0) for buffer
Log inconsistent (didn't find previous header)
empty log check failed
zero_log: cannot find log head/tail (xlog_find_tail=5)
        - 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
        - process newly discovered inodes...
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
        - check for inodes claiming duplicate blocks...
        - agno = 2
        - agno = 0
        - agno = 3
        - agno = 1
        - agno = 4
        - agno = 5
Phase 5 - rebuild AG headers and trees...
        - reset superblock...
Phase 6 - check inode connectivity...
        - resetting contents of realtime bitmap and summary inodes
        - traversing filesystem ...
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
Phase 7 - verify and correct link counts...
Maximum metadata LSN (1:573584) is ahead of log (1:2).
Format log to cycle 4.
done

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...