[SOLVED] (hopefully) USB Hard drive disconnects

I have a 2TB SATA drive which I used in a stationary computer (as a server). The drive is encrypted using LUKS and for a filesystem I use xfs. Unfortunately that computer died, so I figured I'd migrate everything over to a laptop instead. I put the 2TB SATA drive in an USB drive adapter, and it worked as it expected.
Until a few hours after when I suddenly couldn't use the drive any longer. It always happens after I haven't used the drive in a little while.
dmesg shows the following relevant information:
[ 81.300065] usb 1-2: new high speed USB device number 2 using ehci_hcd
[ 81.516917] usbcore: registered new interface driver uas
[ 81.538799] Initializing USB Mass Storage driver...
[ 81.538966] scsi2 : usb-storage 1-2:1.0
[ 81.539424] usbcore: registered new interface driver usb-storage
[ 81.539429] USB Mass Storage support registered.
[ 82.548407] scsi 2:0:0:0: Direct-Access WDC WD20 EARS-00J2GB0 PQ
: 0 ANSI: 2
[ 82.551630] sd 2:0:0:0: Attached scsi generic sg2 type 0
[ 82.552000] sd 2:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.
81 TiB)
[ 82.554255] sd 2:0:0:0: [sdb] Write Protect is off
[ 82.554262] sd 2:0:0:0: [sdb] Mode Sense: 38 00 00 00
[ 82.554266] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[ 82.557630] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[ 82.593632] sdb: unknown partition table
[ 82.597254] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[ 82.597262] sd 2:0:0:0: [sdb] Attached SCSI disk
[ 104.697278] XFS (dm-1): Mounting Filesystem
[ 105.023577] XFS (dm-1): Ending clean mount
[ 4249.281149] usb 1-2: USB disconnect, device number 2
[ 4440.332930] INFO: task khubd:370 blocked for more than 120 seconds.
[ 4440.332935] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 4440.332939] khubd D 00000000 0 370 2 0x00000000
[ 4440.332947] dea97d74 00000046 c1030357 00000000 00000001 00000003 5d6764c7 000003dd
[ 4440.332956] 00000096 ddd02180 dea97d04 c10303a4 00000000 00000096 dea97d18 c1527480
[ 4440.332965] ddc84c38 c1527480 dec06480 de38f8e0 de2a0d20 00000000 00024592 00000000
[ 4440.332974] Call Trace:
[ 4440.332987] [<c1030357>] ? __wake_up_common+0x47/0x70
[ 4440.332993] [<c10303a4>] ? __wake_up_locked+0x24/0x30
[ 4440.332998] [<c10318ab>] ? cpuacct_charge+0x5b/0x70
[ 4440.333006] [<c11bd4b4>] ? rb_insert_color+0xc4/0x100
[ 4440.333014] [<c13487d5>] schedule_timeout+0x265/0x2e0
[ 4440.333022] [<c103f883>] ? check_preempt_wakeup+0x123/0x1b0
[ 4440.333028] [<c1036f72>] ? check_preempt_curr+0x72/0x90
[ 4440.333033] [<c1347527>] wait_for_common+0x97/0x120
[ 4440.333038] [<c10410a0>] ? try_to_wake_up+0x350/0x350
[ 4440.333043] [<c13475c7>] wait_for_completion+0x17/0x20
[ 4440.333048] [<c106390e>] kthread_stop+0x3e/0x130
[ 4440.333058] [<e00e6178>] release_everything+0x28/0xa0 [usb_storage]
[ 4440.333064] [<e00e620f>] usb_stor_disconnect+0x1f/0x30 [usb_storage]
[ 4440.333089] [<e0f9d64c>] usb_unbind_interface+0x3c/0x140 [usbcore]
[ 4440.333096] [<c1264271>] __device_release_driver+0x51/0xb0
[ 4440.333101] [<c12642f4>] device_release_driver+0x24/0x40
[ 4440.333106] [<c1263e6a>] bus_remove_device+0x5a/0x80
[ 4440.333110] [<c1261dc8>] device_del+0x108/0x170
[ 4440.333121] [<e0f9b691>] usb_disable_device+0x91/0x1a0 [usbcore]
[ 4440.333130] [<e0f94d1a>] usb_disconnect+0x9a/0x120 [usbcore]
[ 4440.333141] [<e0f967dc>] hub_thread+0x86c/0xf60 [usbcore]
[ 4440.333146] [<c1347a25>] ? schedule+0x275/0x9c0
[ 4440.333151] [<c1040efc>] ? try_to_wake_up+0x1ac/0x350
[ 4440.333157] [<c1063fa0>] ? abort_exclusive_wait+0x80/0x80
[ 4440.333161] [<c1031b4e>] ? complete+0x4e/0x60
[ 4440.333172] [<e0f95f70>] ? usb_remote_wakeup+0x40/0x40 [usbcore]
[ 4440.333176] [<c10638bd>] kthread+0x6d/0x80
[ 4440.333181] [<c1063850>] ? kthread_worker_fn+0x160/0x160
[ 4440.333187] [<c134b8be>] kernel_thread_helper+0x6/0x10
At first I figured the drive was suspending, so I've tried to play with the settings in /sys/bus/usb/devices/.../power/. To my knownledge the default settings are set to never suspend, and the dmesg doesn't say anything about suspending any drives (should it?), so I doubt this is the case. And also, I can still hear that the drive is on.
I have tried changing the USB cable but I got the same error.
So I figure, it's either a hardware problem (the USB drive adapter is bad) or it's the kernel -- I've read through some mailing lists that older kernels had some problems with USB devices disconnecting.
What I would like to try is to disable ehci_hcd and try to use a different module, though I need a little help with what module and how I would go about doing this. (I see in the lspci a reference to uhci, maybe try that?).
Anyone has any other ideas I can try that would also be greatly appreciated.
Thanks in advance.
lspci
00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 03)
00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev d3)
00:1e.2 Multimedia audio controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller (rev 03)
00:1f.0 ISA bridge: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) IDE Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller (rev 03)
02:01.0 CardBus bridge: Texas Instruments PCI1510 PC card Cardbus Controller
02:03.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)
02:08.0 Ethernet controller: Intel Corporation 82562ET/EZ/GT/GZ - PRO/100 VE (LOM) Ethernet Controller Mobile (rev 03)
lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 04fc:0c25 Sunplus Technology Co., Ltd SATALink SPIF225A
Last edited by Canute (2011-07-29 13:36:55)

I think I may have fixed it, or rather; it has worked the last 8 hours which is twice as long as the longest it did before.
Through ubuntu's bug tracker I found out that there appears to be a bug in the kernel (#32432). From what I read on the bugzilla, that bug appears to be only for 2.6.27-2.6.38 (is it??) and I was using 2.6.39 so I was really unsure if that bug applied to my kernel.
Nevertheless I built my own kernel with the help of abs. I used linux version 2.6.38, the standard arch linux patch for 2.6.38 and the patch located here.

Similar Messages

External USB Hard Drive disconnects during large file transfers.

I have a Western Digital 2TB USB Hard Drive that Ive been using perfectly for a couple of years on my MacBook Pro. A couple of months ago I bought a 27inch iMac and started using it as my main computer. So I had that hard drive connected to my iMac.
I started to notice that during large transfers (be it many files or 1 big one), usually into the Gigs, I suddenly got a warning message saying that the Hard Drive was inappropriately disconnected. It doesnt appear in Disk Utility so I have to manually connect and disconnect the drive in order for it to show up again on the iMac. I tested it again on my MacBook and the same thing happened.
Another problem:
Sometimes it will dissappear from the iMac without a warning message, it just doesnt show up. (Usually after long periods of inactivity). I then have to manually disconnect and connect for it to show up.
So what do you think? Is my Hard Drive Dying?

