Reply
Visitor
utopian
Posts: 2
Registered: 05-28-2009
0

Re: Buffalo external drive stopped working after MacOS 10.5.7 update.

Colin,

 

Despite my frustration with the ongoing reality of not being able to access my files on my Japanese 250GB HD, I do want to thank you for keeping us all up to date. I do hope that the fix will arrive swiftly as I have another computer that I need to transfer files to in the next few weeks.

 

Thanks again.

Running Bull - Moderator
Colin137
Posts: 1,112
Registered: 12-05-2008

Re: Buffalo external drive stopped working after MacOS 10.5.7 update.

[ Edited ]

The update has been posted on our FTP site. The username/password is buffalo/buffalo.

 

ftp://buffalo:buffalo@209.252.83.162/share/drivestation_os_10.5.7_fix/

 

This update patches Mac OS 10.5.7 to correct Apple's USB MSC driver behavior with older Buffalo Drivestation models. The symptoms occur after updating to 10.5.7. When the device is attached:

  • It will not be detected in both Disk Utility and System Profiler.
  • Check the Console (from Finder, Go->Utilities, Console). Click on the Show Log List button, then choose system.log. Look for lines following this pattern:
### Lots of these:
May 13 21:13:46 HOSTNAME kernel[0]: USBF: 66380.387 AppleUSBEHCI0x4893000::
Found a transaction which hasn't moved in 5 seconds on bus 0xfd, timing out! (Addr: 0, EP: 0)
May 13 21:13:52 HOSTNAME kernel[0]: USBF: 66386.388 AppleUSBEHCI0x4893000::
Found a transaction which hasn't moved in 5 seconds on bus 0xfd, timing out! (Addr: 0, EP: 0)

### Then this:
May 13 21:13:53 HOSTNAME kernel[0]: USBF: 66387.621 0xc415b00
The IOUSBFamily was not able to enumerate a device.
May 13 21:13:53 HOSTNAME kernel[0]: USBF: 66387.762 0x51fc300
The IOUSBFamily is having trouble enumerating a USB device that has been plugged in.
It will keep retrying. (Port 1 of hub @ location: 0xfd100000)

### Then lots more of these, then the middle one again:
May 13 21:13:59 HOSTNAME kernel[0]: USBF: 66393.388 AppleUSBEHCI0x4893000::
Found a transaction which hasn't moved in 5 seconds on bus 0xfd, timing out! (Addr: 0, EP: 0)
May 13 21:14:05 HOSTNAME kernel[0]: USBF: 66399.388 AppleUSBEHCI0x4893000::
Found a transaction which hasn't moved in 5 seconds on bus 0xfd, timing out! (Addr: 0, EP: 0)

 

 

 

Instructions for update

1. Download "Buffalo Drivestation OS 10.5.7 Fix.zip", put it on your Desktop.
2. Double click on the file to extract it. It will create a folder named "Buffalo Drivestation OS 10.5.7 Fix". Open the folder.
3. Follow the instructions in the READ ME FIRST file to perform the update.

 

Contents of READ ME FIRST.txt:

 

This update patches Mac OS 10.5.7 to correct Apple's USB MSC driver behavior with older Buffalo Drivestation models. It will copy a kernel extension package to the /System/Library/Extensions directory, then notify the system of the change. BEFORE PERFORMING THE UPDATE, MAKE SURE YOU SAVE ANY OPEN DOCUMENTS. You must restart your computer afterwards to apply the fix.

This update is provided "AS IS" with no warranty of any kind. This update should not result in data loss, but Buffalo cannot be held liable for any problems that may result. Make sure your data is backed up before performing the update!

Installation Instructions:
1. Check the version of your Mac's OS:

Click on the Apple menu, then choose "About This Mac". The version will be listed under the Apple logo, under the words "Mac OS X".

IF THE VERSION DOES NOT SAY EXACTLY "10.5.7", DO NOT PERFORM THIS UPDATE, AND DO NOT FOLLOW ANY MORE OF THESE INSTRUCTIONS.



2. Check that your user account is an administrator, and that there is a set password for the account:

2a. Click on the Apple menu and choose "System Preferences". Click on "Accounts". Your username should be listed on the left side, underneath "My Account". If your user account is an administrator, it will say "Admin" directly underneath your username.

2b. Click on the "Set Password..." button on the top right side, and make sure there is a password set. If the password boxes are blank, enter in a new password.



