[SOLVED] luksOpen device-mapper reload ioctl failed invalid argument

Hello,
I don't know what things I have problem.
Have You any idea?
What I need to do?
$ sudo cryptsetup luksOpen /dev/sr0 dvd
Jelszó:
Enter passphrase for /dev/sr0:
device-mapper: reload ioctl failed: invalid argument
$ sudo cryptsetup luksDump /dev/sr0
LUKS header information for /dev/sr0
Version: 1
Cipher name: aes
Cipher mode: cbc-essiv:sha256
Hash spec: sha1
Payload offset: 2056
MK bits: 256
MK digest: b5 3e d0 e4 d4 e0 ed 52 25 68 88 af 74 01 90 a7 a7 e2 50 19
MK salt: 74 8e 97 56 48 b8 ad eb a9 dc 18 85 e3 a2 e9 03
7a 87 0d df d9 e3 04 e1 87 6e ce c8 3a f5 1d 6d
MK iterations: 15375
UUID: 1ef0225c-328f-4531-9d76-7259dd381960
$ cat /proc/crypto
name : sha256
driver : sha256-generic
module : sha256_generic
priority : 0
refcnt : 1
selftest : passed
type : shash
blocksize : 64
digestsize : 32
name : sha224
driver : sha224-generic
module : sha256_generic
priority : 0
refcnt : 1
selftest : passed
type : shash
blocksize : 64
digestsize : 28
name : cbc(aes)
driver : cbc(aes-asm)
module : kernel
priority : 200
refcnt : 1
selftest : passed
type : givcipher
async : no
blocksize : 16
min keysize : 16
max keysize : 32
ivsize : 16
geniv : eseqiv
name : cbc(aes)
driver : cbc(aes-asm)
module : cbc
priority : 200
refcnt : 1
selftest : passed
type : blkcipher
blocksize : 16
min keysize : 16
max keysize : 32
ivsize : 16
geniv : <default>
name : aes
driver : aes-asm
module : aes_i586
priority : 200
refcnt : 1
selftest : passed
type : cipher
blocksize : 16
min keysize : 16
max keysize : 32
name : aes
driver : aes-generic
module : aes_generic
priority : 100
refcnt : 1
selftest : passed
type : cipher
blocksize : 16
min keysize : 16
max keysize : 32
name : stdrng
driver : krng
module : kernel
priority : 200
refcnt : 2
selftest : passed
type : rng
seedsize : 0
Last edited by gyurman (2011-12-03 11:54:18)

Have you tried:
sudo cryptsetup -r luksOpen /dev/sr0 dvd

Similar Messages

LUKS/dmcrypt device-mapper error

Hi,
Ok this is a strange one because I have several encrypted volumes already in use working fine, yet im having problems creating a new LUKS container with cryptsetup on a new USB hard drive.
Just using standard AES in XTS mode, and all the required kernel modules (dmcrypt/aes) are loaded.
[root@tcore media]# cryptsetup -c aes-xts-plain -y -s 512 luksFormat /dev/sdf1
WARNING!
========
This will overwrite data on /dev/sdf1 irrevocably.
Are you sure? (Type uppercase yes): YES
Enter LUKS passphrase:
Verify passphrase:
device-mapper: reload ioctl failed: Invalid argument
Failed to setup dm-crypt key mapping for device /dev/sdf1.
Check that kernel supports aes-xts-plain cipher (check syslog for more info).
This is /dev/sdf:
Disk /dev/sdf: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdf1 63 488392064 244196001 83 Linux
Any ideas? As my kernel clearly does support the cipher. Possibly a USB issue as all my other volumes are on internal SATA drives?
EDIT: on some attempts the error varies and also shows: device-mapper: remove ioctl failed: Device or resource busy
Last edited by tntcoda (2010-09-30 12:31:00)

Ehm..I am trying to mount the device (/dev/sdb3), not the mapper! Although I can see that with file-based truecrypt container the mapper gets mounted. Shan't truecrypt create the mapper and mount that for me in case I select a device?
This is the information of the two mappings created (2_0 and 2_1 since I had already mounted a file-based container):
Name: truecrypt2_0
State: ACTIVE
Read Ahead: 256
Tables present: LIVE
Open count: 0
Event number: 0
Major, minor: 254, 2
Number of targets: 1
Name: truecrypt2_1
State: ACTIVE
Read Ahead: 256
Tables present: LIVE
Open count: 1
Event number: 0
Major, minor: 254, 1
Number of targets: 1
None of them gets mounted after I get the mentioned error; maybe truecrypt is expecting a dm feature which I have not enabled in my kernel?

Cannot mount Truecrypt volume (device-mapper error)

I have a 1TB external USB disk (externally powered) and I have created 3 partitions on it:
Disk /dev/sdb: 1000.2 GB, 1000202043392 bytes
255 heads, 63 sectors/track, 121600 cylinders, total 1953519616 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 2048 696322047 348160000 7 HPFS/NTFS
/dev/sdb2 1683384320 1744824319 30720000 83 Linux
/dev/sdb3 1744824320 1953517567 104346624 7 HPFS/NTFS
The last partition, /dev/sdb3, has been formatted with Truecrypt 7.0a and I'd like to mount it, but truecrypt reports the following error:
device-mapper: reload ioctl failed: No such file or directory
Command failed
I am getting the same error with my custom kernel and with stock Arch Linux kernel; what can it be? Can somebody please help me to narrow down this issue?
Thanks

