Astra linux mount wrong fs type

Mount: wrong fs type, bad option, bad superblock on /dev/mapper/VolGroup-lv_home

[root@localhost local]# dmesg | tail type=1305 audit(1548343606.632:3): audit_pid=3415 old=0 auid=4294967295 ses=4294967295 res=1 EXT4-fs (dm-2): bad geometry: block count 228899840 exceeds size of device (26214400 blocks) usb 3-1: USB disconnect, device number 2 possible SYN flooding on port 22. Sending cookies. possible SYN flooding on port 22. Sending cookies. possible SYN flooding on port 22. Sending cookies. possible SYN flooding on port 22. Sending cookies. possible SYN flooding on port 22. Sending cookies. EXT4-fs (dm-2): bad geometry: block count 228899840 exceeds size of device (26214400 blocks) EXT4-fs (dm-2): bad geometry: block count 228899840 exceeds size of device (26214400 blocks) 

[root@localhost local]# history 1 yum -y install screen 2 screen -S lnmp 3 cd /usr/local/nginx/conf/vhost/ 4 ll 5 vi www.SDFS.com.conf 6 lsblk 7 ls 8 cd /home/ 9 ls 10 cd /dev/VolGroup/ 11 ls 12 cd lv_home 13 ls 14 cd lv_root 15 df -h 16 fdisl -l 17 fdisk -l 18 cat /etc/mtab 19 mount /dev/VolGroup/lv_home /home/ 20 fsck -t ext4 /dev/mapper/VolGroup-lv_home 21 mount /dev/VolGroup/lv_home /home/ 22 ls 23 cd 24 ls 25 cd / 26 ls 27 cd usr/local/ 28 ls 29 cd mysql/ 30 ls 31 cd .. 32 ls 33 cd nginx/ 34 ls 35 cd html/ 36 ls 37 cd .. 38 ls 39 cd .. 40 ls 41 cd src/ 42 ls 43 cd .. 44 ls 45 cd .. 46 ls 47 cd tmp/ 48 ls 49 cd .. 50 ls 51 cd .. 52 ls 53 cd mnt/ 54 ls 55 cd .. 56 ls 57 cd dev/ 58 ls 59 cd .. 60 ls 61 cd opt/ 62 ls 63 cd .. 64 ls 65 cd root/ 66 ls 67 cd .. 68 ls 69 cd media/ 70 ls 71 cd ,, 72 ls 73 cd ..ls 74 cd .. 75 ls 76 cd lost+found/ 77 ls 78 cd .. 79 ls 80 cd root/ 81 ls 82 cd .. 83 ls 84 cd home/ 85 ls 86 cd .. 87 ls 88 cd usr/ 89 ls 90 cd include/ 91 ls 92 cd .. 93 ls 94 cd src/ 95 ls 96 cd .. 97 ls 98 cd .. 99 ls 100 cd lib 101 ls 102 cd .. 103 ls 104 cd usr/local/ 105 ls 106 mysql -u root 107 mysql -u root -p 108 df -hT 109 mount 110 grep /home /etc/fstab 111 fdisk -l 112 cd /dev/mapper/VolGroup-lv_home 113 dmesg | tail 114 lsblk 115 history 

Источник

Смоленск 1.5 Добавление USB накопителей (FAT)

Добрый день!
Не монтируется USB флеш накопитель фс Fat под пользователем.

Появляется сообщение «Mount failed mount wrong fs type. »
Накопитель добавлен с 0 уровнем МРД, разрешен для чтения, записи и выполнения всем пользователям.
Процесс монтирования и ошибка представлены на скринах во вложении.

Аркадий Слепов

Moderator

Pavel

New member

