Linux mounting failed invalid argument

mount error(22): Invalid argument

Добрый день, монтирую виндовую сетевую папку под debian 9 командой:

нельзя монтировать иерархию каталогов вроде, верным будет

mount -t cifs //

а /folder/CB потом забиндить если только.

такая же ошибка:(

Поправка, должно быть так. но все равно не работает. (

попробовал у себя, полет нормальный

sudo mount.cifs // /mnt/servak -o user=user, pass=password

mount -t cifs // /SHARE -o user=co,domain=CB,password=«Rkbtyn ( 18.10.18 09:59:28 MSK )

у меня тоже так работает на другом серваке, а тут нет=(

verbose добавьте при монтировании, может скажет что-нибудь вразумительное

mount.cifs kernel mount options: ip=,unc=\\\ExtRep,vty2019!,iocharset=utf8,user=co,domain=CB,pass=******** mount error(22): Invalid argument

похоже на то, что он воспринимает часть пароля как отдельный параметр

а на другом ПК тот же пароль при монтировании?


Mounting failed — invalid argument

I’ve setup a Kali Linux installation on an SD card and created an encrypted LUKS partition with a LVM logical volume inside of it, then created a BTRFS filesystem inside. Almost everything works, but boot fails after decrypting the LUKS volume succeeds. Logs:

It seems to fail to be able to mount my root filesystem. In the initramfs, I can actually mount the BTRFS partition just fine using all the options given in fstab. It seems to fail initially, for some strange reason that I can’t diagnose.

In the initramfs, running the following works:

Mounting works and I can see the filesystem properly.

Here’s my /etc/fstab :

Here’s my /etc/crypttab :

Here’s my kernel command line:

I’ve made sure that initramfs.gz is up to date.

Again, to reiterate, here’s my setup:

  • SD Card
    • Boot VFAT FS
    • LUKS Encrypted FS ( picrypt )
    • LVM Logical Volume ( /dev/mapper/pi-root )
      • BTRFS Filesystem
      • BTRFS Subvolume ( subvol=@ )

I have a fairly identical setup as this on my main laptop, which works fine.

During Boot, here’s what happens and then what fails:

  1. Decrypt LUKS Volume picrypt : Works
  2. Open Volume Group pi and LV root : Works
  3. Try mounting LV root via fstab: Fails with Invalid argument .

Busybox also seems to fail with not being able to access the tty, but that’s irrelevant to the problem.


«Invalid argument» when trying to mount my USB

On Ubuntu, I’m trying to mount my USB

I also tried with «-t ext4» with no success. What am I doing wrong? Thank you very much.

3 Answers 3

/dev/sdb represents the whole storage device. The individual partitions are addressed by numbers following the device name, e.g. sdb1 is the 1st partition in the storage device sdb. As USB flash drives usually have only one partition, the mount command should be:

sda or sdb is just the name of your storage device, if you want to mount it you must enter the partition number too.

Since this is among the top results I want to share some insight about what happened to me and how I solved it.

My situation is that I’m booting the 18.04 di-based server installer and I want to mount another (virtual) optical disc drive. Which gave me this exact error message.

  • I’m in a busybox shell, which may behave different than GNU tools.
  • I have a different, limited kernel running. While the error message gave no indication and all arguments seemed to be correct I tried loading the filesystem module, iso9660 in my case, with modprobe. Then it worked. So whatever filesystem you are trying to mount, you should check (lsmod?) that the respective filesystem module is loaded to. It’s unlikely that the OP was on busybox, but hey questions with not enough context are common and we are trying to solve them.


mount: mounting /dev/sda2 on /mnt/sda2 failed: Invalid argument

I’m following this tutorial. But I got stuck at step 9, somehow I’m not able to mount my USB.

Every time I try to mount my USB I get the following error:

The USB seems to be OK and connected but somehow I’m not able to mount the sda2 (ext4) partition.

The partitions seems to be OK as well:

And this is my dmesg output:

This is my fdisk -l output:

4 Answers 4

The error message comes from this line in
/fs/ext4/super.c :

The placeholder for the number in the error message is %x , so the number 400 in the actual error message is hexadecimal 0x400. And it is one if the features identified by the EXT4_FEATURE_RO_COMPAT_ constants.

The definitions for those constants can be found in
/fs/ext4/ext4.h :

The dir_nlink feature mentioned by sourcejedi is 0x20, not 0x400:

So, the MR3020 could not mount the filesystem in read/write mode because its operating system cannot handle ext4 metadata checksums. So you’ll need to turn that feature off using the Linux system you used to create the USB stick. Move the USB stick back to that system (don’t mount the ext4 filesystem) and run:

(replace X with whatever is the actual identifier of the USB stick in your Linux system.)

After running this command successfully, the metadata_csum feature will be disabled in the USB stick’s ext4 filesystem, and the MR3020 should now be able to use it.


mounting mmcblk0p1 failed with Invalid argument

When I am running linux from sd card and try to mount sd card -no problem, works fine. But when I am running linux from flash memory I am unable to mount my SD card:

What could be the basic reason for this error ?

Additional Info

5 Answers 5

As commented by goldilocks, mount -t expects the filesystem type to come after -t , so it won’t work. Otherwise it sounds like you just need to specify the filesystem type. If you don’t know the filesystem type, then there are a list of methods to find out in this answer. If the file command is available, this is probably the best method. As root you would do:

Note also that if the filesystem type is not in listed in /proc/filesystems , then the driver is not compiled into the kernel and so must be available as an external module. Once you have the correct type, you can try:

As a final thought, also make sure the /mnt directory exists! If not create it with mkdir /mnt .

Basic reasons: (updated)

1) Your system does not (properly?) initialize or does not recognize the SD when booting from flash. Is there the /dev/mmcblk0 device after you boot from flash? What does fdisk -l /dev/mmcblk0 say?

2) There is no file system on /dev/mmcblk0p1, you need to create a file system first ( mkfs . ). Check with file -s /dev/mmcblk0p1

3) The file system on /dev/mmcblk0p1 is corrupted, you need to check / repair it, try fsck /dev/mmcblk0p1 , or create a new one

4) Your kernel (when booting from flash) does not have the needed file system driver, check cat /proc/filesystems and ls «/lib/modules/$(uname -r)/kernel/fs/» and see if that list contains the needed file system type. Typically, older kernels don’t support ext4, while your OS might already have tools to create an ext4 file system.

5) Hardware defect — could be the SD card, the controller, wiring . but if it works when booting from the SD card then this is most probably not the case.