Ehm..I am trying to mount the device (/dev/sdb3), not the mapper! Although I can see that with file-based truecrypt container the mapper gets mounted. Shan't truecrypt create the mapper and mount that for me in case I select a device?
This is the information of the two mappings created (2_0 and 2_1 since I had already mounted a file-based container):
Name: truecrypt2_0
State: ACTIVE
Read Ahead: 256
Tables present: LIVE
Open count: 0
Event number: 0
Major, minor: 254, 2
Number of targets: 1
Name: truecrypt2_1
State: ACTIVE
Read Ahead: 256
Tables present: LIVE
Open count: 1
Event number: 0
Major, minor: 254, 1
Number of targets: 1
None of them gets mounted after I get the mentioned error; maybe truecrypt is expecting a dm feature which I have not enabled in my kernel?

I8kbuttons: ioctl failed

I've been trying to get the volume buttons of my Dell Latitude D830 to work. I installed i8kutils and tried an approach using amixer. I've also installed aumix to try the example in the i8kbuttons man page. I keep getting things like this:
[user@system ~]$ i8kbuttons -u "aumix -v +10" -d "aumix -v -10" -m "aumix -v 0" -r 100 -v
i8kbuttons v1.3 07/11/2001 - Copyright (C) Massimo Dal Zotto <[email protected]>
ioctl failed: Invalid argument
Does anyone have a clue? I'm running acpid as well, though I'm not too sure whether it's needed. Running i8kbuttons as root doesn't seem to make any difference.
Update:
Somehow I'd managed to overlook the fact that, since I run GNOME, I can simply add the volume control buttons to the appropriate shortcuts in GNOME's "Keyboard Shortcuts".
The problem isn't really solved though, because i8kbuttons still doesn't work. But at least I'm happy.
Last edited by ppvg (2007-11-02 13:07:16)

I have the same problem but am using dwm, so i have no real way of doing this without ioctl. does anyone know whats wrong here?
-Tj

How save is dmcrypt? / ...invalid argument [solved]

Greetings,
i plan to crypt all my partitions with dmcrypt.
my question would be: how save is it?
is it a big efford to encode a crypted partition if you dont have the paraphrase?
EDIT:
great...i just tried to make an crypted partition with:
cryptsetup -y create daten2 /discs/disc1/part1
but i get an:
Command failed: invalid argument
if i try the same in verbose mode, the error is this:
Command failed: device-mapper ioctl cmd 9 failed: Invalied Argument
would be pleased if someone could help me out in some way.

Greetings,
sorry, but i solved the problem by myself :-D
the failure was, that the disk i tried, had still a partition.
after i deleted that one, everything worked.

My AP execute ioctl(handle,command,&arg) got invalid argument

Hi Dear All,
I have coding one user space program.
It send my private control code to my scsi adapter driver.
But I got invalid argument when my program execute ioctl.
Does anyone know that if solaris has its command limit as FreeBSD or &arg spec.
typedef struct CMDIO_CONTROL
uint32_t HeaderLength;
uint8_t Signature[8];
uint32_t Timeout;
uint32_t ControlCode;
uint32_t ReturnCode;
uint32_t Length;
} CMD_IO_CONTROL,*PCMD_IO_CONTROL;
typedef struct CMDIOCTL_FIELD
CMD_IO_CONTROL                          cmdioctl; /*ioctl header*/
uint8_t                     ioctldatabuffer[224];/*areca gui program does not accept more than 1031 byte*/
} CMD_IOCTL_FIELD,*PCMD_IOCTL_FIELD;
/*FunctionCode*/
#define FUNCTION_READ_RQBUFFER      0x0001
#define FUNCTION_WRITE_WQBUFFER      0x0002
#define FUNCTION_CLEAR_RQBUFFER      0x0003
#define FUNCTION_CLEAR_WQBUFFER      0x0004
#define FUNCTION_CLEAR_ALLQBUFFER      0x0005
#define FUNCTION_RETURN_CODE_3F      0x0006
#define FUNCTION_SAY_HELLO      0x0007
#define FUNCTION_SAY_GOODBYE 0x0008
#define     DEVCTL_IOC          (0xDC << 16)
#define ARCMSR_IOCTL_READ_RQBUFFER      (DEVCTL_IOC | 1)
#define ARCMSR_IOCTL_WRITE_WQBUFFER      (DEVCTL_IOC | 2)
#define ARCMSR_IOCTL_CLEAR_RQBUFFER      (DEVCTL_IOC | 3)
#define ARCMSR_IOCTL_CLEAR_WQBUFFER      (DEVCTL_IOC | 4)
#define ARCMSR_IOCTL_CLEAR_ALLQBUFFER      (DEVCTL_IOC | 5)
#define ARCMSR_IOCTL_REQUEST_RETURNCODE_3F      (DEVCTL_IOC | 6)
#define ARCMSR_IOCTL_SAY_HELLO      (DEVCTL_IOC | 7)
#define ARCMSR_IOCTL_SAY_GOODBYE (DEVCTL_IOC | 8)
          if(file_handle=open(arcmsr_device_path_name, O_RDWR ) < 0)
               perror("watchdog:open file fail");
          else
               printf("arcmsr watchdog:open %s ok \n",arcmsr_device_path_name);
          memcpy(arcmsr_ioctl_field.cmdioctl.Signature, ustring, strlen(ustring));
          arcmsr_ioctl_field.cmdioctl.ControlCode=ARCMSR_IOCTL_SAY_GOODBYE;
          arcmsr_ioctl_field.cmdioctl.Length=sizeof(struct CMDIOCTL_FIELD);
