2016-01-30 Mount Failure Problem resolution
[Email protected] ~]# MOUNT/DEV/SDC/DTA
Mount:you must specify the filesystem type
[Email protected] ~]#
[Email protected] ~]# mount-t ext4/dev/sdc1/data
Mount:wrong fs type, bad option, bad Superblock ON/DEV/SDC1,
Missing codepage or helper program, or other error
In some cases useful info are found in Syslog-try
DMESG | Tail or so
[[email protected] ~]# cat/proc/filesystemsnodev sysfsnodev rootfsnodev bdevnodev procnodev Cgroupnodev Cpusetnodev tmpfsnodev devtmpfsnodev binfmt_miscnodev debugfsnodev securityfsnodev sockfsnodev Usbfsnodev Pipefsnodev anon_inodefsnodev inotifyfsnodev devptsnodev ramfsnodev hugetlbfs iso9660nodev pstorenodev m Queuenodev selinuxfs Ext4nodev autofs[[email protected] ~]# View the file formats supported in the background, where 2.6.32-431.29.2.el6.x86_64 directories vary depending on the system version find/lib/modules/-name Kernel command to find out the real directory [[email protected] ~]# ll/lib/modules/2.6.32-431.29.2.el6.x86_64 /kernel/fstotal 132drwxr-xr-x. 2 root root 4096 Sep autofs4drwxr-xr-x. 2 root root 4096 Sep btrfsdrwxr-xr-x. 2 root root 4096 Sep cachefilesdrwxr-xr-x. 2 root root 4096 Sep cifsdrwxr-xr-x. 2 root root 4096 Sep configfsdrwxr-xr-x. 2 root root 4096 Sep cramfsdrwxr-xr-x. 2 root root 4096 Sep dlmdrwxr-xr-x. 2 root root 4096 Sep Ecryptfsdrwxr-xr-x. 2 root root 4096 Sep exportfsdrwxr-xr-x. 2 root root 4096 Sep ext2drwxr-xr-x. 2 root root 4096 Sep ext3drwxr-xr-x. 2 root root 4096 Sep ext4drwxr-xr-x. 2 root root 4096 Sep fatdrwxr-xr-x. 2 root root 4096 Sep fscachedrwxr-xr-x. 2 root root 4096 Sep fusedrwxr-xr-x. 2 root root 4096 Sep gfs2drwxr-xr-x. 2 root root 4096 Sep jbddrwxr-xr-x. 2 root root 4096 Sep jbd2drwxr-xr-x. 2 root root 4096 Sep jffs2drwxr-xr-x. 2 root root 4096 Sep lockd-rwxr--r--. 1 root root 19920 Sep 9 mbcache.kodrwxr-xr-x. 2 root root 4096 Sep nfsdrwxr-xr-x. 2 root root 4096 Sep nfs_commondrwxr-xr-x. 2 root root 4096 Sep nfsddrwxr-xr-x. 2 root root 4096 Sep nlsdrwxr-xr-x. 2 root root 4096 Sep squashfsdrwxr-xr-x. 2 root root 4096 Sep ubifsdrwxr-xr-x. 2 root root 4096 Sep udfdrwxr-xr-x. 2 root RoOT 4096 Sep xfs[[email protected] ~]# View the file format for this system: [[email protected] ~]# df-t-hfilesystem Type Size used Avail use% mounted on/dev/sda1 ext4 29G 2.8G 25G 11%/tmpfs tmpfs 14G 0 14G 0%/ DEV/SHM/DEV/SDB1 ext4 56G 180M 53G 1%/mnt/resource[[email protected] ~]# fdisk/dev/sdc, appears/dev/sdc1dis k/dev/sdc:53.7 GB, 53687091200 bytes255 heads, sectors/track, 6527 cylindersunits = cylinders of 16065 * 512 = 822528 0 bytessector size (logical/physical): bytes/512 bytesi/o size (minimum/optimal): bytes/512 bytesdisk IdentiFi er:0x4cb42802 Device Boot Start End Blocks Id system/dev/sdc1 1 6527 52428 096 linux[[email protected] ~]# has an input w command is the write disk file initialization, if unsuccessful, execute mkfs.ext4/dev/sdc1mkfs.ext4/dev/sdc1[[ Email protected] ~]# mkfs.ext4/dev/sdc1mke2fs 1.41.12 (17-may-2010) Filesystem Label=os type:linuxblock size=4096 (log=2) Fragment size=4096 (log=2) stride=0 blocks, Stripe width=0 blocks3276800 inodes, 13107024 blocks655351 blocks (5.00%) reserved for the Super Userfir St Data block=0maximum filesystem blocks=4294967296400 block groups32768 blocks per group, 32768 fragments per group8192 I Nodes per groupsuperblock backups stored on blocks:32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 265 4208, 4096000, 7962624, 11239424Writing inode tables:done Creating Journal (32768 blocks): Donewriting superblocks and filesystem accounting information:donethis filesystem would be automatically checked every 37 Mounts or180 days, whichever comes first. Use Tune2fs-c or-i to override. [[email protected] ~]# [[email protected] ~]# mount/dev/sdc1/data[[email protected] ~]# df-t- Hfilesystem Type Size used Avail use% mounted on/dev/sda1 ext4 29G 2.4G 25G 9%/tmpfs TMPFS 14G 0 14G 0%/dev/shm/dev/sdb1 ext4 56G 180M 53G 1%/mnt/RESOURCE/DEV/SDC1 ext4 50G 180M 47G 1%/data[[email protected] ~]# PS: Users of the program Super Block corruption, but the file system has a super block backup, only need to re-restore The super block is ready. Mkfs.ext4-n device The command is best to be the backup location of the Super block Mkfs.ext4-b Superblocknum device that's it. To enable mount to take effect after restarting the VM, you also need to configure/etc/fstabvim/ Etc/fstab/dev/sdc/data EXT4 Defaults 1 2 Restart, the Could not chdir to home Directo appears Ry/home/adminuser:no such file or directory error is due to/etc/fstab inside configuration error
Mount:wrong FS Type in Azure Cloud, bad option, bad Superblock ON/DEV/SDC1