3. Run the installation script:

3a. On the desktop, double click on the folder (not the .zip file!) named "Buffalo Drivestation OS 10.5.7 Fix". THE FOLDER MUST BE NAMED EXACTLY "Buffalo Drivestation OS 10.5.7 Fix", AND MUST BE LOCATED ON THE DESKTOP, OR THE UPDATE SCRIPT WILL NOT FUNCTION.

3b. Find the file named "RunAfterReading.bash". Hold the Control key while you click on "RunAfterReading.bash". Select "Open With", then choose "Other". Click on the "Utilities" folder, then choose "Terminal", and click "Open".

3c. The script will prompt you for your password. When it does, enter in your user's password. No characters will appear on the screen when you type in the password, this is normal. If the update completes successfully, please restart the computer. The issue will not be resolved until you restart.



Troubleshooting:
If you receive any errors, please leave the window open and contact technical support. We will need to see what the error messages were in order to diagnose the problem. If the update folder is named correctly, the script will also create a log file named logfile.txt in the folder.

Message Edited by Colin137 on 06-15-2009 06:17 PM
Message Edited by Colin137 on 06-15-2009 08:54 PM
Message Edited by drmemory on 06-16-2009 10:33 AM
Message Edited by drmemory on 06-16-2009 10:50 AM


My stuff: Buffalo WHR-HP-G54 + WHR-G125 in WDS

PLEASE post the Model Number and Firmware Version of your device! We can help a lot more with that info.

Visitor
mrsanger17
Posts: 2
Registered: 06-07-2009
0

Re: Buffalo external drive stopped working after MacOS 10.5.7 update.

Thank you very much.  It worked perfectly.
Visitor
lsinger9404
Posts: 4
Registered: 06-11-2009
0

Re: Buffalo external drive stopped working after MacOS 10.5.7 update.

How does one get permission to download?? It says I do not have permission.
Running Bull - Moderator
Colin137
Posts: 1,112
Registered: 12-05-2008
0

Re: Buffalo external drive stopped working after MacOS 10.5.7 update.

[ Edited ]

lsinger9404 wrote:
How does one get permission to download?? It says I do not have permission.

ftp://buffalo:buffalo@209.252.83.162/share/drivestation_os_10.5.7_fix/

 

Log in with username buffalo and password buffalo. I've tried it from several computers, and it works fine for me.

Message Edited by drmemory on 06-16-2009 10:50 AM


My stuff: Buffalo WHR-HP-G54 + WHR-G125 in WDS

PLEASE post the Model Number and Firmware Version of your device! We can help a lot more with that info.

Visitor
lsinger9404
Posts: 4
Registered: 06-11-2009
0

Re: Buffalo external drive stopped working after MacOS 10.5.7 update.

When I click the link, Safari tells me:

 

You don’t have permission to open this page.

You don’t have permission to view “Drivestation OS 10.5.7 Fix”. 

 

 can't get in with an ftp client either 

Visitor
davemiles21
Posts: 3
Registered: 05-16-2009
0

Re: Buffalo external drive stopped working after MacOS 10.5.7 update.

It didn't work for me either in Safari but works fine if you load the link in Firefox.

 

I've just downloaded and everything is working now! It's taken a while to get this sorted but thankfully it's back to normal. Thanks for the fix.

Thunder Bison - Administrator
drmemory
Posts: 318
Registered: 09-10-2008
0

Re: Buffalo external drive stopped working after MacOS 10.5.7 update.

[ Edited ]

We fixed the Safari issue, you should be able to connect and download the fix on Safari now.

Message Edited by drmemory on 06-16-2009 10:51 AM
Buffalo Technology USA
Always backup important data to multiple devices/locations. Storing data in one device IS NOT A BACKUP!
Visitor
lsinger9404
Posts: 4
Registered: 06-11-2009
0

Re: Buffalo external drive stopped working after MacOS 10.5.7 update.

Bingo! Thank you kind sirs! I knew you'd come through with a fix.

 

Larry 

JLB
Visitor
JLB
Posts: 1
Registered: 06-16-2009
0

Re: Buffalo external drive stopped working after MacOS 10.5.7 update.

The update worked great.  Back in business now with my HB 250 U2 on the IMac.  I did have to open a second terminal window to enter the password, then copy and paste it into the "fix" window, but it worked OK.

 

Thank you