printf("file_handle:%x \n",file_handle);
          printf("Signature:%s \n",(char *) &arcmsr_ioctl_field.cmdioctl.Signature);
          printf("ControlCode:%x \n",arcmsr_ioctl_field.cmdioctl.ControlCode);
printf("Length:%x \n",arcmsr_ioctl_field.cmdioctl.Length);
          if (ioctl(file_handle, ARCMSR_IOCTL_SAY_GOODBYE, &arcmsr_ioctl_field) == SYSERR)
               printf("errno=%x \n",errno);
               printf("strerror=%s \n",strerror(errno));
               perror("watchdog:ioctl fail");
          else
printf("arcmsr watchdog:say goodbye to %s raid adapter complete \n",arcmsr_device_path_name);
          }

Hi Dear All,
The following description is my dump message.
# ./watchdog
watchdog:adapter=/devices/pci@0,0/pci8086,2543@2/pci8086,1460@1f/pci8086,335@6/p
ci17d3,1120@e:pci17d3,1120
arcmsr watchdog:open /devices/pci@0,0/pci8086,2543@2/pci8086,1460@1f/pci8086,335
@6/pci17d3,1120@e:pci17d3,1120 ok
file_handle:0
Signature:arcmsr ustring=arcmsr
ControlCode:6308
Length:1c
errno=16
strerror=Invalid argument
watchdog:ioctl fail: Invalid argument

[solved] Upgrade failing for a package called device-mapper

Hi All,
I am using archlinux in a VirtualBox to get used to it. Now, I tried to upgrade (after a month or so) with following command
pacman -Syu
I get following errors
error: failed to commit transaction (invalid or corrupted package)
device-mapper-1.02.31-1-i686.pkg.tar.gz is invalid or corrupted
Errors occurred, no packages were upgraded
Any help is welcome.
regards,
rangalo
Last edited by rangalo (2009-04-22 09:32:48)

Hi,
Thanks for the quick response... I am given the choice to remove the package but it still complains about it being corrupted..
I also deleted it manually and running the update again gives following.
:: File device-mapper-1.02.31-1-i686.pkg.tar.gz is corrupted. Do you want to delete it? [Y/n] Y
error: failed to commit transaction (invalid or corrupted package)
device-mapper-1.02.31-1-i686.pkg.tar.gz is invalid or corrupted
Errors occurred, no packages were upgraded.
Last edited by rangalo (2009-04-21 14:32:35)

[SOLVED] Device mapper problem with LVM

I'm trying to mount an LVM partition using the archie livecd (ie kernel 2.6.13). I've installed lvm2 and device-mapper (1.01.05) but although vgscan gives:
[root@localhost archie]# vgscan
Reading all physical volumes. This may take a while...
Found volume group "vg1" using metadata type lvm2
vgchange gives:
[root@localhost archie]# vgchange -a y
/proc/misc: No entry for device-mapper found
Is device-mapper driver missing from kernel?
Failure to communicate with kernel device-mapper driver.
0 logical volume(s) in volume group "vg1" now active
Any suggestions?

Solved it.
Should have installed the appropriate module:
# modprobe dm_mod
# dmsetup ls
now lists the correct virtual devices.

Fssnap fails by "fssnap: ioctl: error 22: Invalid argument" because of xntp

Hi,
on cluster node fssnap -F ufs -o bs=/xxxx /
fails by "fssnap: ioctl: error 22: Invalid argument" because of xntpd_cluster service.
Is there any workaround?
Many thanks
Ushas Symon

I don't know if we support fssnap on anything other than the root file system because of its interaction with the system and potential to lock file systems for brief periods. If this is on the root file system then may be you could stop and start xntpd_cluster briefly while the snap is being taken.
Of course, the better option would be to upgrade to SC3.2 01/09 and use ZFS for the root file system. I believe support for ZFS boot just squeezed in at the last minute thanks to some excellent work by some of my QA colleagues.
Regards,
Tim
---

Thanks this was very useful.. I have a brand new iphone 4s unlocked version from singapore and I am having the same problem constant network fluctuations, no service, call failed, invalid sim, sim failure, bars fluctuating from 5 - 3 - 2 - 1, no signal/ba

