USB drive started unmounting itself after OS X update

Has anyone a work around to get a USB hard drive to stop unmounting itself? The drive used to work flawlessly and only started behaving as though the cable were disconnected following an OS X update.

Don't know about the update as a possible cause, but WD externals have a reputation for being very flakey with Macs, or flakey period. You could try a PRAM reset: hold CMD-Option-P-R keys down together at the startup chime, keep holding down until you hear two more chimes, total three, then let go and it will finish booting.
Also, you might try re-applying the 10.5.8 Combo Update.
http://support.apple.com/downloads/MacOS_X_10_5_8_ComboUpdate

Similar Messages

HELP: WD External Hard drive disconnecting by itself after Maverick OSX update.

Hello!
I just finished updating my OSX from Mountain Lion 10.8 to Maverick 10.9
I am using 15 inch Macbook Pro late 2011 processor is i7 and 4GB memory.
Before on ML I'm rarely or never expirience this where my external drive is disconnecting
by itself. I am using USB hub (10 ports) I have 2 HD's both are 1TB and on that usb port
my cooling pad is also connected as well the data plug for iphone. My USB port has another
power cable which is also in use.
Now I have three questions
1) Do you think that one of my HD has an issue? because this is the only one
that is disconnecting by it self? when I unplug and plug it back it shows to Utility Disk
but it is not mounting. I manage to restore it by clicking the repair button several time
but it keeps disconnecting by itself and I am not comfortable on doing this time to time.
2) Do you think updating to Maverick is one of the reason why this is happening?
3) What solution i can do to solve this issue.
Thank you in advance.

Hi to All
It seems my issue is already solved I didn't expirience any auto ejecting anymore after I formated my 1TB using the Disk Utility. I already bring back the files that I removed before from my 1TB and so far its all good.
Another tip is if you will plug your external HD's to a usb port give a one interval slot because if you do there's a possibility that it may auto eject again, this happen to me since updating to Maverick but in Mountain Lion maybe it happen to be once or thrice maybe because of bad ejecting that i've done to my 1TB.
This all is as per my intuition, observation and pure guts but now im good and my usb's are not auto ejecting anymore from the day I'd format it to disk utility using erase (of course in exfat format) until now. I wish this will help others too...
Have a nice day!

USB drives keep unmounting by themselves

This keeps happening over and over...
my USB drives are unmounting by themselves.
with no prompt or eject.
I've tried to re-set the PRAM. with no luck.
is this a on-going problem?
what can I do?

There are several reasons this might be happening so you'll need to provide us with more information.
1) are the drives connected directly to the computer or to a hub? If to a hub, try removing the hub and see if a drive or two connected directly to the computer will stay mounted.
2) who is the manufacturer of the drive(s)?
3) has this been an ongoing problem from day one or did it just recently start after a long period of stability? If the latter, did you make any changes about the same time the trouble began?

Creating a Mavericks USB boot drive after the horse has bolted. Can I create a bootable USB drive from my iMac after installing Mavericks without saving the Install OS X Mavericks.app file? Do I need to re- download the whole 5.29 Gb again?

Creating a Mavericks USB boot drive after the horse has bolted. Can I create a bootable USB drive from my iMac after installing Mavericks without saving the Install OS X Mavericks.app file? Do I need to re- download the whole 5.29 Gb from the App Store again? My problem is my 4Gb/month allowance on a 12 month contract. I cannot purchase a data block from my ISP and although my speed is theoretically slowed to 64k after reaching my 4Gb, it actually ceases to download in reality.

HI tasclix, it depends what you mean by an OS X boot drive.
If you want a recovery disk from which you can reinstall (by re-downloading) or recover from a time machine backup, then nbar is correct.
If, however, you want to boot and run the OS X installer from the USB drive (so that you don't need to download again), then you will need a copy of "Install OS X Mavericks.app"; see this article:
http://support.apple.com/kb/HT5856
Before downloading again, search your system to see if the installer is still there - it's usually in the /Applications folder unless it has been deleted, but check your whole system for it anyway, you never know, you might still have it somewhere.
Message was edited by: SilverSkyRat

USB drive keep showing up after eject

I just bought a USB drive today and everything works perfectly except - after 3-4 seconds after I ejected the disk, it will keep showing up in Finder automatically and it keeps doing that everytime I ejected it. I disconnect the usb drive between the gap (after eject and its auto re-mount). So, anybody know what's the problem here? I verify and repair the usb disk (as well as my internal hard drive) in disk utility, but still the problem keeps showing up.
Macbook Mac OS X (10.4.6) 2 GHz Intel Core 2 Duo, 120GB HD, 1GB SDRAM

Adnan,
two suggestions:
1) Try it using a different Mac
2) Create a new user account and check things there
Mihalis.