I've been having similar problems with Lion on both external USB2 drive docks and more recently a Mediasonic 4 bay Firewire RAID drive. It was suggested that powersaving mode shut these down but changing that didn't completely solve the problem. I'm returning the Mediasonic for a replacement but suspect that it is something in the OS that is causing it.
If the replaced drive still causes the problem, I'll do a rebuilt of the system, eliminating apps that were migrated over, even though the system is only 5 months old. If anyone has solved similar issues, please let me know as well. Thanks.

USB Hard Drives Keep Disconnecting or Not Responding

Hi,
This is a long post - but one that I hope someone can offer advice on.
The Hardware
Mac Pro running OSX 10.8 (but this has happened on all versions of the OS i.e. 10.6/.7 etc)
3 x Internal SATA Hard Drives - All working perfectly.
External Drives:
2 x Western Digital My Book 1TB USB Hard Drives
1 x Seagate 750GB Hard Drive with USB2 connectivity
2 x IcyBox Dual Bay USB2 hard Drive enclosures using JMicron Chipsets - these enclosures have 2 x 1TB Western Digital Green in each (totaling 4 TB across the 2 enclosures).
D-Link 7 Port USB2 Hub
The Problem
- USB Hard Drives connected to the Mac are ejected from the system without notice and at random times AND/OR
- The external hard drive remains mounted, but when trying to write to the drive/partitions, Finder throws an error message up saying the operation cannot be completed - error code -50.
- Time Machine: TM will back up successfully several times, before eventually throwing an error up that it cannot create the folders required on the drive.
- The only way to be able to use the drives again is either remount the drive, or in some case, it is required to completely power the drive down and then reconnect.
Re-creating the problem
I have honestly not found a sure-fire way of replicating the problem. It seems completely random. It happens when I am actually sat at the computer, but it also happens when I am away from the computer.
In the past - my Time Machine hard drive has been one of the Western Digital MyBook drives. I also used the second MyBook for SuperDuper backups (extra redundancy). The 4TB drives in the IcyBox enclosures have been used to backup my ripped movie collection.
Recently however - I decided to have 2 of the 1TB drives in the IcyBox enclosures to be TM and SuperDuper backups. I have however reverted TM back to one of the Western Digital drives, purely for testing purposes. SuperDuper is backing up to one of the 1TB drives in the IcyBox.
I am trying various things to see if I can find the issue, but it is such a random event that it is taking ages to even come close to find a problem. Sometimes the drives will stay active for a few days, sometimes only a few hours, even minutes.
Theories
I have several theories as to why my USB drives continually disconnect.
1. The D-Link USB Hub.
Could connecting the drives through the hub be causing the problem? I don't really see how, unless it is a documented case that D-Link USB hubs do not play nice with OSX? To try and rule this out I have connected the current Time Machine back up drive (Western Digital MyBook) directly to the USB port on the back of the computer. The SuperDuper (IcyBox enclosure) drive is currently connected through the D-Link hub. I have removed all the other drives from the enclosures - so at present I have only 2 external drives connected (1 x 1TB Western Digital MyBook, 1 x 1TB Western Digital Green inside one of the IcyBox dual-bay enclosures - connected through D-Link Hub).
2. JMicron Chipset
I have done a bit of research on the internet and there are a few indications that perhaps JMicron SATA-to-USB controller chipsets found in a lot of external hard drive enclosures (including the dual bay IcyBox external enclosures that I have) do not play nice with OSX. If the JMicron chipsets in the 2 IcyBox enclosures is a problem - would that cause issues with other USB devices on the USB bus off the Mac? (i.e. can the JMicron chipset in the enclosures cause devices such as the WD MyBook drives which I assume use a non-JMicron chipset, to experience similar failures?)
3. Green Hard Drives
As I have said, I have 4 Western Digital Green 1TB hard drives inside the IcyBox Dual Bay Enclosures. Could the fact that these drives are 'Green' be causing a problem? They do go to sleep after x number of minutes, but they do wake up when required. But could on the occasion when I have problems, could this be caused by the 'Green' feature interrupting OSX in waking the drives? Coupled with JMicron chipset, could this be compounding the issue?
Possible Solutions
I am prepared to spend money on replacement drives and/or enclosures etc - but I would hate to spend x amount of money and have the same problem. So I am hoping to get some advice on what drives/enclosures are more than likely to work flawlessly with OSX.
Thanks for reading!

FYI - re: the SuperDuper drive that is in one of the IcyBox enclosures.
I just opened this drive up in Finder. I heard the drive wake up, but when I came to copy a file over (tried various file sizes) - I got the error -50 message.
Here is the info from Console.
31/07/2012 23:35:52.000 kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
31/07/2012 23:35:52.000 kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
31/07/2012 23:35:53.000 kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
31/07/2012 23:35:53.000 kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
31/07/2012 23:35:53.000 kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
31/07/2012 23:35:53.000 kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
31/07/2012 23:35:53.000 kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
31/07/2012 23:35:53.000 kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
31/07/2012 23:35:53.000 kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
31/07/2012 23:35:53.000 kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
31/07/2012 23:35:53.000 kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
31/07/2012 23:35:53.000 kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
31/07/2012 23:35:53.000 kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
31/07/2012 23:35:53.000 kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
31/07/2012 23:35:53.000 kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
31/07/2012 23:35:53.000 kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
31/07/2012 23:35:53.000 kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
31/07/2012 23:35:53.000 kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
31/07/2012 23:35:53.000 kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
31/07/2012 23:35:53.000 kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
31/07/2012 23:35:53.000 kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
31/07/2012 23:35:53.000 kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
31/07/2012 23:35:53.000 kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
31/07/2012 23:35:53.000 kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
31/07/2012 23:35:53.000 kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
31/07/2012 23:35:53.000 kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
31/07/2012 23:35:53.000 kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
31/07/2012 23:35:53.000 kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
31/07/2012 23:35:53.000 kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
31/07/2012 23:35:53.000 kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
31/07/2012 23:35:53.000 kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
31/07/2012 23:35:53.000 kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
31/07/2012 23:35:53.000 kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
31/07/2012 23:35:53.000 kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
31/07/2012 23:35:53.000 kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
31/07/2012 23:35:53.000 kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
31/07/2012 23:35:53.000 kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
31/07/2012 23:35:53.000 kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
31/07/2012 23:35:53.000 kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
31/07/2012 23:35:53.000 kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
31/07/2012 23:35:53.000 kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
31/07/2012 23:35:53.000 kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
31/07/2012 23:35:53.000 kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
31/07/2012 23:35:53.000 kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
31/07/2012 23:35:53.320 fseventsd[55]: disk logger: failed to open output file /Volumes/Data 1/.fseventsd/0000000002478a7f (No such file or directory). mount point /Volumes/Data 1/.fseventsd
31/07/2012 23:35:53.320 fseventsd[55]: disk logger: failed to open output file /Volumes/Data 1/.fseventsd/0000000002478a7f (No such file or directory). mount point /Volumes/Data 1/.fseventsd
Also, while the drive was inaccessible, I tried 'Verify Disk' in Disk Utility - here are the results
Verifying volume “SuperDuper”
Checking file systemPerforming live verification.
Checking Journaled HFS Plus volume.
Checking extents overflow file.
Checking catalog file.
Checking multi-linked files.
Checking catalog hierarchy.
Checking extended attributes file.
Invalid leaf record count
(It should be 2 instead of 1)
Checking volume bitmap.
Checking volume information.
The volume SuperDuper was found corrupt and needs to be repaired.
Error: This disk needs to be repaired. Click Repair Disk.
Please also note that the all my external hard drives have recently been reformated using GUID part. map and HFS Journaled.