I have a brand new iphone 4s unlocked version from singapore and I am experiencing constant network fluctuations on my iphone , no service, call failed, invalid sim, sim failure, bars fluctuating from 5 - 3 - 2 - 1, no signal/bars searching etc... Ifeel miserable after trying out all the options changed multiple sims, tried multiple carriers, restored the phone back and have set-up as new device but the problem does not get solved... its is so frustrating that after investing on a world's most expensive phone you cannot enjoy the calling features which the phone offers which is the main thing you own the phone for.. Rest of the things are working.. The funniest part I am not able to make calls or receive calls but can access the internet.. I have tried every possible thing and really very frustrated with this iphone of mine...I hope the problem gets solved.. would anyone have any solutions to this problem.. Does it mean one should never update software as I hear that after updating to IOS.5.1 the problem has started coming and same has been with there.... Apple says its a hardware failure which is very difficult to digest as sometimes I get 5 bars and able to make and receive calls but 95% of the time I am unable to. If anyone has any solution I will be very happy if he or share can share the same. Many thanks. its so disgusting to experience this on top of this apple does not support global warranty for the phone as you need to go to the country from where you bought the phone for replacement.. Truly sad state of affairs.. very very very dissappointing.

Have a look at this it might help
http://support.apple.com/kb/TS4148

[solved] docker: Error mounting: invalid argument