My APTV 3 restarts by itself after the last update. plz help me

Netquark Sep 16, 2014 8:42 AM
Hello my APTV 3 restarts by itself after the last update.
I restore my APTV with pc and it does not work.
if I unplug the cables after 30 minutes, it works, but once sleep if you restarts the problem comes back. plz help me
Apple TV

Did you successfully restore the Apple TV?
Apple TV (2nd and 3rd generation): Restoring your Apple TV

[SOLVED] Problem with external USB drive started yesterday

My system freezes for about 65 seconds at the login screen. After 65 seconds, I can login and everything is normal afterwards.
I discovered that I can eliminate the freeze by disconnecting the external USB drive from the PC. Here are the error messages from kernel.log when the drive is connected:
Oct 15 23:10:14 localhost kernel: [ 17.035091] usb 1-1.3: device descriptor read/64, error -110
Oct 15 23:10:29 localhost kernel: [ 32.155955] usb 1-1.3: device descriptor read/64, error -110
Oct 15 23:10:29 localhost kernel: [ 32.325394] usb 1-1.3: new high speed USB device number 4 using ehci_hcd
Oct 15 23:10:31 localhost kernel: [ 34.045126] MediaState is connected
There is supposed to be a kernel boot option (irqpoll) to prevent this from occurring. However, that option seems to no longer work for kernels after 2.6.39. If I try using it with Arch, the system will not boot, saying all the CPU's failed.
I also don't understand why this just started happening yesterday, as the USB drive has been connected to the PC longer than I've been using Arch. Also, my kernel has not been updated since I installed Arch on Oct 8.
Does anyone know another fix or workaround for this problem?
Thanks,
Tim
Last edited by ratcheer (2011-10-17 01:30:08)

Problem solved
I feel stupid, but I also feel better. I turned off the PC, disconnected the power from the USB drive for about 15 seconds, reconnected the power, rebooted, removed the irqpoll kernel option, and Ubuntu started, perfectly. I need to learn that the USB drive just goes freaky sometimes and remember to do this. But, this is only the second time I've had to do this in months of use.
Tim

External USB drive won't mount after 10.9.5 upgrade

Is anyone else reporting the following issue? Immediately after installing OS X update 10.9.5 (13F34) on 09/18, my external USB drive (IOMega 1GB OS X Extended FS) used for Time Machine would no longer mount and isn't recognized. When I look at the drives in finder, it is missing. However, it does show up under the USB Hi-Speed Bus device tree:
USB Mass Storage:
Product ID:    0x0376
Vendor ID:    0x059b (Iomega Corporation)
Version:     0.00
Serial Number:    ABCDEF012314E2ED
Speed:    Up to 480 Mb/sec
Manufacturer:    Iomega
Location ID:    0x1a120000 / 3
Current Available (mA):    500
Current Required (mA):    0
Console message when device plugged in:
10/6/14 3:22:31.000 AM kernel[0]: USBMSC Identifier (non-unique): ABCDEF012314E2ED 0x59b 0x376 0x0, 2
mount command results:
devfs on /dev (devfs, local, nobrowse)
map -hosts on /net (autofs, nosuid, automounted, nobrowse)
map auto_home on /home (autofs, automounted, nobrowse)
/dev/disk1s2 on /Volumes/Mac-Mini 2 (hfs, local, nodev, nosuid, noowners)
System is Mac-Mini (late 2012), 2.5 Ghz i5, 8GB ram, 500GB local storage, 1TB on second Firewire disk for media, 1TB USB disk for Firewire (PROBLEM)
I have reinstalled the combined 10.9.5 OS upgrade, and verified that the drive works when connected to my other MB Pro (mid-2012 running Yosemite beta 3). There is no third party software that I'm aware of in use for this drive, as it's only for Time Machine backups.
Thanks