[SOLVED] Kernel panic when using external USB hard drive

I have a desktop PC with a 64 bit arch install, on a Core2 Duo 6320 CPU. I have been using (and continue using right now) a 500 GB "Iomega Desktop Hard Drive" external USB hard disk without problems. But I have just bought a 3 TB "Seagate Expansion" external USB hard drive and I'm unable to use it from my Arch install. Each time I try to format it or to copy data from the PC, Arch freezes with a kernel panic. Sometimes it freezes faster and I cannot see anything, but others I am able to see the following kernel messages, repeating several times:
[11701.205071] sd 3:0:0:0: [sdf] uas_eh_abort_handler ffff880014e13380 tag 29, inflight: CMD
[11701.221297] sd 3:0:0:0: [sdf] abort completed
[11701.221313] scsi host3: uas_eh_task_mgmt: ABORT TASK failed (wrong tag 0/256)
[11701.221323] sd 3:0:0:0: [sdf] uas_eh_abort_handler ffff880014e13500 tag 30, inflight: CMD
[11701.237550] sd 3:0:0:0: [sdf] abort completed
[11701.237567] scsi host3: uas_eh_task_mgmt: ABORT TASK failed (wrong tag 0/256)
[11701.237576] sd 3:0:0:0: [sdf] uas_eh_abort_handler ffff880014e13680 tag 31, inflight: CMD
[11701.253922] sd 3:0:0:0: [sdf] abort completed
[11701.253936] scsi host3: uas_eh_task_mgmt: ABORT TASK failed (wrong tag 0/256)
[11701.253956] sd 3:0:0:0: uas_eh_device_reset_handler
[11704.252182] scsi host3: uas_eh_task_mgmt: LOGICAL UNIT RESET timed out
[11704.252196] scsi host3: uas_eh_bus_reset_handler start
[11704.252443] usb 5-6: stat urb: killed, stream 0
[11704.358882] usb 5-6: reset high-speed USB device number 3 using ehci-pci
[11704.483206] scsi host3: uas_eh_bus_reset_handler success
Strange enough, the drive is listed by lsusb command as a 2TB but I don't think this is related to the problem (as the OS sees the 3 TB). This is the lsusb output:
Bus 001 Device 003: ID 0bc2:3312 Seagate RSS LLC SRD00F2 [Expansion Desktop Drive 2TB]
I have tried the drive on other PCs and it works flawlessly. Also tried booting Windows 8 on the same PC I have Arch installed in, and in Windows it also works perfect. I have tried using ext2 and NTFS filesystems. Tried also changing the USB cable without success. And right now I'm out of ideas. Any suggestions?
Last edited by doragasu (2014-07-03 11:06:25)

looks like it could be the UAS module , check https://bbs.archlinux.org/viewtopic.php?id=183190

USB hard drive kills trackpad

I left my mid 2010 MacBook Pro 13" running for a few hours, cloning my internal hard drive using Disk Utility to a new USB hard drive, ready for a transplant. It's not the first time I've done this, last time it all went well. This time, when I came back to it, it appeared to have finished, but the trackpad was unresponsive. The keyboard worked fine, spotlight search appeared immediately, and searched as quick as ever, so there's nothing wrong with the processor or hard drive. The pointer would move about a minute after I used the trackpad, which is more or less unusable, and I was unable to eject the USB hard drive properly, so I yanked the cable. The screen went black for half a second then came back and the trackpad was working perfectly again. What's going on, and what should I have done differently?

I was on the phone with Apple for over an hour and unfortunately we don't have any solutions. But they took extensive documentation of the problem and said they would transfer it off to their engineering team and hopefully get back to me early next week.
They seemed truly appreciative of the bug report and interested to see what the problem was. If you have AppleCare I'd STRONGLY recommend that you call them and report the issue as well. The more people who report it the more likely we'll see a fix.
I ended up pulling the drive out of my USB case and transferring it to another FireWire case to get my data off of it. It doesn't solve the problem but it at least allowed me to access my data.

XP sp3 cannot see usb hard drive connected to airport extreme 802.11n

I have a sata drive that the airport utility recognizes. I attempted to follow the instructions from post HT1331 but no luck yet. I also reformatted the drive from ntfs to fat32 using vista but with the same result.
I found another post while writing this one which solved my problem. It turns out how I formatted the drive wasn't usable by AEBS.
Connecting Large USB Hard Drives to Airport Extreme
I needed to format the drive using the instructions found below.
http://www.ridgecrop.demon.co.uk/index.htm?fat32format.htm
After doing this and plugging in the drive I was able to use the drive intended. Since I had started the post I figured I would list the solution.
Cheers!

I don't think two problem are related. Now, for PC, try to disable the firewall software if you ave one. Some firewall can block it, like for ex PC Tools firewall, or ZonaAlarm. Some of them you can configure to work with disk agent.

USB hard drive not detected on reboot

I am running Windows 7 Ulitmate 64-bit on my 2011 15" Macbook Pro. I have a USB Hard Drive (WD My Passport SE - USB 3.0/2.0 - 1 TB).
The hard drive is formatted for HFS+ and I am running Mac Drive 8 to detect it in Windows.
For some reason when I reboot (in Windows), the hard drive won't be there until I unplug it and plug it back in.
This is really annoying! Can anybody help me? I'm pretty good with things like this but I can't think of any reason this shouldn't be working right.
HELP =T
Message was edited by: PTHEOFYL
Message was edited by: PTHEOFYL

I am having the exact same problem. WD 1TB Passport. USB 3.0 drive. Running on Windows 7 Pro 64 via Bootcamp.
My 1TB Passport is formatted with FAT32 and works with Windows and Mac OS.
I was getting the same problem when I was running Windows XP Pro on the same MacBook Pro. I was hoping the upgrade to Windows 7 would remidy the issue but it did not.
The drive light is on in a steady state when I boot and I have the same symptoms as reported by everyone else above.
In my research, I am leaning towards thinking that it is a power issue related to the cable used to connect the USB 3.0 Drive or something to do with the USB driver for Bootcamp, but researching the WD site suggests it's a power issue, not a faulty or failing drive.
I have a 500GB WD Passport USB 2.0 also attached to my computer, also running FAT32 and it starts up no problem. It's just the USB 3.0 drive that is having this issue.
Also worth noting; the drive is detected properly when I boot in Mac OS X. It's only the Windows side I have to unplug and plug back in to access the drive.

USB Hard drive, permission issue on one partition