I'm relatively new to using docker. When I had initially set it up (weeks ago) I was able to pull and manipulate containers. Today I came back to my docker project and now I can't even successfully pull an image.
$ docker pull ubuntu:14.04
ubuntu:14.04: The image you are pulling has been verified
511136ea3c5a: Download complete
511136ea3c5a: Error downloading dependent layers
d497ad3926c8: Downloading [============================> ] 115.7 MB/201.6 MB 7s
e791be0477f2: Download complete
3680052c0f5c: Download complete
22093c35d77b: Download complete
5506de2b643b: Download complete
5506de2b643b: Error pulling image (14.04) from ubuntu, endpoint: https://registry-1.docker.io/v1/, Error mounting '/dev/mapper/dock5506de2b643b: Error pulling image (14.04) from ubuntu, Error mounting '/dev/mapper/docker-8:98-380441-511136ea3c5a64f264b78b5433614aec563103b4d4702f3ba7d4d2698e22c158' on '/var/lib/docker/devicemapper/mnt/511136ea3c5a64f264b78b5433614aec563103b4d4702f3ba7d4d26982014/11/14 20:14:12 Error pulling image (14.04) from ubuntu, Error mounting '/dev/mapper/docker-8:98-380441-511136ea3c5a64f264b78b5433614aec563103b4d4702f3ba7d4d2698e22c158' on '/var/lib/docker/devicemapper/mnt/511136ea3c5a64f264b78b5433614aec563103b4d4702f3ba7d4d2698e22c158': invalid argument
This is the log:
$ journalctl -e
Nov 14 20:24:47 example.com docker[18225]: 2014/11/14 20:24:47 docker daemon: 1.3.1 4e9bbfa; execdriver: native; graphdriver:
Nov 14 20:24:47 example.com docker[18225]: [0687b0f9] +job serveapi(fd://)
Nov 14 20:24:47 example.com docker[18225]: [info] Listening for HTTP on fd ()
Nov 14 20:24:47 example.com docker[18225]: [0687b0f9] +job init_networkdriver()
Nov 14 20:24:47 example.com docker[18225]: [0687b0f9] -job init_networkdriver() = OK (0)
Nov 14 20:24:47 example.com docker[18225]: 2014/11/14 20:24:47 WARNING: Your kernel does not support cgroup swap limit.
Nov 14 20:24:47 example.com docker[18225]: [info] Loading containers:
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 07b2a034632f0ddb8f01ebdcf1c0cc4ba0ade7a6d927b544754b44aa3b58f877: open /var/lib/docker/containers/07b2a034632f0ddb8f01ebdcf1c0cc4ba0ade7a6d927b544754b44aa3b58f877/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 0bb0b50393dd951caeaa8386eb8ec8be1cc60e0822167ebed4dfdce9724b618c: open /var/lib/docker/containers/0bb0b50393dd951caeaa8386eb8ec8be1cc60e0822167ebed4dfdce9724b618c/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 15732a4b2a97b91a2c590cab260f91dde7708b50059942221d349a778f94c892: open /var/lib/docker/containers/15732a4b2a97b91a2c590cab260f91dde7708b50059942221d349a778f94c892/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 17b4471d4b031cd24feba6a2dc46e1524bcd9a6bb3b03342a642a5968caff3fa: open /var/lib/docker/containers/17b4471d4b031cd24feba6a2dc46e1524bcd9a6bb3b03342a642a5968caff3fa/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 20686bda195d61f2c76c3e3c809f8b07df9b830d8bc650e10593e1863c82b7f3: open /var/lib/docker/containers/20686bda195d61f2c76c3e3c809f8b07df9b830d8bc650e10593e1863c82b7f3/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 2fe7db68f38445c8ac0124be87174f66ccd1729880c5fa94b93d77ac0aa547fe: open /var/lib/docker/containers/2fe7db68f38445c8ac0124be87174f66ccd1729880c5fa94b93d77ac0aa547fe/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 31b34a085e90849bcffd50c5f7b41d93849d494913448a92849c5d621555251d: open /var/lib/docker/containers/31b34a085e90849bcffd50c5f7b41d93849d494913448a92849c5d621555251d/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 3484c3c05947051eea53865c973100d493e7ec495b3d7a5d4fbc1e5096196733: open /var/lib/docker/containers/3484c3c05947051eea53865c973100d493e7ec495b3d7a5d4fbc1e5096196733/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 3ed275efb25789d6c9e18bf36e46f437fbdb21f3ffd7a93cb4525610737441f0: open /var/lib/docker/containers/3ed275efb25789d6c9e18bf36e46f437fbdb21f3ffd7a93cb4525610737441f0/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 4503890c72d2f728e315b6ecae05fbabba85a3f959898a52df800f6fa22ca094: open /var/lib/docker/containers/4503890c72d2f728e315b6ecae05fbabba85a3f959898a52df800f6fa22ca094/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 4db4ed2fbac1b442d770bcd325937508d2b190caa766f4ddef4f21628a953ea2: open /var/lib/docker/containers/4db4ed2fbac1b442d770bcd325937508d2b190caa766f4ddef4f21628a953ea2/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 56f36a11482d6b9c513cbb819d6c67a768bd47dc4c02bd0de62c61365b6ba363: open /var/lib/docker/containers/56f36a11482d6b9c513cbb819d6c67a768bd47dc4c02bd0de62c61365b6ba363/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 5b254c1c2344f61ab6bf6b338b22150cccd6ebd04407f3d00d6b5b3e37810d4f: open /var/lib/docker/containers/5b254c1c2344f61ab6bf6b338b22150cccd6ebd04407f3d00d6b5b3e37810d4f/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 73fd6f0edadcf67fcdad7a397784275db013df085e648230b5818f0e68e3f48c: open /var/lib/docker/containers/73fd6f0edadcf67fcdad7a397784275db013df085e648230b5818f0e68e3f48c/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 7ad8ad079db979b156af858cd36b908434157efd43e8cbc13677fa287bdf4da0: open /var/lib/docker/containers/7ad8ad079db979b156af858cd36b908434157efd43e8cbc13677fa287bdf4da0/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 82a2e14c00dd73e2df1d78c45a0e576d52637c5dc422c32182ded365d6893167: open /var/lib/docker/containers/82a2e14c00dd73e2df1d78c45a0e576d52637c5dc422c32182ded365d6893167/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 86572f605d7990f173875853bcfbdfe3f909c9b26f439378ab73d561e0e735eb: open /var/lib/docker/containers/86572f605d7990f173875853bcfbdfe3f909c9b26f439378ab73d561e0e735eb/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 9eecdb0bf364f80cc88532832221da9de86c10a31b24660fdce8b68c79504a88: open /var/lib/docker/containers/9eecdb0bf364f80cc88532832221da9de86c10a31b24660fdce8b68c79504a88/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container a0920424bc83bffbc980f39f6dad17c865f84de1c3508a01d3c1298870f608c1: open /var/lib/docker/containers/a0920424bc83bffbc980f39f6dad17c865f84de1c3508a01d3c1298870f608c1/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container be228e991ffba0d423bb8bdca22fda9e318b7084bae53d765212bed6612e6b01: open /var/lib/docker/containers/be228e991ffba0d423bb8bdca22fda9e318b7084bae53d765212bed6612e6b01/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container e01b5a18f7c252f9c06e6d2dc9720baa184bc803e52aa68e9253372854382213: open /var/lib/docker/containers/e01b5a18f7c252f9c06e6d2dc9720baa184bc803e52aa68e9253372854382213/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container f00aff0df390b90f0a739430b4896cd67afc256a1c657271caf989fd3791ac91: open /var/lib/docker/containers/f00aff0df390b90f0a739430b4896cd67afc256a1c657271caf989fd3791ac91/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container f271529997f7479b5b6f65ccdd21d6b91445bbb31a3b253e95b1cf6ad6468c37: open /var/lib/docker/containers/f271529997f7479b5b6f65ccdd21d6b91445bbb31a3b253e95b1cf6ad6468c37/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .......................[info] : done.
Nov 14 20:24:47 example.com docker[18225]: [0687b0f9] +job acceptconnections()
Nov 14 20:24:47 example.com docker[18225]: [0687b0f9] -job acceptconnections() = OK (0)
Nov 14 20:24:47 example.com docker[18225]: [info] POST /v1.15/images/create?fromImage=ubuntu%3A14.04
Nov 14 20:24:47 example.com docker[18225]: [0687b0f9] +job pull(ubuntu, 14.04)
Nov 14 20:24:47 example.com docker[18225]: [0687b0f9] +job trust_update_base()
Nov 14 20:24:48 example.com docker[18225]: [0687b0f9] -job trust_update_base() = OK (0)
Nov 14 20:24:48 example.com docker[18225]: [0687b0f9] +job trust_key_check(/library/ubuntu)
Nov 14 20:24:48 example.com docker[18225]: [0687b0f9] -job trust_key_check(/library/ubuntu) = OK (0)
Nov 14 20:24:48 example.com kernel: device-mapper: thin: Creation of new snapshot 0 of device 0 failed.
Nov 14 20:24:48 example.com kernel: JBD2: no valid journal superblock found
Nov 14 20:24:48 example.com kernel: EXT4-fs (dm-1): error loading journal
Nov 14 20:24:48 example.com kernel: JBD2: no valid journal superblock found
Nov 14 20:24:48 example.com kernel: EXT4-fs (dm-1): error loading journal
Nov 14 20:24:52 example.com systemd-udevd[298]: error: /dev/dm-1: No such device or address
Nov 14 20:24:53 example.com docker[18225]: [error] pull.go:151 Error from V2 registry: Error mounting '/dev/mapper/docker-8:98-380441-511136ea3c5a64f264b78b5433614aec563103b4d4702f3ba7d4d2698e22c158' on '/var/lib/docker/devicemapper/mnt/511136ea3c5a64f264b78b5433614aec563103b4d4702f3ba7d4d2698e22c158': invalid argument
Nov 14 20:24:57 example.com kernel: JBD2: no valid journal superblock found
Nov 14 20:24:57 example.com kernel: EXT4-fs (dm-1): error loading journal
Nov 14 20:24:57 example.com kernel: JBD2: no valid journal superblock found
Nov 14 20:24:57 example.com kernel: EXT4-fs (dm-1): error loading journal
Nov 14 20:25:02 example.com systemd-udevd[298]: error: /dev/dm-1: No such device or address
Nov 14 20:25:03 example.com docker[18225]: Error pulling image (14.04) from ubuntu, Error mounting '/dev/mapper/docker-8:98-380441-511136ea3c5a64f264b78b5433614aec563103b4d4702f3ba7d4d2698e22c158' on '/var/lib/docker/devicemapper/mnt/511136ea3c5a64f264b78b5433614aec563103b4d4702f3ba7d4d2698e22c158': invalid argument
Nov 14 20:25:03 example.com docker[18225]: [0687b0f9] -job pull(ubuntu, 14.04) = ERR (1)
Nov 14 20:25:03 example.com docker[18225]: panic: runtime error: invalid memory address or nil pointer dereference
Nov 14 20:25:03 example.com docker[18225]: [signal 0xb code=0x1 addr=0x20 pc=0x6bb9ac]
Nov 14 20:25:03 example.com docker[18225]: goroutine 58 [running]:
Nov 14 20:25:03 example.com docker[18225]: runtime.panic(0xa6bc20, 0x1087c93)
Nov 14 20:25:03 example.com docker[18225]: /usr/lib/go/src/pkg/runtime/panic.c:279 +0xf5
Nov 14 20:25:03 example.com docker[18225]: bufio.(*Writer).flush(0xc2082228c0, 0x0, 0x0)
Nov 14 20:25:03 example.com docker[18225]: /usr/lib/go/src/pkg/bufio/bufio.go:530 +0xdc
Nov 14 20:25:03 example.com docker[18225]: bufio.(*Writer).Flush(0xc2082228c0, 0x0, 0x0)
Nov 14 20:25:03 example.com docker[18225]: /usr/lib/go/src/pkg/bufio/bufio.go:519 +0x39
Nov 14 20:25:03 example.com docker[18225]: net/http.(*response).Flush(0xc20816fa40)
Nov 14 20:25:03 example.com docker[18225]: /usr/lib/go/src/pkg/net/http/transport.go:885 +0x38f
Nov 14 20:25:03 example.com docker[18225]: created by net/http.(*Transport).dialConn
Nov 14 20:25:03 example.com docker[18225]: /usr/lib/go/src/pkg/net/http/transport.go:601 +0x957
Nov 14 20:25:03 example.com docker[18225]: goroutine 118 [runnable]:
Nov 14 20:25:03 example.com docker[18225]: net/http.(*persistConn).readLoop(0xc2080d7130)
Nov 14 20:25:03 example.com docker[18225]: /usr/lib/go/src/pkg/net/http/transport.go:868 +0x829
Nov 14 20:25:03 example.com docker[18225]: created by net/http.(*Transport).dialConn
Nov 14 20:25:03 example.com docker[18225]: /usr/lib/go/src/pkg/net/http/transport.go:600 +0x93f
(snipping several dozen lines of stack trace in the middle there)
The search results for various permutations of "docker error mount invalid argument dm" are badly washed out so I wasn't able to find any helpful leads; nor was I able to find anything relevant in the docker issue list. I tried re-installing docker (by running pacman -Rns docker and then pacman -S docker hoping that it was a config setting I could nuke & pave but this had no effect. I then ran the following:
$ dmsetup ls
docker-8:98-380441-pool (254:0)
followed by dmsetup remove docker-8:98-380441-pool and attempted the pull again. No difference.
I'm convinced this is not a docker bug but a misconfiguration of my system, but the error provided ("error mounting .... invalid argument") is rather opaque and I'm stuck with what to try next.
Any suggestions would be appreciated.
Last edited by cmtonkinson (2014-11-15 11:41:47)

Well, rm -rf /var/lib/docker did it!
I was unable to remove /var/lib/docker/devicemapper ("device or resource busy") but that doesn't seem to matter - as you suggest docker reconfigured itself. Thanks for the tip!
For the record (should have posted this previously):
$ docker info
Containers: 1
Images: 7
Storage Driver: devicemapper
Pool Name: docker-8:98-380441-pool
Pool Blocksize: 65.54 kB
Data file: /var/lib/docker/devicemapper/devicemapper/data
Metadata file: /var/lib/docker/devicemapper/devicemapper/metadata
Data Space Used: 598.3 MB
Data Space Total: 107.4 GB
Metadata Space Used: 1.18 MB
Metadata Space Total: 2.147 GB
Library Version: 1.02.90 (2014-09-01)
Execution Driver: native-0.2
Kernel Version: 3.17.2-1-ARCH
Operating System: Arch Linux
WARNING: No swap limit support
$ docker --version
Docker version 1.3.1, build 4e9bbfa

[Solved] Root device doesn't exist

Hi!
EDIT SOLVED: Booted from a arch-core CD and did a;
mv /etc/mkinitcpio.conf.pacnew /etc/mkinitcpio.conf
pacman -U /var/cache/pacman/pkg/kernel26-2.6.25-4-1-i686.pkg.tar.gz
Seems like a had a configuration error in my old mkinitcpio.conf file and kernel install failed.
.. But should it install when the kernel install failes?
For interested, here is my pacman.log
[2008-05-24 20:04] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2008-05-24 20:04] ==> Building image "default"
[2008-05-24 20:04] ==> Running command: /sbin/mkinitcpio -k 2.6.25-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
[2008-05-24 20:04] :: Begin build
[2008-05-24 20:04] :: Parsing hook [base]
[2008-05-24 20:04] :: Parsing hook [udev]
[2008-05-24 20:04] :: Parsing hook [autodetect]
[2008-05-24 20:04] :: Parsing hook [pata]
[2008-05-24 20:04] :: Parsing hook [scsi]
[2008-05-24 20:04] :: Parsing hook [sata]
[2008-05-24 20:04] :: Parsing hook [usbinput]
[2008-05-24 20:04] ==> FAIL
[2008-05-24 20:04] ==> Building image "fallback"
[2008-05-24 20:04] ==> Running command: /sbin/mkinitcpio -k 2.6.25-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26-fallback.img -S autodetect
[2008-05-24 20:04] :: Begin build
[2008-05-24 20:04] :: Parsing hook [base]
[2008-05-24 20:04] :: Parsing hook [udev]
[2008-05-24 20:04] :: Parsing hook [pata]
[2008-05-24 20:04] :: Parsing hook [scsi]
[2008-05-24 20:04] :: Parsing hook [sata]
[2008-05-24 20:04] :: Parsing hook [usbinput]
[2008-05-24 20:04] ==> FAIL
[2008-05-24 20:04] upgraded kernel26 (2.6.25.4-1 -> 2.6.25.4-1)
And old mkinitpcio.conf
MODULES="ata_generic ahci"
BINARIES=""
FILES=""
HOOKS="base udev autodetect pata scsi sata usbinput keymap filesystems"
I think it was the keymap it complained about
---- Original message
After the last upgrade with kernel 2.6.25, i get;
Attempting to create root device '/dev/sda3'
ERROR: Failed to parse block device name for '/dev/sda3' unknown
ERROR: root fs cannot be detected
Waiting for device to settle...done
Root device '/dev/sda3' doesn't exist, attempting to create it
ERROR: Failed to parse block device name for '/dev/sda3' unknown
ERROR: Unable to create/detect root device, '/dev/sda3'
Dropping to recovery shell.. type 'exit' to reboot
at startup.
The fallback entry at grub, gives the same message.
When trying to modprobe a module, it gives me message:
FATAL: Could not load /lib/modules/2.6.25-ARCH/modules.dep: No such file or directory
Only /lib/modules/2.6.24-ARCH exists.
Last edited by cybe-arch (2008-05-24 18:40:56)