Is the drive's icon on the desktop (perhaps behind another icon, which is possible if Finder > View > Cleanup is enabled)?
If not, is the box Finder > Preferences > General > External Disks checked?
Is the drive listed in every Finder window's sidebar?
If not, is the box Finder > Preferences > Sidebar > External Disks checked?
Are Time Machine backups to the drive happening on schedule?
If not, does the drive appear in System Preferences > Time Machine > Select Disk?
Can you open /Volumes/Mac-Mini 2/Backups.backupdb using Finder > Go > Go to Folder...?
Does the drive appear in Disk Utility? Is it (or can it be) mounted there?
Have you tried to plug it in to a USB port on the Mini (not a hub) or into a different USB port on the Mini?
Have you tried this: shut down; unplug the drive; boot the Mac; after you have logged in and the Finder is done populating the desktop and menu bar, plug the drive in?

HT1178 how to add usb drives to time capsule after initial setup

How to add USB hard drives to TC after TC is already setup then access the usb drives by both PC and mac?

1. Just plug them in. The drives need to be formatted as FAT16, FAT32, or Mac OS Extended (Journaled), and may need to be connected through a powered USB hub.
2. Click here for information.
(82647)

Epson USB Scanner not working properly after 10.44 update

After 10.44 update, my Epson 3490 USB Photo scanner has stopped working properly. Is this just another one of those update issues that seem to be reported at the moment. Will someone at Aplle actually fix thisat some point?

I can't open Epson Scan - it appears in the dock and info bar for about 2 seconds, then quits. I can sometimes open SmartPanel by pushing the scan button on the unit, but then it says "Please install the supported TWAIN driver." Most of the time it appears in the dock and info ba) but doesn't open the window itself. Epson couldn't fix it. It works on a PC, so they said it's a Mac problem.

Why tethering with USB cable doesn't work after IOS6.0 update?

why tethering with USB cable doesn't work after IOS 6.0 update?

Try updating the carrier settings, if that doesn't do it try following along with this Apple doc -> iOS: Troubleshooting Personal Hotspot

Start up slow after a windows update

I feel a little slow in windows start up in my notebook after a windows update, I have downloaded an install an update about 800mb but all components have not been installed successfully, again after one day back there was another update and it has installed successfully in complete.
Is updating windows affect to slow down the PC performance?
Seek your expert advices?
Tnx.