Hi,
I have an issue with my USB hard drive, when I pluged it the 3 partitions are mounted, and 2 of them grant access to the users group:
mount
/dev/sdc6 on /media/usbhd-sdc6 type ext2 (rw,relatime)
/dev/sdc1 on /media/usbhd-sdc1 type fuseblk (rw,nosuid,nodev,allow_other,blksize=4096,default_permissions)
/dev/sdc5 on /media/usbhd-sdc5 type vfat (rw,relatime,utf8,gid=100,umask=002)
ls -l /media/
drwxrwxr-x 1 root users 4096 Jun 29 22:21 usbhd-sdc1
drwxrwxr-x 18 root users 16384 Dec 31 1969 usbhd-sdc5
drwxr-xr-x 3 root root 4096 Jun 29 22:21 usbhd-sdc6
I read the wiki page about udev, but I can not solve this issue.
PS : HAL is removed from my daemons list.

> You can write on "usb" because the right are : drwxrwxrwx
They appear only when I use 'sudo mount -o rw,noauto,async,user,umask=1000' instead of plain 'sudo mount /dev/sdb1 /mnt/usb2'.
I use vfat for that USB stick, so maybe that's why it works for me. The first two listings in your first post show the drives in different order, but of course the mountpoints show that the offending drive is ext2 not vfat, my bad.
Edit: This is how my ext3 USB stick behaves like:
[karol@black test]$ sudo mount /dev/sdb1 /mnt/usb
[karol@black test]$ mount | grep sdb1
/dev/sdb1 on /mnt/usb type ext3 (rw)
[karol@black test]$ ls -l /mnt
total 8
drwxr-xr-x 2 karol users 4096 07-03 01:08 usb
drwxr-xr-x 2 root root 4096 2009-09-14 usb2
This time /mnt/usb is an ext3. As you can see, there's no root, I (karol) an the owner, so I can rw to my heart's content. Maybe you should change the ownership - 'chown' (man chown if you're not familiar w/ that command).
Last edited by karol (2010-07-02 23:05:52)

External USB Hard Drive not showing up on Time Capsule

Hi all,
I have a 500 Gb Time Capsule that used to be able to detect my external USB hard drives. I had to store my things for a while and have just started using the Time Capsule again. The TC works fine, however, the same USB external hard drives I used to connect to the TC are not showing up anymore :s They show up on the desktop when I connect them directly to my MacBook via USB. I have been through most of the file sharing options in Airport Utility and System Preferences but have not been able to solve this. I can't think of any settings that would have changed from when they were showing up in the past. Any help would be greatly appreciated. Thx

yosemite won't work with ntfs drives for some reason, i've had the same issue with my toshiba. i thought ok lemme buy another one, and transfer it over maybe it's a driver issue which i've tried over and over, apple support can't figure it out.
here's a simple fix, but the problem is i have an external where all my photography and video files are stored, so i can't access them right now and it's making my life ****.
http://guides.macrumors.com/Formatting_an_External_Device
that does work and make the drive mountable now, but problem being i can't obviously reformat the old drive and lose everything. once the new drive is formatted for mac i can't plug it into a pc to transfer the files from. which is the only problem now. but formatting the drive for mac only DOES work. but you're just screwed and not able to use it ntfs. hope the link helps SOME people.

Airport "sees" USB hard drives, but Finder can't find them!

Yesterday, my iMac's Finder could see my external USB hard drive connected to AIrport, but not today. Airport sees it right now--I've checked and updated it and restarted it. Finder still can't find the drive. I click on my Airport connection in the Finder sidebar, my usual route to the hard drive, but the connection window hangs. And hangs. I need access to the files on that hard drive. Problem is, another iMac using Tiger needs access, too, so I can't disconnect arbitrarily. With that iMac, Tiger's Finder sees the files, and can access them. But not this 20" 2.4G iMac with Leopard 10.5.3. What's going on?

floba,
the first solution, clearing the entire index and letting it rebuild, did not work.
But setting the drive in 'privacy' and then removing it did immediately work, my search window which was left open refreshed instantly to reveal my items. I'm curious however if it will stick..
i have another issue that may be completely unrelated, but maybe not..
i clear my spotlight shortcut key (command+spacebar) because it conflicts with common Adobe app commands i use. But i frequently will find that this shortcut key is RE-ENABLED. At the same time, my shortcut to use Spaces (command+f8, command+arrow keys, and command+numk keys) are CLEARED as if i had never set them. This happens consistently and is frustrating. I don't reboot very often, but i under 10.5.2 i often came home to find my computer has locked up, so it would seem these shortcuts all reset when i reboot, and i wonder if my external drive index is lost every time the drives are ejected.
Vista's completely useless search features were a main reason i gave my PC's away and bought macs. I'm obviously finding these failings frustrating on the mac. I'm even more disappointed at the news Snow Leopard is a bug fix and is selling as a separate OS. Installing additional programs is not an option, i want the OS to do what i tell it to do /rant

Time Machine External Hard Drive Disconnected Incorrectly

I have an external USB hard drive functioning for my Time Machine back-ups. I usually turn off my iMac by using the sleep function. Often, when I activate out of sleep, I get the error message that the hard drive was disconnected incorrectly (I assume this means not ejected properly). But I haven't disconnected the USB wire. I can't figure ot why I am getting this message so often. Any ideas? Thanks.

mr1213 wrote:
I have an external USB hard drive functioning for my Time Machine back-ups. I usually turn off my iMac by using the sleep function. Often, when I activate out of sleep, I get the error message that the hard drive was disconnected incorrectly (I assume this means not ejected properly). But I haven't disconnected the USB wire. I can't figure ot why I am getting this message so often.
It may be that your TM drive isn't "waking up" quickly enough for Time Machine.
An improper disconnect (yes, not ejecting first) can cause directory damage to the disk. Do a +Repair Disk+ (not permissions) on your TM drive, via Disk Utility (in your Applications/Utilities folder).
Depending on your drive, one or more of the following may help:
Un-check the +Put the hard disk(s) to sleep ...+ option of System Preferences > Energy Saver.
See if it has an auto-sleep or "spin down" mode you can disable.
Check with the maker to see if there's a firmware upgrade for your model.

USB hard drive is not recognized on MBP running Lion

Hello,
I have:
- Freecom ToughDrive Pro USB hard drive
- New MBP running Lion 10.7.3
When I plug the disk in an USB port in the MBP, the light that indicates operation starts blinking but very lighltly colored and the disk is not recognized by the computer. I have put data on it using iMac Snow Leopard. I have plugged the disk into a MBP running Snow Leopard and it works. I have also tried another Lion (older MBP) and it also works.
What is wrong? How come the disk is not mounted or shown in Disk Utility. Can it be a power issue? Any ideas?
I have noticed there a lot of similar posts in the forum and none has been satisfactorily solved. Is this a mayor Lion bug? If yes, how can I downgrade to Snow Leopard?

dafnedr wrote:
Thanks for the reply.
However... how is it possible that with all other MBPs I have tried it works just fine? Has Apple lowered the power levels in recent models? The other MBP where I have tried the disk on are just over a year old, my current one is only a month old.
Are you saying that USB ports on different Apple computers are supplying different levels of power? That's psychotic! It should be a standard power level... or it should go up on newer models... not down!!!
I think I'm just gonna return this piece of scrape and get my old (one year old) MBP back... Snow Leopard was bliss compared to this... I rather go back than have to jump to a store to buy a cable to make something work that should work by default.
On the one Mac it does not work on that Mac does not put out enough power to fully power the drive. If it works on other Mac's we know that the drive works, so that question is answered. And it doesn't work on your newest Mac then there can only one answer, Not Enough Power is being put out by the USB port to fully power it.
Yes the one Mac that it is not working on has a lower USB power output. Why, I have no idea.
This is Very Common you can find posts about it on all notebook forums. Psychotic, No. Yes Mac is touted as "It Just Works" which is a flat out LIE.
Do what you think is best for you. Good Luck

CPU is very hot when using Thunderbolt display and mac attached USB hard drive for TimeMachine

Hello,
i've bought the new MacBook Pro 15" and a Thunderbolt display. Everything works fine for me due to the latest updates, but i experience an issue which i really don't understand. When i connect an usb hard drive for TimeMachine to my display it works like expected (CPU has a temperature of 64°C), but when i connect it to an usb port of the mac while using my display the CPU temperature goes crazy (spikes about 80°C) and it gets very noisy. Has anyone else experienced this behaviour?
May this has something to do with the dual graphics adapter and how the system handles the data stream to thunderbold ports and usb devices? Which graphics card is used for the external display, the internal gpu or the adapter from ati? I've googled a lot but haven't found appropriet answers about these questions.

Hi there ulairi9!
I understand how this would be a frustrating issue! I have an article here that can provide some troubleshooting steps for you, and can hopefully help you resolve the issue. That article specifically addresses the issue you are experiencing, and can be found here:
AirPort Extreme and Time Capsule: External USB drive becomes inaccessible
http://support.apple.com/kb/TS3271
Thanks for using the Apple Support Communities!
Cheers,
Braden

LaCie d2 195 GB USB hard drive and new iMac

Has anybody had a problem with a LaCie d2 drive that is connected via USB instead of FireWire? I have both types of external hard drives; the FireWire connected LaCie has worked flawlessly, as has a Seagate 300GB FireWire drive. But my poor little LaCie 195 GB USB hard drive bit the dust when I tried to copy my iPhoto library from it to the hard drive of my new iMac Intel Core. The entire Mac froze up, even though there was disk activity on the LaCie. After waiting for 25 minutes for the Mac to unfreeze, I finally manually powered down the system. Unfortunately this corrupted my LaCie disk, and it could not be repaired using Disk Utility. Even when I tried to repartition the drive, Disk Utility simply hung to the point where I had to do a Force Quit to get out of it.
I forgot to mention that I was connecting the LaCie through a powered USB 2.0 hub - that could be a source of the problem, but it worked flawlessly in my iMac G5. I did reconnect it directly to a USB port on the iMac, but still could not get Disk Utility to repartition the drive.
Luckily I had a secondary backup of my photo and music files, or I'd really be crying right now.
Any thoughts?
Thanks,
JD
PowerBook G4 12 Mac OS X (10.4.4)
PowerBook G4 12 Mac OS X (10.4.4)

Mac 1 Ghz G4 1 gig Ram Os 10.4.5
My Firewire connected LaCie Bigdrive started disconnecting spontaneously with a complaint from the iMac that it was disconnected improperly.
Finally it did so once more and has not mounted via FW since. However, USB does mount it but big files take all day to transfer.
I took out the Maxator from the LaCie drive and put it in a FW/USB caddy, ok for a while then the same story. USB only mounting.
Informed with some confidence by a poster on Bombich's website
( http://forums.bombich.com/viewtopic.php?p=25658#25658 ) that it was the boot drive OS
Tried new cable. repaired boot drive disc, repaired permissions, ran DiscWarrior over it, repaired permisssions, ran downloaded 10.4.5 combo, ran DiscWarrior over it and finally repaired permissions again.
No Joy.
i would most appreciate useful suggestions.
Regards and thanks in advance
Anoop in the UK
apollo11
View Public Profile
Send a private message to %1$s
Find More Posts by apollo11
Add apollo11 to Your Buddy List
Reply

Getting error while backing up database on a USB hard drive

Hi
I have run oracle 10g database installed on a Redhat linux AS4.I ran out of space so i tried to backup my database on a USB hard drive with RMAN.
I got this error in the middle of backup process.
ORA-19502: write error on file "/media/OneTouch_4/backup_dev/p9k30k6c_1_1", blockno 1969153 (blocksize=8192)
Note that i have not formatted the new hard drive in linux and just plug and play the hard drive.
I have read that i have to format the hard drive in linux (ex3).
what could be the problem? does the problem solve if i format the usb hard drive?
I will be grateful if i have your suggestions.
many thanks
Edited by: Hesam on Dec 24, 2008 8:21 AM

using target database control file instead of recovery catalog
connected to target database: ORCL (DBID=1137313685)
executing command: SET COMMAND ID
set command id to 'BACKUP_DATABASE_FU_122308090352';
echo set on
run {
allocate channel oem_backup_disk1 type disk format '/media
channel oem_backup_disk1: sid=564 devtype=DISK
allocated channel: oem_backup_disk1
allocated channel: oem_backup_disk2
channel oem_backup_disk2: sid=569 devtype=DISK
allocated channel: oem_backup_disk3
channel oem_backup_disk3: sid=716 devtype=DISK
channel oem_backup_disk4: sid=619 devtype=DISK
allocated channel: oem_backup_disk4
Starting backup at 23-DEC-08
channel oem_backup_disk1: starting full datafile backupset
channel oem_backup_disk1: specifying datafile(s) in backupset
input datafile fno=00131 name=/opt/oradata/datafile/undotbs01.dbf
input datafile fno=00087 name=/opt/oradata/datafile/KJ_ind.dbf
input datafile fno=00088 name=/opt/oradata/datafile/KB_ind.dbf
input datafile fno=00089 name=/opt/oradata/datafile/GU_DATA_reorg1.dbf
input datafile fno=00092 name=/opt/oradata/datafile/FO_ind.dbf
input datafile fno=00093 name=/opt/oradata/datafile/EB_ind.dbf
input datafile fno=00094 name=/opt/oradata/datafile/CT_ind.dbf
input datafile fno=00095 name=/opt/oradata/datafile/CM_DATA_reorg4.dbf
input datafile fno=00096 name=/opt/oradata/datafile/CM_ind.dbf
input datafile fno=00097 name=/opt/oradata/datafile/BI_ind_reorg0.dbf
input datafile fno=00100 name=/opt/oradata/datafile/KA_ind.dbf
input datafile fno=00101 name=/opt/oradata/datafile/SU_ind.dbf
input datafile fno=00103 name=/opt/oradata/datafile/NT_ind.dbf
input datafile fno=00106 name=/opt/oradata/datafile/UA_DATA_reorg0.dbf
input datafile fno=00110 name=/opt/oradata/datafile/IA_DATA.dbf
input datafile fno=00111 name=/opt/oradata/datafile/Ia_ind.dbf
input datafile fno=00112 name=/opt/oradata/datafile/CS_ind_reorg3.dbf
input datafile fno=00113 name=/opt/oradata/datafile/TP_ind.dbf
input datafile fno=00114 name=/opt/oradata/datafile/PU_ind_reorg0.dbf
input datafile fno=00116 name=/opt/oradata/datafile/PC_ind_reorg0.dbf
input datafile fno=00117 name=/opt/oradata/datafile/CM_DATA_reorg5.dbf
input datafile fno=00119 name=/opt/oradata/datafile/CS_ind_reorg0.dbf
input datafile fno=00120 name=/opt/oradata/datafile/IQ_DATA.dbf
input datafile fno=00121 name=/opt/oradata/datafile/GU_ind_reorg0.dbf
input datafile fno=00123 name=/opt/oradata/datafile/CS_ind_reorg5.dbf
input datafile fno=00124 name=/opt/oradata/datafile/CS_ind_reorg6.dbf
input datafile fno=00125 name=/opt/oradata/datafile/TC_DATA_reorg1.dbf
input datafile fno=00128 name=/opt/oradata/datafile/AC_ind_reorg0.dbf
input datafile fno=00129 name=/opt/oradata/datafile/IQ_IND.dbf
input datafile fno=00011 name=/opt/oradata/datafile/AC_DATA_reorg2.dbf
input datafile fno=00086 name=/opt/oradata/datafile/inventory01.dbf
channel oem_backup_disk1: starting piece 1 at 23-DEC-08
channel oem_backup_disk2: starting full datafile backupset
channel oem_backup_disk2: specifying datafile(s) in backupset
input datafile fno=00003 name=/opt/oradata/datafile/sysaux01.dbf
input datafile fno=00032 name=/opt/oradata/datafile/PC_DATA_reorg0.dbf
input datafile fno=00077 name=/opt/oradata/datafile/BI_DATA_reorg3.dbf
input datafile fno=00115 name=/opt/oradata/datafile/CS_ind_reorg4.dbf
input datafile fno=00049 name=/opt/oradata/datafile/IS_ind_reorg1.dbf
input datafile fno=00057 name=/opt/oradata/datafile/OR_ind_reorg0.dbf
input datafile fno=00073 name=/opt/oradata/datafile/PR_DATA_reorg1.dbf
input datafile fno=00013 name=/opt/oradata/datafile/IS_DATA_reorg0.dbf
input datafile fno=00044 name=/opt/oradata/datafile/GU_DATA_reorg2.dbf
input datafile fno=00016 name=/opt/oradata/datafile/CS_ind_reorg1.dbf
input datafile fno=00036 name=/opt/oradata/datafile/BI_DATA_reorg2.dbf
input datafile fno=00078 name=/opt/oradata/datafile/GU_ind_reorg3.dbf
input datafile fno=00102 name=/opt/oradata/datafile/DE_ind.dbf
input datafile fno=00109 name=/opt/oradata/datafile/kp_datap31.dbf
input datafile fno=00002 name=/opt/oradata/datafile/SH_DATA.dbf
input datafile fno=00004 name=/opt/oradata/datafile/users01.dbf
input datafile fno=00014 name=/opt/oradata/datafile/SZ_DATA.dbf
input datafile fno=00019 name=/opt/oradata/datafile/KL_ind_reorg0.dbf
input datafile fno=00025 name=/opt/oradata/datafile/pr_ind_reorg1.dbf
input datafile fno=00028 name=/opt/oradata/datafile/PK_ind_reorg0.dbf
input datafile fno=00031 name=/opt/oradata/datafile/OU_DATA.dbf
input datafile fno=00037 name=/opt/oradata/datafile/LJ_DATA.dbf
input datafile fno=00041 name=/opt/oradata/datafile/SW_DATA_reorg0.dbf
input datafile fno=00046 name=/opt/oradata/datafile/EB_DATA.dbf
input datafile fno=00052 name=/opt/oradata/datafile/PL_DATA_reorg0.dbf
input datafile fno=00056 name=/opt/oradata/datafile/CG_ind_reorg0.dbf
input datafile fno=00060 name=/opt/oradata/datafile/GU_ind_reorg1.dbf
input datafile fno=00063 name=/opt/oradata/datafile/UA_ind.dbf
input datafile fno=00066 name=/opt/oradata/datafile/SZ_ind.dbf
input datafile fno=00072 name=/opt/oradata/datafile/PK_DATA_reorg0.dbf
input datafile fno=00079 name=/opt/oradata/datafile/OU_ind.dbf
input datafile fno=00084 name=/opt/oradata/datafile/LJ_ind.dbf
input datafile fno=00085 name=/opt/oradata/datafile/TP_data0.dbf
channel oem_backup_disk2: starting piece 1 at 23-DEC-08
channel oem_backup_disk3: starting full datafile backupset
channel oem_backup_disk3: specifying datafile(s) in backupset
input datafile fno=00001 name=/opt/oradata/datafile/system01.dbf
input datafile fno=00068 name=/opt/oradata/datafile/SR_ind.dbf
input datafile fno=00012 name=/opt/oradata/datafile/KP_ind_reorg4.dbf
input datafile fno=00022 name=/opt/oradata/datafile/pr_ind_reorg4.dbf
input datafile fno=00047 name=/opt/oradata/datafile/GA_ind_reorg1.dbf
input datafile fno=00082 name=/opt/oradata/datafile/PR_DATA_reorg2.dbf
input datafile fno=00005 name=/opt/oradata/datafile/admin01.dbf
input datafile fno=00053 name=/opt/oradata/datafile/OR_DATA_reorg2.dbf
input datafile fno=00067 name=/opt/oradata/datafile/SW_ind.dbf
input datafile fno=00126 name=/opt/oradata/datafile/ST_DATA.dbf
input datafile fno=00038 name=/opt/oradata/datafile/SP_DATA_reorg0.dbf
input datafile fno=00010 name=/opt/oradata/datafile/st_ind_reorg0.dbf
input datafile fno=00034 name=/opt/oradata/datafile/ND_ind_reorg0.dbf
input datafile fno=00069 name=/opt/oradata/datafile/SP_ind.dbf
input datafile fno=00099 name=/opt/oradata/datafile/kp_datap10_reorg2.dbf
input datafile fno=00107 name=/opt/oradata/datafile/kp_datap21_reorg1.dbf
input datafile fno=00130 name=/opt/oradata/datafile/SA_ind_reorg2.dbf
input datafile fno=00007 name=/opt/oradata/datafile/AC_DATA_reorg1.dbf
input datafile fno=00017 name=/opt/oradata/datafile/PU_DATA_reorg1.dbf
input datafile fno=00023 name=/opt/oradata/datafile/KP_ind_reorg1.dbf
input datafile fno=00027 name=/opt/oradata/datafile/GU_DATA_reorg0.dbf
input datafile fno=00030 name=/opt/oradata/datafile/PC_ind_reorg1.dbf
input datafile fno=00035 name=/opt/oradata/datafile/kp_datap30_reorg2.dbf
input datafile fno=00040 name=/opt/oradata/datafile/KJ_DATA.dbf
input datafile fno=00045 name=/opt/oradata/datafile/FO_DATA.dbf
input datafile fno=00051 name=/opt/oradata/datafile/CT_DATA.dbf
input datafile fno=00055 name=/opt/oradata/datafile/SU_DATA_reorg0.dbf
input datafile fno=00059 name=/opt/oradata/datafile/KA_DATA
input datafile fno=00062 name=/opt/oradata/datafile/NT_DATA.dbf
input datafile fno=00065 name=/opt/oradata/datafile/TC_ind.dbf
input datafile fno=00071 name=/opt/oradata/datafile/RG_ind.dbf
input datafile fno=00075 name=/opt/oradata/datafile/PL_ind.dbf
input datafile fno=00083 name=/opt/oradata/datafile/MC_ind.dbf
channel oem_backup_disk3: starting piece 1 at 23-DEC-08
channel oem_backup_disk4: starting full datafile backupset
channel oem_backup_disk4: specifying datafile(s) in backupset
input datafile fno=00118 name=/opt/oradata/datafile/PC_DATA_reorg1.dbf
input datafile fno=00008 name=/opt/oradata/datafile/USER_DATA.dbf
input datafile fno=00080 name=/opt/oradata/datafile/CS_DATA_reorg4.dbf
input datafile fno=00122 name=/opt/oradata/datafile/SR_DATA_reorg0.dbf
input datafile fno=00048 name=/opt/oradata/datafile/GA_DATA_reorg2.dbf
input datafile fno=00108 name=/opt/oradata/datafile/KP_DATA_reorg2.dbf
input datafile fno=00018 name=/opt/oradata/datafile/PC_ind_reorg2.dbf
input datafile fno=00098 name=/opt/oradata/datafile/BI_ind.dbf
input datafile fno=00104 name=/opt/oradata/datafile/kp_datap11_reorg0.dbf
input datafile fno=00020 name=/opt/oradata/datafile/perftbs.dbf
input datafile fno=00076 name=/opt/oradata/datafile/ND_DATA_reorg0.dbf
input datafile fno=00009 name=/opt/oradata/datafile/UA_DATA.dbf
input datafile fno=00024 name=/opt/oradata/datafile/KB_DATA_reorg0.dbf
input datafile fno=00042 name=/opt/oradata/datafile/SA_DATA_reorg0.dbf
input datafile fno=00091 name=/opt/oradata/datafile/CG_DATA_reorg0.dbf
input datafile fno=00105 name=/opt/oradata/datafile/kp_datap20_reorg0.dbf
input datafile fno=00127 name=/opt/oradata/datafile/SA_ind_reorg1.dbf
input datafile fno=00006 name=/opt/oradata/datafile/sh_ind.dbf
input datafile fno=00015 name=/opt/oradata/datafile/TS_DATA_reorg0.dbf
input datafile fno=00021 name=/opt/oradata/datafile/RG_DATA.dbf
input datafile fno=00026 name=/opt/oradata/datafile/PM_DATA.dbf
input datafile fno=00029 name=/opt/oradata/datafile/PG_ind_reorg0.dbf
input datafile fno=00033 name=/opt/oradata/datafile/CM_DATA_reorg3.dbf
input datafile fno=00039 name=/opt/oradata/datafile/KL_DATA.dbf
input datafile fno=00043 name=/opt/oradata/datafile/CS_ind_reorg2.dbf
input datafile fno=00050 name=/opt/oradata/datafile/KP_ind_reorg2.dbf
input datafile fno=00054 name=/opt/oradata/datafile/MC_DATA_reorg1.dbf
input datafile fno=00058 name=/opt/oradata/datafile/OG_DATA_reorg0.dbf
input datafile fno=00061 name=/opt/oradata/datafile/DE_DATA.dbf
input datafile fno=00064 name=/opt/oradata/datafile/TS_ind.dbf
input datafile fno=00070 name=/opt/oradata/datafile/PG_DATA_reorg0.dbf
input datafile fno=00074 name=/opt/oradata/datafile/PM_ind.dbf
input datafile fno=00081 name=/opt/oradata/datafile/OG_ind.dbf
channel oem_backup_disk4: starting piece 1 at 23-DEC-08
channel oem_backup_disk2: finished piece 1 at 23-DEC-08
piece handle=/media/OneTouch_4/backup_dev/pak30k6c_1_1 tag=BACKUP_DATABASE_FU_122308090352 comment=NONE
channel oem_backup_disk2: backup set complete, elapsed time: 00:04:56
channel oem_backup_disk3: finished piece 1 at 23-DEC-08
piece handle=/media/OneTouch_4/backup_dev/pbk30k6c_1_1 tag=BACKUP_DATABASE_FU_122308090352 comment=NONE
channel oem_backup_disk3: backup set complete, elapsed time: 00:05:31
channel oem_backup_disk4: finished piece 1 at 23-DEC-08
channel oem_backup_disk4: backup set complete, elapsed time: 00:07:37
piece handle=/media/OneTouch_4/backup_dev/pck30k6c_1_1 tag=BACKUP_DATABASE_FU_122308090352 comment=NONE
RMAN-03009: failure of backup command on oem_backup_disk1 channel at 12/23/2008 21:14:34
channel oem_backup_disk1 disabled, job failed on it will be run on another channel
Additional information: 286720
Additional information: 1969153
Additional information: 4
Linux-x86_64 Error: 2: No such file or directory
ORA-27072: File I/O error
ORA-19502: write error on file "/media/OneTouch_4/backup_dev/p9k30k6c_1_1", blockno 1969153 (blocksize=8192)
input datafile fno=00094 name=/opt/oradata/datafile/CT_ind.dbf
input datafile fno=00095 name=/opt/oradata/datafile/CM_DATA_reorg4.dbf
input datafile fno=00096 name=/opt/oradata/datafile/CM_ind.dbf
input datafile fno=00097 name=/opt/oradata/datafile/BI_ind_reorg0.dbf
channel oem_backup_disk2: starting piece 1 at 23-DEC-08
input datafile fno=00101 name=/opt/oradata/datafile/SU_ind.dbf
input datafile fno=00103 name=/opt/oradata/datafile/NT_ind.dbf
input datafile fno=00106 name=/opt/oradata/datafile/UA_DATA_reorg0.dbf
input datafile fno=00110 name=/opt/oradata/datafile/IA_DATA.dbf
input datafile fno=00111 name=/opt/oradata/datafile/Ia_ind.dbf
input datafile fno=00112 name=/opt/oradata/datafile/CS_ind_reorg3.dbf
input datafile fno=00113 name=/opt/oradata/datafile/TP_ind.dbf
input datafile fno=00114 name=/opt/oradata/datafile/PU_ind_reorg0.dbf
input datafile fno=00116 name=/opt/oradata/datafile/PC_ind_reorg0.dbf
input datafile fno=00117 name=/opt/oradata/datafile/CM_DATA_reorg5.dbf
input datafile fno=00119 name=/opt/oradata/datafile/CS_ind_reorg0.dbf
input datafile fno=00120 name=/opt/oradata/datafile/IQ_DATA.dbf
input datafile fno=00121 name=/opt/oradata/datafile/GU_ind_reorg0.dbf
input datafile fno=00123 name=/opt/oradata/datafile/CS_ind_reorg5.dbf
input datafile fno=00124 name=/opt/oradata/datafile/CS_ind_reorg6.dbf
input datafile fno=00125 name=/opt/oradata/datafile/TC_DATA_reorg1.dbf
input datafile fno=00128 name=/opt/oradata/datafile/AC_ind_reorg0.dbf
input datafile fno=00129 name=/opt/oradata/datafile/IQ_IND.dbf
input datafile fno=00011 name=/opt/oradata/datafile/AC_DATA_reorg2.dbf
input datafile fno=00086 name=/opt/oradata/datafile/inventory01.dbf
input datafile fno=00093 name=/opt/oradata/datafile/EB_ind.dbf
input datafile fno=00092 name=/opt/oradata/datafile/FO_ind.dbf
input datafile fno=00089 name=/opt/oradata/datafile/GU_DATA_reorg1.dbf
input datafile fno=00088 name=/opt/oradata/datafile/KB_ind.dbf
input datafile fno=00087 name=/opt/oradata/datafile/KJ_ind.dbf
input datafile fno=00131 name=/opt/oradata/datafile/undotbs01.dbf
channel oem_backup_disk2: specifying datafile(s) in backupset
channel oem_backup_disk2: starting full datafile backupset
input datafile fno=00100 name=/opt/oradata/datafile/KA_ind.dbf
input datafile fno=00131 name=/opt/oradata/datafile/undotbs01.dbf
input datafile fno=00087 name=/opt/oradata/datafile/KJ_ind.dbf
channel oem_backup_disk3: starting full datafile backupset
channel oem_backup_disk2 disabled, job failed on it will be run on another channel
Additional information: 319488
Additional information: 1969153
Additional information: 4
Linux-x86_64 Error: 2: No such file or directory
ORA-27072: File I/O error
ORA-19502: write error on file "/media/OneTouch_4/backup_dev/pdk30kpr_1_1", blockno 1969153 (blocksize=8192)
RMAN-03009: failure of backup command on oem_backup_disk2 channel at 12/23/2008 21:21:13
input datafile fno=00092 name=/opt/oradata/datafile/FO_ind.dbf
input datafile fno=00089 name=/opt/oradata/datafile/GU_DATA_reorg1.dbf
input datafile fno=00088 name=/opt/oradata/datafile/KB_ind.dbf
channel oem_backup_disk3: specifying datafile(s) in backupset
input datafile fno=00117 name=/opt/oradata/datafile/CM_DATA_reorg5.dbf
input datafile fno=00119 name=/opt/oradata/datafile/CS_ind_reorg0.dbf
input datafile fno=00120 name=/opt/oradata/datafile/IQ_DATA.dbf
input datafile fno=00121 name=/opt/oradata/datafile/GU_ind_reorg0.dbf
input datafile fno=00123 name=/opt/oradata/datafile/CS_ind_reorg5.dbf
input datafile fno=00124 name=/opt/oradata/datafile/CS_ind_reorg6.dbf
input datafile fno=00125 name=/opt/oradata/datafile/TC_DATA_reorg1.dbf
input datafile fno=00128 name=/opt/oradata/datafile/AC_ind_reorg0.dbf
input datafile fno=00129 name=/opt/oradata/datafile/IQ_IND.dbf
input datafile fno=00011 name=/opt/oradata/datafile/AC_DATA_reorg2.dbf
input datafile fno=00086 name=/opt/oradata/datafile/inventory01.dbf
input datafile fno=00116 name=/opt/oradata/datafile/PC_ind_reorg0.dbf
input datafile fno=00114 name=/opt/oradata/datafile/PU_ind_reorg0.dbf
input datafile fno=00113 name=/opt/oradata/datafile/TP_ind.dbf
input datafile fno=00112 name=/opt/oradata/datafile/CS_ind_reorg3.dbf
input datafile fno=00111 name=/opt/oradata/datafile/Ia_ind.dbf
input datafile fno=00110 name=/opt/oradata/datafile/IA_DATA.dbf
input datafile fno=00106 name=/opt/oradata/datafile/UA_DATA_reorg0.dbf
input datafile fno=00103 name=/opt/oradata/datafile/NT_ind.dbf
input datafile fno=00101 name=/opt/oradata/datafile/SU_ind.dbf
channel oem_backup_disk3: starting piece 1 at 23-DEC-08
input datafile fno=00097 name=/opt/oradata/datafile/BI_ind_reorg0.dbf
input datafile fno=00096 name=/opt/oradata/datafile/CM_ind.dbf
input datafile fno=00095 name=/opt/oradata/datafile/CM_DATA_reorg4.dbf
input datafile fno=00094 name=/opt/oradata/datafile/CT_ind.dbf
input datafile fno=00093 name=/opt/oradata/datafile/EB_ind.dbf
input datafile fno=00100 name=/opt/oradata/datafile/KA_ind.dbf
channel oem_backup_disk4: starting full datafile backupset
channel oem_backup_disk4: specifying datafile(s) in backupset
Additional information: 475136
Additional information: 1969153
Additional information: 4
Linux-x86_64 Error: 2: No such file or directory
ORA-27072: File I/O error
ORA-19502: write error on file "/media/OneTouch_4/backup_dev/pek30l69_1_1", blockno 1969153 (blocksize=8192)
RMAN-03009: failure of backup command on oem_backup_disk3 channel at 12/23/2008 21:27:34
input datafile fno=00093 name=/opt/oradata/datafile/EB_ind.dbf
input datafile fno=00092 name=/opt/oradata/datafile/FO_ind.dbf
input datafile fno=00089 name=/opt/oradata/datafile/GU_DATA_reorg1.dbf
input datafile fno=00088 name=/opt/oradata/datafile/KB_ind.dbf
input datafile fno=00087 name=/opt/oradata/datafile/KJ_ind.dbf
input datafile fno=00131 name=/opt/oradata/datafile/undotbs01.dbf
channel oem_backup_disk3 disabled, job failed on it will be run on another channel
input datafile fno=00120 name=/opt/oradata/datafile/IQ_DATA.dbf
input datafile fno=00121 name=/opt/oradata/datafile/GU_ind_reorg0.dbf
input datafile fno=00123 name=/opt/oradata/datafile/CS_ind_reorg5.dbf
input datafile fno=00124 name=/opt/oradata/datafile/CS_ind_reorg6.dbf
input datafile fno=00125 name=/opt/oradata/datafile/TC_DATA_reorg1.dbf
input datafile fno=00128 name=/opt/oradata/datafile/AC_ind_reorg0.dbf
input datafile fno=00129 name=/opt/oradata/datafile/IQ_IND.dbf
input datafile fno=00011 name=/opt/oradata/datafile/AC_DATA_reorg2.dbf
input datafile fno=00086 name=/opt/oradata/datafile/inventory01.dbf
input datafile fno=00119 name=/opt/oradata/datafile/CS_ind_reorg0.dbf
input datafile fno=00117 name=/opt/oradata/datafile/CM_DATA_reorg5.dbf
input datafile fno=00116 name=/opt/oradata/datafile/PC_ind_reorg0.dbf
input datafile fno=00114 name=/opt/oradata/datafile/PU_ind_reorg0.dbf
input datafile fno=00113 name=/opt/oradata/datafile/TP_ind.dbf
input datafile fno=00112 name=/opt/oradata/datafile/CS_ind_reorg3.dbf
input datafile fno=00111 name=/opt/oradata/datafile/Ia_ind.dbf
input datafile fno=00110 name=/opt/oradata/datafile/IA_DATA.dbf
input datafile fno=00106 name=/opt/oradata/datafile/UA_DATA_reorg0.dbf
input datafile fno=00103 name=/opt/oradata/datafile/NT_ind.dbf
input datafile fno=00101 name=/opt/oradata/datafile/SU_ind.dbf
channel oem_backup_disk4: starting piece 1 at 23-DEC-08
input datafile fno=00097 name=/opt/oradata/datafile/BI_ind_reorg0.dbf
input datafile fno=00096 name=/opt/oradata/datafile/CM_ind.dbf
input datafile fno=00095 name=/opt/oradata/datafile/CM_DATA_reorg4.dbf
input datafile fno=00094 name=/opt/oradata/datafile/CT_ind.dbf
input datafile fno=00100 name=/opt/oradata/datafile/KA_ind.dbf
released channel: oem_backup_disk1
released channel: oem_backup_disk3
released channel: oem_backup_disk4
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on oem_backup_disk4 channel at 12/23/2008 21:34:10
ORA-19502: write error on file "/media/OneTouch_4/backup_dev/pfk30li6_1_1", blockno 1969153 (blocksize=8192)
ORA-27072: File I/O error
Linux-x86_64 Error: 2: No such file or directory
Additional information: 4
Additional information: 1969153
Additional information: 176128
exit;
released channel: oem_backup_disk2

[SOLVED] (hopefully) USB Hard drive disconnects

Similar Messages

Maybe you are looking for