Disk Utility, restore image via HTTP, and error 22 (invalid argument)

I'm trying to restore a properly-created and prepared (i.e. volume checksum applied) Apple Software Restore disk image to a volume on a target computer. The source image is hosted on a Web server and accessible via HTTP.
The image restoration process appears to succeed for the most part, but at the end, I get an error 22 (invalid argument). This may be after the image restoration has finished, and when the resulting volume is being mounted. (I wonder if the problem is automount-related?)
The same image, so far, restores to the same volume successfully when restored locally, mounting the drive in target disk mode on the host Mac.
I am curious if anyone else has seen this same behavior and found a solution. Or is everyone else having the same kinds of problems with HTTP-based restores?
MacBook Pro   Mac OS X (10.4.9)   15-inch, Core 2 Duo 2.16 GHz, 2 GB RAM

Visit http://www.bombich.com/. See if you find any related info on that site. If not email Mike Bombich about the problem. If anyone knows the answer I would think he should.

Similar Messages

  • Disk Utility Restore Process Input/Output Error

    <Image Edited by Host>
    My niece's MBP specs above. If I posted a picture of this poor machine, there'd be a lynch mob of passionate Apple fans arrive at my door wanting a public hanging...It's been dropped no less than a dozen times. (The ethernet port is stretched out of shape so badly that a standard plug will no longer fit the port!!!).
    Among other physical injuries, the screen won't present an image (just flickers white lines on black background, hinge has partially detatched, suspect the ribbon that transmits the display signal has been compromised). A visit to the Apple store tells us (by plugging into a cinema display via TB) that the hard drive is still in tact and data is salvageable. Keyboard and trackpad both work fine (surprisingly).
    Long story short, she's acquired a new MBA, been read the riot act about looking after it, and I have the unenviable task of salvaging her data, approx 275Gig.
    My objective is to obtain:
    1. A full copy of the data (existing file structures) - Complete
    2. A bootable disk image of the MBP - Incomplete and troublesome
    I have at my disposal:
    Mid 2011 27' iMac (Intel i7) on Mav
    MBPr13 (third host if needed) on Mav
    A home ethernet network with enterprise grade switching
    A Lacie 5BigPro 10TB NAS
    A couple of 1 & 2 TB Toshiba external drives, and
    Enough network adapters, USB cables and thunderbolt cables to suffice. Admin priviliges all round. All disk permissions repaired.
    Current connection config is the MBP thunderbolted to the iMac. I can use TDM (if I need to interface with the MBP using the iMac display) or can boot in Target Disk Mode if I want to see the MBP disk image on the iMac.
    Regarding Objective2: A bootable disk image of the MBP, I first tried to use the Restore function in Disk Utility, but that only works when booting the host in Recovery mode, whcih doesn't support TDM, so I'm flying blind...
    Next try, I booted the MBP in Target Disk Mode, which allowed me to use the Restore process from the iMac's Disk Utility, select the MBP HD, and target an external drive (one of the Toshiba's) plugged in to the iMac via USB.
    I've now tried this Restore 3 times, each time getting the following I/O error (at about 45 munites in to a projected 4 hour process):
    Any thoughts on root cause?
    And (given my screen/display limitations) am I missing a far simpler option?
    Cheers, Sla

    If that were the case you would not get in/out errors. These errors occur because the drive is no longer able to transfer data which is a hardware failure.
    If you want to post an image to the forum then you need to open the message editor and click on the Camera icon you will find in the editor's toolbar. Then select the image you wish to post and click on the Insert button.
    You can try running the Apple Hardware Test to see if it reveals anything.
    Using Apple Hardware Test
    Intel-based Macs- Using Apple Hardware Test

  • Disk Utility: Restore no longer creates bootable images?

    So I have a new hard drive for my macbook, and followed the procedure I used last time of using disk utility restore to write the current hard drive image to the new disk, with the new disk in a USB enclosure.
    I have done this before, it creates a bootable copy on the new disk, swap the disks away I go.
    This time however the new disk is not bootable. When starting it gets to the grey screen with the rotating white pips then dumps back to a black screen with error messages (like its trying to boot of the network).
    Swapping back to the old disk boots just fine, so its a problem with the image written to the new disk by disk utility restore not being bootable.
    Is this a known issue? I searched the forum with no answers, and am frustrated that its now working as I have run the image twice now at about 5 hours a go for 100GB of data so I am sure its not the copy. Straight after the copy the original disk has about 10 more files than the new disk that's just been imaged, has their been some update to disk utility in the OS X patches that means it no longer copies some key files?
    Note that partition on new disk is GUID as it should be, and I don't want to re-install anything from the install media I want to use make disk utility work as designed.

    I found two references that may help:
    A) At http://everythingapple.blogspot.com/2007/11/use-powerpc-mac-to-create-bootable.h tml it says "PowerPC Macs use the Apple Partition Map, but this poses no problem for Intel Macs, even though Intel Macs use the GUID Partition Table. The reverse is not true however. PowerPC Macs cannot boot disks with a GUID Partition Table."
    1. Open up Disk Utility and select your backup drive. Select the "Partition" tab.
    2. Go to the "Options" and choose "Apple Partition Map", which is the partition type necessary for PowerPC Macs.
    B) Carbon Copy Cloner - Red Dot Warning on main screen: "The target volume will not boot this computer because PowerPC Macintoshes cannot boot from USB devices."
    Looks like I'll have to install the 2.5" SATA drive into my PowerPC MacMini to upgrade my system volume from 80gb to 320gb.

  • Disk Utility Restore - Why error -34 ?

    I cloned my 700 G3 iBook's 20GB hard drive to a 30GB ext. HD with Disk Utility>Restore before sending it for repair. Now that I have gotten it back I want to restore the data to the computer's HD. I'm getting error -34 (disk full).
    So what is the nature of my problem? Must the destination disk be at least as big as the source disk? (Because it is copying the entire 30GB size.) Or must I empty (erase, reformat) the destination disk? (Because it is adding the data to what is already there.)
    Thanks

    Michael:
    You were right. Thanks. The data would have been added to what was already there.
    While I had made back-up clones before, this was the first time I needed to put it back into the computer's hard drive.

  • How to clone disk (Disk Utility Restore, boot: kernel panic)

    Hi, I've tried two times to clone my 120GB system disk (old Core2Duo Mac Mini (macmini2,1)) to a 1TB disk attached via USB cradle. Running Snow Leopard 10.6.8 which long time ago was upgraded from Leopard.
    Used the Disk Utility "Restore" for cloning. Both times Disk Utility completed without errors. However when I swap the 1TB from USB cradle into mac mini (to internal SATA), the result of even a "Save Mode" boot attempt with Shift/Mod key held is always a kernel panic: "unable to find driver for this platform: \"ACPI\"
    As my goal is to clone the existing system to a larger drive, a new install of OS X on the 1TB drive is out of the question. The original 120GB disk boots without problems. But the cloned attempts do not boot.
    Judging from the kernel panic it is as if "Restore" doesn't actually restore, but leaves out files. Thus Disk Utility restore in SL is buggy?
    Or is my cloning method wrong? Currently I just drag the 120GB system disk (the live running system) to the Source, then drag the 1TB USB disk to Destination, and allow full erase of destination, and do the priviledge elevation to root i.e. the usual password prompt. Does successful cloning need something extra...?

    If I understand correctly, what you're doing is copying your 120 GB drive to the 1 TB drive, then swapping the 1 TB drive into your Mac and trying to boot from it, and it fails.
    You're doing it wrong, and that's why it fails. A Finder copy (what you're doing) does not respect permissions or symbolic links, which are required to make the system boot. You need to use something that does respect that.
    Get your hands on a copy of SuperDuper http://shirtpocket.com/
    (free for basic use, but it's well worth the small fee of $27.95 for full access to all features); and/or
    Carbon Copy Cloner http://bombich.com
    and use one of those to make a bootable clone of your 120 GB drive, then you can boot from it.

  • Disk utility - restoring a .cdr question

    i hate the format of the apple discussion forums now.
    not sure if this is the proper place since there is no "community" to discuss Disk Utility and the "restore" function, which is not specific to snow leopard, but since i'm still running 10.6.8, i'll go ahead an post this here.
    in the past, i've successfuly restored disk images onto dedicated hard drive partitions.  i do this for a variety of reasons, namely to have working backups of certain DVD's, such as my install DVD's when internal super drive stopped functioning.
    however, i just tried this following what i think are the proper instructions, but now i can't restore the disk image and can't find the answer anywhere online.
    basically:
    1)  i'm going into disk utility, hooking up an external dvd drive and copying a playable DVD of some live music i purchased
    2)  i'm choosing "create new image" and under compression, choosing "dvd/cd master"
    the problem is that the resulting file comes out as ".cdr" and not .dmg.  i haven't tried it using some type of compression, but for some reason Disk Utility won't let me "restore" from a ".cdr" file, only a .dmg or .iso.
    i've tried changing the extensions.  i've tried converting (within disk utility) the .cdr to .dmg, and i get the same "invalid argument" error as always.
    the only thing i haven't done is tried making another .dmg using some type of compression, or read-only, read-write format.
    it would seem to me that choosing cd/dvd master is the proper category.
    does anyone know why a .cdr will mount, but cannot be used for restore???  and why making a disk image of a disk i own defaults to .cdr and not .dmg?
    thanks.
    666

    Hmmm.... I've just realised that none of the images I've created recently will verify properly. They all get to the end of the first stage (block checksum of partition #1) and then fail with "internal error". The only one which passes the verification process is the very first one which I created a long time ago. That one seems to complete two stages of block verifications (for 2 partitions) then one "file checksum".
    If I try to select a disk image and use "Open Disk Image" (from the right-click menu) I get an error saying "Unable to attach [image-name].dmg. No mountable file systems." This happens with every disk image I've created, apart from the very first one.

  • I'm trying to backup a my harddrive with disk utility but I'm getting an error  Unable to create Backup.dmg" (input/output error). Is there any other way to save my data? I believe my hard drive is failing or corrupt file. I can't boot up. Grey screen

    I'm trying to backup a my hard drive with disk utility but I'm getting an error  Unable to create Backup.dmg" (input/output error). Is there any other way to save my data? I believe my hard drive is failing or corrupt file. I can't boot up. Grey screen and spinning wheel. I've tried everything https://discussions.apple.com/message/20580424#20580424
    any help will be greatly appreciated.

    Check here. Also have you done a TimeMachine back up?
    http://support.apple.com/kb/TS2570

  • My external hard drive will not open and only shows up in Disk Utilities. When I try yo repair it, it give me and error of invalid sibling link. How do I fix my external hard drive?

    My external hard drive will not open and only shows up in Disk Utilities. When I try yo repair it, it give me and error of invalid sibling link. How do I fix my external hard drive?

    Invalid sibling link may not be fixable by Disk Utility. (Disk Utility is very conservative, and will not attempt repairs that might cause you to lose data.)
    It is an indication of serious Directory damage.
    that leaves
    a) third-party Utilities that will take those risks, or
    b) re-initializing the drive (which deletes all your data) and restoring from another backup source.
    c) "Copying off whatever files you can salvage" has gone by, and you cannot copy anything off a drive that will not mount. You may be able to use "rescue" programs such as prosoft engineering Data Rescue to copy files to another drive, but that sounds a lot better than its reality. You may get many files, but not get ANY filenames.

  • DISK UTILITY -- "New Image" problems

    Maybe I don't get how this works. I used an external USB drive to back up my MacBook Pro, making an image un=sing Disk Utility "New Image." THis seems to have worked fine. When I attach the external drive and double click on the DMG file it open and I seem to have access to all contents.
    Today I tried to make a second "New Image" on the same drive of my iMac24" and everything runs and makes a DMG file, but when I click on this one I get a msg saying the disk image "couldn't be opened" with the reason given being "no mountable file systems."
    Does this make perfect sense to somebody?
    Have I completely misunderstood the use and practice of the "new image" in Disk Utility?
    Thanks.

    Hey. If you want to make a DMG image of your iMac, you will need to boot off the install DVD and use Disk Utility from the DVD. To create the DMG is the same process: Select the "Macintosh HD" icon on the left hand side list of Disk Utility, click the "New Image" button, leave "Image Format" as "Compressed" and its up to you for Encryption, I always leave it as "None".
    Select to save your DMG image on the external hard drive and click save. Once the image is done, click on "Image" on the menu bar and click on "Scan Image for Restore...".
    That's it!
    Good luck

  • Disk Utility is reporting a fatal hardware error-S.M.A.R.T. status failing. Is there hope?

    OS 10.5.8 on a 1.8 GHz Power PC G5. Installed Western Digital WD1002FAEX as a second internal hard drive. I also installd the jumper needed to slow HD down for this computer. Initialized and formated the HD was able to back up a large iPhoto file and am still able to acceass the file from the new HD. Now Disk Utility is reporting a fatal hardware error-S.M.A.R.T. status failing. Is there hope?

    Is that on your first drive or the new one???
    Only experience I had with SMART warning was that in less than 48 hrs it was dead for good.

  • Disk Utility Restore

    I copied my macbook pro's hard drive to an external drive using disk utility restore. Is it normal for the copy's overall size to be smaller than the original? I thought it would be the same size? The external had no data on it. The original is 273.54 GB and the copy is 271.45 GB... Problem?

    May I try to answer your question. When you copy a disk there are a number of files which are not copied such as Trash, swap files and any temporary files that may have on the old disk will not be copied to the new disk. So while the approximately 2 GB of data might at first glance seem like a lot, it is in fact not really that much. I hope that helps you to understand what is happening there.
    |___________________
    Allan

  • Running via https and/or http ?

    Hi all,
    The applications you are all working on, do you run them in a secure link? I have just read that Oracle recommends running Apex app's using https which is definitely what I need to do for most of my pages. Is that possible with the embedded webserver or will I need to configure a separate webserver? Is it straightforward/recommended to run some pages via http and others via https?
    I'm using 11g and 3.2.
    regards,
    Malcolm.

    This in the online help:
    "Utilizing Secure Sockets Layer (SSL)
    Secure Sockets Layer (SSL) is a protocol for managing the security of data transmitted on the Internet. For Web applications, SSL is implemented by using the HTTPS protocol. Oracle recommends that you run Oracle Application Express applications using SSL (HTTPS protocol) to prevent any sensitive data from being sent over an unencrypted (cleartext) communication channel."
    but I suppose you could read that as only applying to pages containing sensitive data, as anyone would recommend.
    Thanks Andrew - you've answered my question that it is possible to use the embedded/bundled server to switch from http to https depending on the page ID, that's what I want to do. It's a public facing app. yes, and will contain some pages of sensitive data that the users would expect to use via a secure link.

  • I used a partitioned HDD for time machine, using a partition already containing other data files. I am now no longer able to view that partition in Finder. Disk Utility shows it in grey and "not mounted". Any suggestions of how to access the files?

    I used a partitioned HDD for time machine, using a partition already containing other data files. I am now no longer able to view that partition in Finder. Disk Utility shows it in grey and "not mounted". Any suggestions of how to access the files? Does using time machine mean that that partition is no longer able to be used as it used to be?
    HDD is a Toshiba 1TB, partitioned into two 500GB partitions.
    OS X version 10.9.2

    Yes, sharing a TM disk is a bad idea, and disks are cheap enough so that you don't need to.
    Now
    Have you tried to repair the disk yet

  • Have a mac book pro that crashed. ran disk utility to repair. comp booted and ran for short time. then crashed. ran repair again. disk utility said it could not repair files and i needed to format hard drive and start again. now nothing works

    have a mac book pro that crashed. ran disk utility to repair. comp booted and ran for short time. then crashed. ran repair again. disk utility said it could not repair disk and needed to format and start again.
    comp said it could not unmount disk and now when comp trys to boot all i get is a question mark on the screen. help

    Erase and Install
    1. Boot from your Snow Leopard Installer Disc. After the installer loads select your language and click on the Continue button.  When the menu bar appears select Disk Utility from the Utilities menu.
    2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area.  If it does not say "Verified" then the drive is failing or has failed and will need replacing.  SMART info will not be reported  on external drives. Otherwise, click on the Partition tab in the DU main window.
    3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Click on the Options button, set the partition scheme to GUID then click on the OK button. Set the format type to Mac OS Extended (Journaled.) Click on the Partition button and wait until the process has completed.
    4. Quit DU after formatting completes and return to the installer. Install Snow Leopard.
    5. After restart into Snow Leopard download and install Mac OS X 10.6.8 Update Combo v1.1.

  • [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

Maybe you are looking for