I have the same issue with kernel26-lts-2.6.32.41-1.
Recent Arch updates made my favourite operating system of the worst kind: flashplugin freezez in 5 seconds, mozilla gets some freezes as well,
copying files from one drive to another takes like 1.5h and many more weird things including some frequent performance abuses by the processes.
I see Arch behaves like old Microshit products. Sad thing but I move to more stable distro very soon, because I have enough of fixing bugs 3 times a week, to make my Arch usable again. Before like 6 months ago updated were less frequent and surprises were once a month not twice a week. Outrageous.
Perhaps Arch crew is overrun by the Apple guys, to compromise this distro, to encourage people to buy Apple products instead of using faulty Windowses or from day to day more troublesome Linuxes.
Going to the point.
So in response I wanted give LTS a try, but it drops me to recovery console (ramfs) saying that "Root device doesn't exist"

[nQSError: 43126]Authentication failed:invalid user/password, how to avoid?

Hi,
I encountered following error: [nQSError: 43126] Authentication failed: invalid user/password.
when I was starting weblogic server, and server used to shutdown.
After snooping around on net, came across this blog: http://obiee11gqna.blogspot.com/2011/09/obiee-11g-errors-nqserror-43113.html
Found that password for MDS & BIPLATFORM was 'expired', was able to solve my problem and my Presentation Services were up & running.
My question is, how to avoid password of MDS & BIPLATFORM from getting expired in future??
Regards,
Jitendra