You have probably installed too many updates. Windows Update puts many files on the computer to update files. Follow these steps to remove some leftover files.
1. Click Start.
2. Search for "Disk Cleanup".
3. Open Disk Cleanup
4. Let it search for Windows Update Files. (I don't remember what the actual name is)
5. Have it clean those files.
You're done!

My Toshiba external hard drive won't mount after OSX Mavericks update. Please help.

Two days ago I updated to Mavericks 10.9.3 and prior to this, my Toshiba 1TB external hard drive worked perfectly well. Since the update, my hard drive will no longer mount. It shows up in Disk Utility but will not let me 'mount', 'verify disk' or 'repair disk' through Disk Utility. My sister has an identical Macbook Pro which she has not updated to Mavericks. I have tested my hard drive on her laptop and it works just fine. Can anyone tell me how to fix this? Do I need to reformat my hard drive (and if so, will that clear everything on my hard drive?) or is there a simple fix?
Thank you for any assistance you can offer!

Reset the NVRAM/PRAM and Reset the SMC, then try again.

USB Drive Accidentally Unmounted & Now Won't Mount

Hi,
My Seagate 400 GB USB external drive was accidentally unmounted improperly and now it won't mount. I restarted my laptop, restarted the drive itself, changed cords and USB inputs on the laptop and nothing has changed.
The drive doesn't show up in Disk Utility, but it does in System profiler. In System Profiler it shows up, but with minimal information. My 300 GB Seagate drive (which is fine) shows up with a great deal more information like it's capacity etc. etc.
I have really essential information on the 400 including a project that's due relatively soon, so any help would me greatly appreciated!! THANKS!
-jules

Two things you can try:
Try connecting the drive, and restarting from the CD/DVD that came with your Powerbook, and use the Disk Utility to look for your connected drive.
You may also look in finder>preferences>general and make sure that the boxes are checked to show hard drives on the desktop.

USB drive no longer works after system reinstallation

Recently I reinstalled the system (after 1 year of no uptades). One of my USB disks (strictly speaking it is a 2.5" disk in a USB enclosure) stopped to work. When I connect the USB cable the drive icon doesn't appear on the desktop. I attach the dmesg messages:
[ 94.770021] usb 5-5: new high-speed USB device number 3 using ehci-pci
[ 95.000996] Initializing USB Mass Storage driver...
[ 95.001670] usbcore: registered new interface driver usb-storage
[ 95.001677] USB Mass Storage support registered.
[ 95.026831] scsi4 : usb-storage 5-5:1.0
[ 95.027324] usbcore: registered new interface driver ums-cypress
[ 96.070828] scsi 4:0:0:0: Direct-Access Hitachi HTS547575A9E384 PQ: 0 ANSI: 0
[ 96.073181] sd 4:0:0:0: [sdb] 1465149168 512-byte logical blocks: (750 GB/698 GiB)
[ 96.073804] sd 4:0:0:0: [sdb] Write Protect is off
[ 96.073813] sd 4:0:0:0: [sdb] Mode Sense: 03 00 00 00
[ 96.074428] sd 4:0:0:0: [sdb] No Caching mode page present
[ 96.074436] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[ 96.076557] sd 4:0:0:0: [sdb] No Caching mode page present
[ 96.076568] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[ 96.105465] sdb: sdb1 sdb2
[ 96.108041] sd 4:0:0:0: [sdb] No Caching mode page present
[ 96.108052] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[ 96.108060] sd 4:0:0:0: [sdb] Attached SCSI disk
[ 104.480029] usb 5-5: reset high-speed USB device number 3 using ehci-pci
[ 116.032583] sd 4:0:0:0: [sdb] Unhandled sense code
[ 116.032595] sd 4:0:0:0: [sdb]
[ 116.032600] Result: hostbyte=0x00 driverbyte=0x08
[ 116.032605] sd 4:0:0:0: [sdb]
[ 116.032608] Sense Key : 0x3 [current]
[ 116.032615] sd 4:0:0:0: [sdb]
[ 116.032618] ASC=0x12 ASCQ=0x0
[ 116.032623] sd 4:0:0:0: [sdb] CDB:
[ 116.032626] cdb[0]=0x28: 28 00 57 54 52 ee 00 00 08 00
[ 116.032640] end_request: I/O error, dev sdb, sector 1465144046
[ 116.032648] Buffer I/O error on device sdb2, logical block 1269825776
[ 116.032655] Buffer I/O error on device sdb2, logical block 1269825777
[ 116.032660] Buffer I/O error on device sdb2, logical block 1269825778
[ 116.032665] Buffer I/O error on device sdb2, logical block 1269825779
[ 116.032669] Buffer I/O error on device sdb2, logical block 1269825780
[ 116.032673] Buffer I/O error on device sdb2, logical block 1269825781
[ 116.032678] Buffer I/O error on device sdb2, logical block 1269825782
[ 116.032682] Buffer I/O error on device sdb2, logical block 1269825783
[ 116.192558] sd 4:0:0:0: [sdb] Unhandled sense code
[ 116.192568] sd 4:0:0:0: [sdb]
[ 116.192572] Result: hostbyte=0x00 driverbyte=0x08
[ 116.192577] sd 4:0:0:0: [sdb]
[ 116.192580] Sense Key : 0x3 [current]
[ 116.192586] sd 4:0:0:0: [sdb]
[ 116.192589] ASC=0x12 ASCQ=0x0
[ 116.192594] sd 4:0:0:0: [sdb] CDB:
[ 116.192597] cdb[0]=0x28: 28 00 0b a4 51 3f 00 00 08 00
[ 116.192610] end_request: I/O error, dev sdb, sector 195318079
[ 116.192617] Buffer I/O error on device sdb1, logical block 195318016
[ 116.349174] sd 4:0:0:0: [sdb] Unhandled sense code
[ 116.349186] sd 4:0:0:0: [sdb]
[ 116.349191] Result: hostbyte=0x00 driverbyte=0x08
[ 116.349196] sd 4:0:0:0: [sdb]
[ 116.349199] Sense Key : 0x3 [current]
[ 116.349206] sd 4:0:0:0: [sdb]
[ 116.349209] ASC=0x12 ASCQ=0x0
[ 116.349214] sd 4:0:0:0: [sdb] CDB:
[ 116.349217] cdb[0]=0x28: 28 00 57 54 52 ee 00 00 01 00
[ 116.349230] end_request: I/O error, dev sdb, sector 1465144046
[ 116.509279] sd 4:0:0:0: [sdb] Unhandled sense code
[ 116.509291] sd 4:0:0:0: [sdb]
[ 116.509295] Result: hostbyte=0x00 driverbyte=0x08
[ 116.509300] sd 4:0:0:0: [sdb]
[ 116.509304] Sense Key : 0x3 [current]
[ 116.509311] sd 4:0:0:0: [sdb]
[ 116.509314] ASC=0x12 ASCQ=0x0
[ 116.509319] sd 4:0:0:0: [sdb] CDB:
[ 116.509322] cdb[0]=0x28: 28 00 57 54 52 ef 00 00 07 00
[ 116.509336] end_request: I/O error, dev sdb, sector 1465144047
[ 116.669240] sd 4:0:0:0: [sdb] Unhandled sense code
[ 116.669249] sd 4:0:0:0: [sdb]
[ 116.669253] Result: hostbyte=0x00 driverbyte=0x08
[ 116.669258] sd 4:0:0:0: [sdb]
[ 116.669261] Sense Key : 0x3 [current]
[ 116.669267] sd 4:0:0:0: [sdb]
[ 116.669270] ASC=0x12 ASCQ=0x0
[ 116.669275] sd 4:0:0:0: [sdb] CDB:
[ 116.669278] cdb[0]=0x28: 28 00 0b a4 51 3f 00 00 08 00
[ 116.669291] end_request: I/O error, dev sdb, sector 195318079
[ 116.825843] sd 4:0:0:0: [sdb] Unhandled sense code
[ 116.825852] sd 4:0:0:0: [sdb]
[ 116.825856] Result: hostbyte=0x00 driverbyte=0x08
[ 116.825860] sd 4:0:0:0: [sdb]
[ 116.825863] Sense Key : 0x3 [current]
[ 116.825870] sd 4:0:0:0: [sdb]
[ 116.825873] ASC=0x12 ASCQ=0x0
[ 116.825877] sd 4:0:0:0: [sdb] CDB:
[ 116.825880] cdb[0]=0x28: 28 00 0b a4 51 fe 00 00 08 00
[ 116.825892] end_request: I/O error, dev sdb, sector 195318270
[ 116.982587] sd 4:0:0:0: [sdb] Unhandled sense code
[ 116.982599] sd 4:0:0:0: [sdb]
[ 116.982603] Result: hostbyte=0x00 driverbyte=0x08
[ 116.982608] sd 4:0:0:0: [sdb]
[ 116.982611] Sense Key : 0x3 [current]
[ 116.982618] sd 4:0:0:0: [sdb]
[ 116.982621] ASC=0x12 ASCQ=0x0
[ 116.982626] sd 4:0:0:0: [sdb] CDB:
[ 116.982629] cdb[0]=0x28: 28 00 0b a4 51 e7 00 00 08 00
[ 116.982642] end_request: I/O error, dev sdb, sector 195318247
[ 117.139178] sd 4:0:0:0: [sdb] Unhandled sense code
[ 117.139189] sd 4:0:0:0: [sdb]
[ 117.139193] Result: hostbyte=0x00 driverbyte=0x08
[ 117.139198] sd 4:0:0:0: [sdb]
[ 117.139201] Sense Key : 0x3 [current]
[ 117.139208] sd 4:0:0:0: [sdb]
[ 117.139211] ASC=0x12 ASCQ=0x0
[ 117.139216] sd 4:0:0:0: [sdb] CDB:
[ 117.139219] cdb[0]=0x28: 28 00 0b a4 51 fe 00 00 01 00
[ 117.139232] end_request: I/O error, dev sdb, sector 195318270
[ 117.295904] sd 4:0:0:0: [sdb] Unhandled sense code
[ 117.295913] sd 4:0:0:0: [sdb]
[ 117.295917] Result: hostbyte=0x00 driverbyte=0x08
[ 117.295922] sd 4:0:0:0: [sdb]
[ 117.295925] Sense Key : 0x3 [current]
[ 117.295932] sd 4:0:0:0: [sdb]
[ 117.295935] ASC=0x12 ASCQ=0x0
[ 117.295940] sd 4:0:0:0: [sdb] CDB:
[ 117.295943] cdb[0]=0x28: 28 00 0b a4 51 ff 00 00 07 00
[ 117.295955] end_request: I/O error, dev sdb, sector 195318271
[ 117.452511] sd 4:0:0:0: [sdb] Unhandled sense code
[ 117.452520] sd 4:0:0:0: [sdb]
[ 117.452524] Result: hostbyte=0x00 driverbyte=0x08
[ 117.452529] sd 4:0:0:0: [sdb]
[ 117.452532] Sense Key : 0x3 [current]
[ 117.452538] sd 4:0:0:0: [sdb]
[ 117.452541] ASC=0x12 ASCQ=0x0
[ 117.452546] sd 4:0:0:0: [sdb] CDB:
[ 117.452549] cdb[0]=0x28: 28 00 0b a4 51 e7 00 00 08 00
[ 117.452562] end_request: I/O error, dev sdb, sector 195318247
[ 117.609238] sd 4:0:0:0: [sdb] Unhandled sense code
[ 117.609247] sd 4:0:0:0: [sdb]
[ 117.609251] Result: hostbyte=0x00 driverbyte=0x08
[ 117.609256] sd 4:0:0:0: [sdb]
[ 117.609258] Sense Key : 0x3 [current]
[ 117.609265] sd 4:0:0:0: [sdb]
[ 117.609268] ASC=0x12 ASCQ=0x0
[ 117.609273] sd 4:0:0:0: [sdb] CDB:
[ 117.609275] cdb[0]=0x28: 28 00 0b a4 52 06 00 00 08 00
[ 117.765841] sd 4:0:0:0: [sdb] Unhandled sense code
[ 117.765849] sd 4:0:0:0: [sdb]
[ 117.765853] Result: hostbyte=0x00 driverbyte=0x08
[ 117.765858] sd 4:0:0:0: [sdb]
[ 117.765861] Sense Key : 0x3 [current]
[ 117.765867] sd 4:0:0:0: [sdb]
[ 117.765870] ASC=0x12 ASCQ=0x0
[ 117.765875] sd 4:0:0:0: [sdb] CDB:
[ 117.765877] cdb[0]=0x28: 28 00 00 00 00 3f 00 00 08 00
[ 117.922568] sd 4:0:0:0: [sdb] Unhandled sense code
[ 117.922576] sd 4:0:0:0: [sdb]
[ 117.922580] Result: hostbyte=0x00 driverbyte=0x08
... (errors repeat)
If I try to 'mount' it as root I get:
mount: wrong fs type, bad option, bad superblock on /dev/sdb2,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
The drive is OK. I was able to use it on other computers, reiserfsck showed no errors. Also my computer is OK, and I was able to mount the drive using some old arch linux cd.
The system is 64-bit, I use the default kernel (3.9.2-1-ARCH x86_64). I wonder, what could be missing in my configuration?
I'm able to use other USB pendrives, hard disks, mouse with no problems
Last edited by senjin (2013-05-12 10:27:29)

For comparison, I attach dmesg log from another computer, which sees the drive normally:
[ 576.596709] usb 5-3: new high-speed USB device number 3 using ehci-pci
[ 577.092795] Initializing USB Mass Storage driver...
[ 577.092922] usbcore: registered new interface driver usb-storage
[ 577.092926] USB Mass Storage support registered.
[ 577.096041] scsi6 : usb-storage 5-3:1.0
[ 577.096429] usbcore: registered new interface driver ums-cypress
[ 578.097696] scsi 6:0:0:0: Direct-Access Hitachi HTS547575A9E384 PQ: 0 ANSI: 0
[ 578.100360] sd 6:0:0:0: [sdb] 1465149168 512-byte logical blocks: (750 GB/698 GiB)
[ 578.101488] sd 6:0:0:0: [sdb] Write Protect is off
[ 578.101499] sd 6:0:0:0: [sdb] Mode Sense: 03 00 00 00
[ 578.102675] sd 6:0:0:0: [sdb] No Caching mode page present
[ 578.102687] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 578.105731] sd 6:0:0:0: [sdb] No Caching mode page present
[ 578.105741] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 578.140717] sdb: sdb1 sdb2
[ 578.143382] sd 6:0:0:0: [sdb] No Caching mode page present
[ 578.143391] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 578.143398] sd 6:0:0:0: [sdb] Attached SCSI disk
The computer which doesn't open the drive is fairly old (AMD Athlon 64, MSI K8T Neo2). I wonder, maybe there is some module or firmware that has been recently dropped from the default setup, that I need to install separately?

USB drive started unmounting itself after OS X update

Similar Messages

Maybe you are looking for