No Volumes No Shares - Superblock Issue?

Re: No Volumes No Shares - Superblock Issue?

Postby NigelBrownless » Sat Dec 21, 2024 10:08 am

Code: Select all
xfs_repair -o force_geometry /dev/md4

Gives the following output...
Code: Select all
root@fvdw-sta-kirkwood:/ # xfs_repair -o force_geometry /dev/md4
unknown option -o force_geometry
Usage: xfs_repair [options] device

Options:
  -f           The device is a file
  -L           Force log zeroing. Do this as a last resort.
  -l logdev    Specifies the device where the external log resides.
  -m maxmem    Maximum amount of memory to be used in megabytes.
  -n           No modify mode, just checks the filesystem for damage.
  -P           Disables prefetching.
  -r rtdev     Specifies the device where the realtime section resides.
  -v           Verbose output.
  -c subopts   Change filesystem parameters - use xfs_admin.
  -o subopts   Override default behaviour, refer to man page.
  -t interval  Reporting interval in minutes.
  -d           Repair dangerously.
  -V           Reports version and exits.
NigelBrownless
 
Posts: 46
Joined: Mon Nov 04, 2024 2:19 pm

Re: No Volumes No Shares - Superblock Issue?

Postby fvdw » Sat Dec 21, 2024 11:07 am

funny :scratch. According manpage of xfs_repair it should be a standard option, I will need to check the source code and recompile xfs_repair to be sure that the option is available.
There is still hope.

In the meantime can you run again xfs_repair -n /dev/md4 to see if we get again same output as before.
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: No Volumes No Shares - Superblock Issue?

Postby fvdw » Sat Dec 21, 2024 11:53 am

I checked the xfs_repair version in the fvdw-sl-console is version 2.10.2 and indeed no support for force_geometry. In my archive I found version 3.2.3 and that has force geometry support.
So replace the xfs_repair binary in tftp folder of the fvdw-sl-consiole by this one and copy it over to the nas when running standalone kernel.
And repeat the command
Code: Select all
xfs_repair -o force_geometry /dev/md4
You do not have the required permissions to view the files attached to this post.
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: No Volumes No Shares - Superblock Issue?

Postby NigelBrownless » Sat Dec 21, 2024 12:22 pm

Code: Select all
xfs_repair -o force_geometry /dev/md4

Is now running.
Initial Output is....
Code: Select all
Phase 1 - find and verify superblock...
bad primary superblock - inconsistent filesystem geometry information !!!

attempting to find secondary superblock...

This is still running...
Will keep you updated.
NigelBrownless
 
Posts: 46
Joined: Mon Nov 04, 2024 2:19 pm

Re: No Volumes No Shares - Superblock Issue?

Postby NigelBrownless » Sat Dec 21, 2024 5:17 pm

Final Output...
Code: Select all
...found candidate secondary superblock...
error reading superblock 17 -- seek to offset 2123235655680 failed
unable to verify superblock, continuing...
found candidate secondary superblock...
verified secondary superblock...
writing modified primary superblock
Memory available for repair (184MB) may not be sufficient.
At least 281MB is needed to repair this filesystem efficiently
If repair fails due to lack of memory, please
turn prefetching off (-P) to reduce the memory footprint.
sb realtime bitmap inode 18446744073709551615 (NULLFSINO) inconsistent with calculated value 129
resetting superblock realtime bitmap ino pointer to 129
sb realtime summary inode 18446744073709551615 (NULLFSINO) inconsistent with calculated value 130
resetting superblock realtime summary ino pointer to 130
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.
NigelBrownless
 
Posts: 46
Joined: Mon Nov 04, 2024 2:19 pm

Re: No Volumes No Shares - Superblock Issue?

Postby NigelBrownless » Sat Dec 21, 2024 5:33 pm

I did try and do a Mount again, and it still fails with the error:
Code: Select all
mount: /dev/md4: can't read superblock


So I'm assuming I need to run xfs_repair with the -L option? And also include the -o force_geometry option. Eg...
Code: Select all
xfs_repair -o force_geometry -L /dev/md4


And should I also include the -P option to be safe?
NigelBrownless
 
Posts: 46
Joined: Mon Nov 04, 2024 2:19 pm

Re: No Volumes No Shares - Superblock Issue?

Postby fvdw » Sat Dec 21, 2024 6:07 pm

yes include the -P option
Code: Select all
xfs_repair -o force_geometry -L -P /dev/md4
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: No Volumes No Shares - Superblock Issue?

Postby NigelBrownless » Sat Dec 21, 2024 6:55 pm

It's running....
NigelBrownless
 
Posts: 46
Joined: Mon Nov 04, 2024 2:19 pm

Re: No Volumes No Shares - Superblock Issue?

Postby NigelBrownless » Sat Dec 21, 2024 11:06 pm

Output below.....Lots of Fixing Bad Flags then the following....
Code: Select all
fixing bad flags.
directory flags set on non-directory inode 2245186206
fixing bad flags.
directory flags set on non-directory inode 2245186207
fixing bad flags.
        - agno = 2
        - agno = 3
        - process newly discovered inodes...
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
        - check for inodes claiming duplicate blocks...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
Phase 5 - rebuild AG headers and trees...
        - reset superblock...
Phase 6 - check inode connectivity...
        - resetting contents of realtime bitmap and summary inodes
        - traversing filesystem ...
entry "197" (ino 2210095107) in dir 2208703968 is a duplicate name
bad hash table for directory inode 2208703968 (no leaf entry): rebuilding
rebuilding directory inode 2208703968
bad hash table for directory inode 2208704146 (no leaf entry): rebuilding
rebuilding directory inode 2208704146
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
disconnected inode 131, moving to lost+found
disconnected inode 132, moving to lost+found
disconnected inode 9052, moving to lost+found
disconnected inode 2208603440, moving to lost+found
disconnected inode 2210095107, moving to lost+found
Phase 7 - verify and correct link counts...
done
NigelBrownless
 
Posts: 46
Joined: Mon Nov 04, 2024 2:19 pm

Re: No Volumes No Shares - Superblock Issue?

Postby fvdw » Sat Dec 21, 2024 11:17 pm

well try to mount it
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

PreviousNext

Return to Lacie 2Big Network vs2

Who is online

Users browsing this forum: No registered users and 14 guests