Dpka,
Thanx for the link, it shows the way to avoid expiry of password.
I also found another link, in comment section which is equally useful: http://www.artofbi.com/index.php/2011/03/mds-or-biplatform-schema-password-change-considerations/
PS: Thanx to Deva as well for replying to my query.
Regards,
Jitendra

[Abandoned] device-mapper/dm-crypt/luks without initramfs

Hi everyone,
i attempted to compile a custom kernel to reduce the my EEE 1000H's boot time by compiling everything i need statically, which seems to work well, except one thing: Accessing my encrypted root partition. I created it by following the wiki and all is well if i boot "normally" (using an initramfs and the encrypt hook).
So i tried to compile the modules necessary to boot encrypted partitions into the kernel. The options i changed to achieve this were
CONFIG_BLK_DEV_DM=y
CONFIG_DM_CRYPT=y
CONFIG_CRYPTO_AES=y
CONFIG_CRYPTO_AES_586=y
in my kernel config (along with all the other stuff of course). All the
The i tried to boot the new kernel via GRUB using just
title Test
root (hd0,0)
kernel /vmlinuz-2.6.30-rc8-eee1000h-kms root=dev/sda3 i915.modeset=1 ro 3
but it panics
sd 0:0:0:0: [sda] Attached SCSI disk
UDF-fs: No partition found (1)
List of all partitions:
0800 156290904 sda driver: sd
0801 497983 sda1 #the unencrypted /boot
0802 2000092 sda2 #swap
0803 153790245 sda3 #root, ext3 fs
No filesystem could mount root, tried: ext3 ext2 iso9660 udf
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,3)
altough it does this in my monitor's native resolution . The kernel seems to try to access the encrypted partition directly and the device mapper doesn't seem to be active.
I guess this is because the script in
/lib/initcpio/hooks/encrypt
seems to handle unlocking the volume and activating the device mapper and it's obviously missing now. I think i would have to rewrite it to not use modules - but this is far beyond my abilites.
I haven't found any further information on this issue either, it just doesn't seem to be possible, or rather, advisable to encrypt your root partition while not using an initramfs. I guess i'll have to use one or just encrypt only my user's home directory, or does anyone have an idea on how to solve this problem?
Update: I gave up on this.
Last edited by Malstrond (2009-08-13 20:20:03)

