January 2, 20206 yr I started receiving a message of Unmountable: no file system present on a drive. It was formatted and working previously. It shows the file system as xfs. What should I do to fix this?
January 2, 20206 yr Community Expert 19 minutes ago, timepants said: I started receiving a message of Unmountable: no file system present on a drive. It was formatted and working previously. It shows the file system as xfs. What should I do to fix this? This is covered here in the online documentation. If anything is unclear ask questions before proceeding as you do not want to lose data through taking inappropriate action. If asking further questions please also post your system diagnostics zip file (obtained via Tools->Diagnostics) so we can see the current state of your system.
January 2, 20206 yr Author Running the check produced this result: Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... sb_fdblocks 969459431, counted 976277671 - 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 = 1 - agno = 2 - agno = 3 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... No modify flag set, skipping filesystem flush and exiting.
January 2, 20206 yr Community Expert Run again without -n or nothing will be done, if it asks for -L use it.
January 2, 20206 yr Author Here's the result without -n Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... sb_fdblocks 969459431, counted 976277671 - 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 = 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 ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... done
January 2, 20206 yr Community Expert Now just start the array and it should mount normally, if it doesn't please post diags.
January 2, 20206 yr Author It still says Unmountable: No file system. I attached the diagnostics bundle. tower-diagnostics-20200102-1243.zip
January 2, 20206 yr Community Expert You have disk2 mounted as an unsigned device, you can't have the same disk mounted twice, though I wounder how UD mounted an array disk. Unmount the disk in UD and re-start the array, you should then run a parity check.
January 2, 20206 yr Author I'm assuming UD means Unassigned Devices? The disk does not show up under there. It is only showing under Array Devices with a green light.
January 2, 20206 yr Community Expert It is mounted: Filesystem Size Used Avail Use% Mounted on /dev/sda1 3.7T 27G 3.7T 1% /mnt/disks/ST4000DM000-1F2168_S301E7YF If you can0't unmount reboot
January 2, 20206 yr Community Expert 23 minutes ago, johnnie.black said: though I wounder how UD mounted an array disk. Was curious about this, looking at the syslog on December 13th that disk dropped offline ( or was disconnected), you then started the array without disk2, and Unraid emulated it, after that on December 31st the disk come back online and it was mounted with UD, then you used the same disk to rebuild disk2, Unraid doesn't check if disks are mounted with UD before rebuilding.
January 2, 20206 yr Author I had to remove it from the array to make it show up under UD. I unmounted it from UD. I put it back in the array. It is no longer giving the error. Thank you!
January 2, 20206 yr Community Expert Forgot to mention, USB disks are not recommend as array devices, they are prone to disconnects.
Archived
This topic is now archived and is closed to further replies.