Jump to content

Retro 6.1.138 is mounting DVD+R! (also, stuck on ATAPI:A:0:0, and loudness: "-u disk1")


Recommended Posts

I've never seen this before.

 

As soon as I upgraded to this version, it started mounting the current "member" of this set of DVD optical media which is in the drive. First I thought this was a cool, new feature, that somehow Retro is letting me browse the contents of the disk to see what's on it. But then I found that it's hanging backups. The backups get stuck on "Scanning Devices... Checking ATAPI:A:0:0", pegging the CPU, and never going anywhere, so I have to Force Quit Retro. And the Finder will not let me unmount that optical disk, claiming it's in use. Furthermore, the Console shows a series of error messages associated with these events:

 

/Applications/Retrospect 6.1/Retrospect/Contents/MacOS/Device_Access.bundle/Contents/MacOS/loudness: "-u disk1" failed, error -9007

/Applications/Retrospect 6.1/Retrospect/Contents/MacOS/Device_Access.bundle/Contents/MacOS/loudness: "-u disk1" failed, error -9007

/Applications/Retrospect 6.1/Retrospect/Contents/MacOS/Device_Access.bundle/Contents/MacOS/loudness: "-uj disk1" failed, error -9007

 

What in the world is going on?? Now, I'm still running Tiger, but I didn't read anywhere that this new, Leopard-compatible version of Retro wasn't supposed to work under Tiger. So what's going on and how can I fix it?

 

Thanks,

 

Dave

Link to comment
Share on other sites

Did you happen to install the File System Plugin when you did the 6.1.138 install? That what it sounds like has happened. From the release notes (Retrospect 6.1 Read Me):

Quote:

Retrospect CD/DVDs mounting in the Finder:
Retrospect 6.1 includes an updated File System Plug-in that can successfully mount Retrospect CD/DVDs in the Finder on computers running Tiger. This includes the ability to mount DVD+R DL media.

 


http://kb.dantz.com/article.asp?article=5320&p=2

(although this KB article refers to Retrospect 5.1, the plugin is still in the same place and is removed the same way). Be sure to reboot.

 

Another thing you could try, since the problem seems to be happening in the scanning of the optical drive, would be to disable that device in Retrospect's Configure > Devices, Device Status.

 

Russ

Link to comment
Share on other sites

Quote:

As soon as I upgraded to this version, it started mounting the current "member" of this set of DVD optical media which is in the drive.

 


 

The ability to mount Member of a CD/DVD Backup Set in the Finder is provided by the "CD/DVD File System Plugin" that is part of the Easy Install of Retrospect. It has been part of Retrospect since I think 5.1; if you didn't see it before then you likely didn't have the extension installed.

 

Personally, I can do without the Finder mounting Retrospect written DVDs, since there's nothing available in them other then a little text file explaining what they are. And since you're having trouble, I'd suggest using the installer to uninstall everything, then doing a Custom Install and don't check the system files (you could just delete the kext file(s) but I don't know for sure what it/they is/are named; the installer will get it all).

 

Dave

Link to comment
Share on other sites

Guys, thanks!

 

The advice seems to have been invaluable. I ran:

 

sudo rm -R /System/Library/Filesystems/retrospectcd.

 

and rebooted, and now I get the good ol' option from the Finder to Ignore the DVD that's in the drive. Tomorrow I'll know if the backups will start working properly again.

 

Thanks again. While the feature of mounting the disks is cute, it definitely seems buggy. I'll have to make sure I stay clear of it with future installs.

 

Dave

 

p.s. What is the purpose of that "loudness" binary, anyway?

Link to comment
Share on other sites

Quote:

The advice seems to have been invaluable. I ran:

 

sudo rm -R /System/Library/Filesystems/retrospectcd.

 


Well, that command wouldn't have done anything. Sure that the command didn't end in "retrospectcd.fs" ?

 

Be sure to type that command EXACTLY RIGHT with no intervening spaces in the folder name. If you happen to mistype it as (don't try this at home, people) (with a space after "Library" or after "System"):

sudo rm -R /System/Library /Filesystems/retrospectcd.fs

or

sudo rm -R /System /Library/Filesystems/retrospectcd.fs

 

the system will happily remove all of /System/Library and then proudly announce:

/Filesystems/retrospectcd.fs not found

or

/Library/Filesystems/retrospectcd.fs not found

 

Bad things will already have happened. As the sudo warning says, with great power comes great responsibility.

 

This is like the command that every sysadmin has typed once (and never again), being in the root directory and wanting to type, as root:

rm -rf *.txt

but instead typing

rm -rf * .txt

(with a space after the *).

 

You wonder why it is taking so long, then you freak out. You only make that mistake once. Be very careful with recursive removes.

 

Russ

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...