# /etc/fstab: static file system information.
#
# Use ‘blkid’ to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
#
# / was on /dev/sda1 during installation
UUID=7d25a062-fafa-44a8-81bb-7b4c0cbddd45 / ext4 errors=remount-ro,secdel=2 0 1
# swap was on /dev/sda5 during installation
UUID=7439aafb-5834-4823-a1de-6c25756abae7 none swap sw 0 0
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
# /etc/fstab.d/PDAC: parsec devices access control mount instructions
#
#
### usb flash
/dev/*fat /*home/*/media/* auto owner,group,noauto,nodev,noexec,iocharset=utf8,defaults,secdel=2 0 0
/dev/*ntfs* /*home/*/media/* auto owner,group,noauto,nodev,noexec,iocharset=utf8,defaults,secdel=2 0 0
/dev/sd*ext* /*home/*/media/* auto owner,group,nodev,noexec,noauto,defaults,secdel=2 0 0
### [cd|dvd|bd]rom
/dev/s*udf /*home/*/media/* udf owner,group,nodev,noexec,noauto,defaults 0 0
/dev/s*iso9660 /*home/*/media/* iso9660 owner,group,nodev,noexec,noauto,defaults 0 0
### other
/dev/sd* /*home/*/media/* auto owner,group,nodev,noexec,noauto,iocharset=utf8,defaults,secdel=2 0 0

Источник

Wrong fs type, bad option, bad superblock on /dev/sdaX

I am trying to create an automated mount for an external hard drive, but it keeps failing. I am a little newbiew at linux. I have googled and searched in StackExchange and I tried a lot of things, but I did not find a solution for my problem. OS: Raspbian Stretch Those are the steps I did:

Format external drive to ext4

sudo mkfs.ext4 /dev/sda1 -L hdd_moc mke2fs 1.43.4 (31-Jan-2017) /dev/sda1 contains a ext4 file system labelled 'hdd_owncloud' last mounted on Mon Feb 12 09:34:38 2018 Proceed anyway? (y,N) y Creating filesystem with 244181760 4k blocks and 61046784 inodes Filesystem UUID: b9b47e44-db76-40de-a0ed-940c9699799a Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, 102400000, 214990848 Allocating group tables: done Writing inode tables: done Creating journal (262144 blocks): done Writing superblocks and filesystem accounting information: done 

Create directory for mounted external usb drive

Create the www-data user to the group

sudo groupadd www-data sudo usermod -a -G www-data www-data 

Give permissions

sudo chown -R www-data:www-data /mnt/hdd_moc sudo chmod -R 775 /mnt/hdd_moc ls -l /mnt total 4 drwxrwxr-x 2 www-data www-data 4096 Feb 12 10:06 hdd_moc 

Get the gid, uid and uuid

id -g www-data 33 id -u www-data 33 ls -l /dev/disk/by-uuid total 0 lrwxrwxrwx 1 root root 15 Feb 12 09:49 9a7608bd-5bff-4dfc-ac1d-63a956744162 -> ../../mmcblk0p2 lrwxrwxrwx 1 root root 15 Feb 12 09:49 B60A-B262 -> ../../mmcblk0p1 lrwxrwxrwx 1 root root 10 Feb 12 10:12 b9b47e44-db76-40de-a0ed-940c9699799a -> ../../sda1 

Give the instruction to fstab

sudo nano /etc/fstab proc /proc proc defaults 0 0 PARTUUID=ed7ab5b3-01 /boot vfat defaults 0 2 PARTUUID=ed7ab5b3-02 / ext4 defaults,noatime 0 1 UUID=b9b47e44-db76-40de-a0ed-940c9699799a /mnt/hdd_moc auto nofail,uid=33,gid=33,umask=0027,dmask=0027,noatime 0 0 

Automated mount test

sudo mount -a mount: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. 

Normal mount test

sudo mount /dev/sda1 /mnt/hdd_moc -> It works, I can do a "ls". 

Источник

Wrong fs type, bad option, bad superblock on /dev/sdX [closed]

Do you expect there to be something on the disk (e.g., you’re moving it from another computer) or is it reasonable that there might be no files on it (e.g., it’s brand new from the store). If it’s brand new, you need to mkfs before you can mount it for the first time.

There is data on the disk. This is an error that suddenly occured. Will add the output of ´file´ tonight.

2 Answers 2

sudo mount /dev/sdc /mnt/harddrive 

mount: /mnt/harddrive: wrong fs type, bad option, bad superblock on /dev/sdc, missing codepage or helper program, or other error. 

This error isn’t surprising: you can only mount a filesystem (which usually resides on a partition like /dev/sdx1 ), but here you’re trying to mount the entire disk ( /dev/sdx ).
Hence the error «wrong fs type […]»: there is no filesystem at the location you have specified.

sudo mount /dev/sdc1 /mnt/harddrive 

Here, you’re specifying a partition, which may (or may not) contain a filesystem.
Based on the information in the partition table (that you have looked at using fdisk -l ), the kernel assumes there should be an NTFS on this partition and loads the relevant kernel module to mount it. That module then fails to mount the NTFS and reports a few errors along the way.

This can mean one of several things:

• There is an NTFS on the partition, but it is damaged.
  In that case, try recovering it from a Windows machine like Micheal suggested.
• There is a different filesystem on there which is not natively supported by Linux (e.g. exFAT).
  In that case, you may be able to install third-party software to mount the filesystem. You should, however, check which filesystem is actually on the drive before randomly installing and trying things.
• There is no filesystem at all; the entry in the partition table is just misleading.
  In that case, there is nothing to lose: just format the partition with a filesystem of your choice and change the filesystem type in the partition table accordingly.

Источник

How to Fix “Wrong Fs Type, Bad Option, Bad Superblock” Error?

When a Linux user mounts a filesystem, then they might have come across the “Wrong Fs Type, Bad Option, Bad Superblock” error. This can be troublesome, especially if someone is not familiar with Linux filesystem management.

In this article, the common causes of this error will be explained in detail by discussing the below outline.

• Reason: Unsupported Filesystem or Incorrect Mount Options
• Solution: Fixing the “Wrong Fs Type, Bad Option, Bad Superblock” Error
• Step 1: Identify the Affected Filesystem
• Step 2: Check the Filesystem Type
• Step 3: Check the Mount Options
• Step 4: Check the Superblock
• Step 5: Mount the Filesystem

Reason: Unsupported Filesystem or Incorrect Mount Options

The “Wrong Fs Type, Bad Option, Bad Superblock” error occurs when the system tries to mount a filesystem with an unsupported filesystem type or incorrect mount options. It can also be caused by a damaged or corrupted superblock containing critical information about the filesystem.

If a user encounters this error, they cannot access the data on the affected filesystem, so the solution to resolve this problem is explained below.

Solution: Fixing the “Wrong Fs Type, Bad Option, Bad Superblock” Error

The solution to resolve this error depends on multiple steps, which are as follows:

Step 1: Identify the Affected Filesystem

The first step in fixing this error is to identify the affected filesystem. This can be done by running the mount command as shown below:

This will display a list of all mounted filesystems on a system, and a user needs to look for the filesystem that is causing the error.

Step 2: Check the Filesystem Type

Once users have identified the affected filesystem, the next step is to check its filesystem type. This can be done by running the blkid command followed by the device name of the filesystem. Let’s assume that the affected filesystem is /dev/sda3, so to check its filesystem type, a user need to run the following command in the terminal:

Step 3: Check the Mount Options

After identifying the filesystem type, the next step is to check the mount options, which can be done by looking at the /etc/fstab file. Make sure that the mount options are correct for the filesystem type.

Step 4: Check the Superblock

If the filesystem type and mount options are correct, the next step is to check the superblock. A user can do this by running the fsck command followed by the device name of the filesystem. This command will scan the filesystem for errors and repair any damaged superblocks.

Step 5: Mount the Filesystem

Once a user follows the above steps properly and resolves any error, they should try to mount the filesystem again using the mount command. If the mount is successful, A user should be able to access their data.

Conclusion

The user normally faces the “Wrong fs type, bad option, bad superblock” error by mounting a file system, and resolving it can be a challenging issue. Some of the most common causes have been discussed in this article, along with the solution to resolve this error.

Источник