Hi everyone,
i attempted to compile a custom kernel to reduce the my EEE 1000H's boot time by compiling everything i need statically, which seems to work well, except one thing: Accessing my encrypted root partition. I created it by following the wiki and all is well if i boot "normally" (using an initramfs and the encrypt hook).
So i tried to compile the modules necessary to boot encrypted partitions into the kernel. The options i changed to achieve this were
CONFIG_BLK_DEV_DM=y
CONFIG_DM_CRYPT=y
CONFIG_CRYPTO_AES=y
CONFIG_CRYPTO_AES_586=y
in my kernel config (along with all the other stuff of course). All the
The i tried to boot the new kernel via GRUB using just
title Test
root (hd0,0)
kernel /vmlinuz-2.6.30-rc8-eee1000h-kms root=dev/sda3 i915.modeset=1 ro 3
but it panics
sd 0:0:0:0: [sda] Attached SCSI disk
UDF-fs: No partition found (1)
List of all partitions:
0800 156290904 sda driver: sd
0801 497983 sda1 #the unencrypted /boot
0802 2000092 sda2 #swap
0803 153790245 sda3 #root, ext3 fs
No filesystem could mount root, tried: ext3 ext2 iso9660 udf
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,3)
altough it does this in my monitor's native resolution . The kernel seems to try to access the encrypted partition directly and the device mapper doesn't seem to be active.
I guess this is because the script in
/lib/initcpio/hooks/encrypt
seems to handle unlocking the volume and activating the device mapper and it's obviously missing now. I think i would have to rewrite it to not use modules - but this is far beyond my abilites.
I haven't found any further information on this issue either, it just doesn't seem to be possible, or rather, advisable to encrypt your root partition while not using an initramfs. I guess i'll have to use one or just encrypt only my user's home directory, or does anyone have an idea on how to solve this problem?
Update: I gave up on this.
Last edited by Malstrond (2009-08-13 20:20:03)

Win8RP: Failed to create new process "...javaw.exe" - Invalid argument

Hi all,
we have a huge Java (JRE 6.0.310.5) app that works fine on the Win 8 CTP, but on RP:
Failed to create new process "C:\Program Files (x86)\...\jre\bin\javaw.exe" - Invalid Argument
Thanks for any insight
G.

Hi,
Based on the error message 'Caused by: com.sap.engine.services.jmx.exception.JmxSecurityException: Caller J2EE_GUEST not authorized, only role administrators is allowed to access JMX' , this note shall solve this issue:
948970 - Caller J2EE_GUEST not authorized, only role administrators
Also check if the ADSUSER and ADS_AGENT have the correct password and the respective roles.
944221 - Error analysis for problems in form processing (ADS)
Which is your NW version?
Regards,
Lucas Comassetto.

[SOLVED] luksOpen device-mapper reload ioctl failed invalid argument

Similar Messages

Maybe you are looking for