April 11, 20233 yr Hi support, I went out for a short trip few days back and when I got home my Unraid is not working properly. On the dashboard i see error "unountable wrong or no file system" and i see unmountable disk present DISK 1. I have only 1 parity and DISK 1. Here is the diagnostic. How do i get back all the drive working? Noob here so please bear with me. komandos-diagnostics-20230411-2044.zip
April 11, 20233 yr Author 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 ignored because the -n option was used. Expect spurious inconsistencies which may be resolved by first mounting the filesystem to replay the log. - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - 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 = 3 - agno = 1 - agno = 2 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... Maximum metadata LSN (2:233724) is ahead of log (2:233045). Would format log to cycle 5. No modify flag set, skipping filesystem flush and exiting. this is the status with -n Edited April 11, 20233 yr by safiedin
April 11, 20233 yr Community Expert Run it again without -n or nothing will be done, and if it asks for it use -L.
April 11, 20233 yr Author 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... clearing needsrepair flag and regenerating metadata - 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 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 2 - agno = 3 - agno = 1 clearing reflink flag on inodes when possible 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 (2:233777) is ahead of log (1:2). Format log to cycle 5. done whats the next step sir Edited April 11, 20233 yr by safiedin
April 11, 20233 yr Author it seems to work now. thanks very much. but i lost all my vm. dont know why. how do i fix it?
April 11, 20233 yr Community Expert Are they missing from the VM page or they don't work? Also post new diags.
April 11, 20233 yr Author it says no virtual machine installed. i went to setting - vm manager. tried few directory that it was installed previously but cant seem to find it. but i dont remember the directory (default) that i had in there. anyway that we can browse the vm setting previously?
April 11, 20233 yr Community Expert A new libvirt.img was created, meaning the old is missing or not in the correct place: Apr 12 00:45:34 komandos root: Creating new image file: '/mnt/maindrive/system/libvirt.img' size: 1G Post the output of: find /mnt -name libvirt.img
April 11, 20233 yr Author /mnt/user/system/libvirt/libvirt.img /mnt/user/system/libvirt.img /mnt/user/libvirt.img /mnt/maindrive/system/libvirt/libvirt.img /mnt/maindrive/system/libvirt.img /mnt/maindrive/libvirt.img how to get the date ? so many how about Default VM storage path: Default ISO storage path: Edited April 11, 20233 yr by safiedin
April 11, 20233 yr Community Expert 15 minutes ago, safiedin said: /mnt/maindrive/system/libvirt.img This is the one you are using, try: 15 minutes ago, safiedin said: /mnt/maindrive/system/libvirt/libvirt.img and 15 minutes ago, safiedin said: /mnt/maindrive/libvirt.img To see if any of these has your VMs (the ones under /mnt/user are the same), also note that you should always have a current backup of this file.
April 12, 20233 yr Author i found it again thanks for your advice. That libvirt.img is it enough for 1 GB size. or should we increase it? or in what situation does it need to be increase more then 1gb. I am planning to delete all libvirt and start a clean vm file.
April 12, 20233 yr Community Expert 9 hours ago, safiedin said: That libvirt.img is it enough for 1 GB size. or should we increase it? or in what situation does it need to be increase more then 1gb That only holds small files related to VMs and their configuration. I would think in practice 100MB is more than enough so you should never outgrow the default 1GB unless you have hundreds of VMs.
April 12, 20233 yr Author OK thanks for the information On the dashboard - main why doesnt it shows used and free space for the parity?
April 12, 20233 yr Author also why it doesnt show any disk share. i still have access to folders on users created. i thought its suppose to show here
April 12, 20233 yr Community Expert Disk shares are disabled by default, you can enable on Settings -> Global Share Settings, but be aware of this: https://wiki.unraid.net/Manual/Shares#Disk_Shares
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.