hdiutil attach AND asr restore acting weird?

[jipsun]

On a Mac OSX system in iterm2 I was able to run these commands yesterday without any problem, but today they're behaving strangely.

hdiutil attach /tmp/InstallESD.dmg -noverify -nobrowse -mountpoint /Volumes/install_app

But now it fails every time, saying hdiutil: attach failed - No such file or directory.

 

I ran it as root

I checked that /Volumes/install_app didn't exist.

I tried making an empty dir at /Volumes/install_app

I checked nothing was mounted there etc.
I tried with -nomount instead of -mountpoint

 

The only thing that made it complete successfully was removing -noverify. (it did a whole scan before mounting)

 

Then asr started acting all weird.

`man asr` says that asr restore parameters have 2 hyphens, but the executable says it wants one hyphen when run as user, or 2 hyphens when it is run as root.
 

asr restore -source /Volumes/install_app/BaseSystem.dmg -target /Volumes/install_build -noprompt -noverify -erase

I tried each option with a single hyphen, and double hyphen. Every time it complained about the parameters.

Usage: asr <verb> <options>

  <verb> is one of the following
   asr restore --source <source> --target <target> [<options>]

 

The only asr params that worked were `asr info --source /Volumes/install_app/BaseSystem.dmg`
Then it showed a bunch of checksums etc.

 

Can someone please shed some light about what is going on?

`asr version` is 413. I don't know how to check the version of hdiutil, but the end of the man page says 13 June 2016.

 

------------------

 

That is after I've created and then attached to a sparse image mounted at /Volumes/install_app.
`df -h` shows my image is mounted and has 7.1GB free.

I tried `touch foo` inside it and then deleted it afterwards. So it's writable etc.

[jipsun]

Okay I see the reason asr didn't work is because I tried a -type SPARSE with my build image. Without that option, the `asr restore...` works.