Problems with USB external drive attached to time capsule

Hi,
I bought a WD 1 TB my book as a supplemental backup drive, as I've pretty much maxed out the space in my 500 GB TC with backups form two macbooks. It's attached to the TC via the USB 2.0. For the first few months everything worked fine. Now suddenly neither machine can access the WD drive. It shows up in the Aiport utility but not in the finder. When I plug it directly into one of the macbooks it accesses fine, but I bought it specifically to use as additional network backup drive.
Where have I gone wrong? I updated the firmware for the WD drive, and everything appears fine on the TC and the macbooks. I poked around on the forums and found many a complaint about the WD drives, but I couldn't find a solution to my particular problem.
Any ideas?
Thanks.

The first thing to try is a nice long power cycle of the network if you have not already done this.
Power everything down, order is not important. Wait 5-10 minutes.
Start the modem first and let it run 4-5 minutes by itself. Then start the next device connected to the modem the same way. Keep powering up each device the same way until all devices are powered on.
Any help?
If no luck, the next thing to try is connect the WD drive directly to your computer and "Verify Disk" using Disk Utility.
Applications > Utilities > Disk Utility
Then click "Repair disk"
If indicated, "Repair Permissions" on the disk.
Eject the disk and then you'll have to do the power cycle all over again and plug the device back into the USB port on the Time Capsule.

Similar Messages

External Drive attached to Time Capsule failing to work consistently

This problem has been occurring since we started using an external drive attached to our Time Capsule as a backup destination for Time Machine over a year ago:
Everything will be fine for a few days or weeks, but at some point backups stop working. This sometimes gives errors (Time Machine could not complete backup, I think) or sometimes it just looks like the backup has gotten stuck (reporting 235.32 MB of 22.86 GB for days). With the latter problem it seems to cause other issues with the OS like System Preferences not responding anymore and certain Save As... dialog boxes not appearing.
Every time this happens, what I do is disconnect all users through AirPort Utility and then plug the drive into one of the computers and run Disk Utility on it.
Each time, without fail, there is the error "Incorrect number of Access Control Lists" stating it should be 0 and it really is something in the thousands usually.
The volume is always repaired successfully, but then the cycle continues.
We've tried a couple of different drives and it always ends up happening.
I've seen other posts with similar problems, but nothing laid out exactly like my problem, and no real fix for it.

Yes, indeed. Let me give some background.
I have an old Gigabit AEBS (7.4.2) as my main router with a Gigabit connection to my Time Capsule (500GB, 7.4.2) running in bridge mode. Both run as wireless access points for my network "Hogwarts." I backup several machines to the TC's internal drive with absolutely no problems whatsoever. Practically bulletproof. I backup two media heavy machines to the external drive attached to the TC. The drive is a Western Digital My Book 1.5TB that before the TC came into our lives, ran flawlessly when attached to my iMac as a backup destination. The media machines are Dumbledore, my mini running as a HTPC, and Tonks, my wife's laptop busting with pics and video of our son. Once I started backups to this drive connected to the TCs, I started to have problems with backup. That's the situation. Here's what I've tried to correct it.
I had a year's worth of backups. Went to the Genius Bar who recommended starting over after they checked out my setup over Back to My Mac. They couldn't find anything wrong and supposed my backups were hopelessly corrupted. So I followed their advice with Dumbledore and archived those for Tonks. Trying to start over with Dumbledore fails within the first 75 of 500 GB to backup every time. I've redirected syslog reporting at Debug level from the TC to my iMac and formatted the external drive several times. I have done disk repairs on the drive, Dumbledore's sparse bundle, and the TM volume contained in the sparse bundle. I've only gotten the "too many ACL's" error. The WD drive comes with SmartWare software I've used to check the S.M.A.R.T. status (100% OK), test the drive (100% OK) and deactivate the Virtual CD partition used to, among other things, encrypt the drive. My drive is unencrypted and have made it as plain vanilla as I can: GUID with one 1.5 TB Mac OS Extended Journaled partition.
What I've noticed when I check the status of the TC when the bakcups fail is that the drive becomes unmounted with no logged error. The client computer either hangs Finder or reports the backup failed. My wife has become so frustrated with hard restarts that she has turned off Time Machine until I fix this. Airport Utility simply no longer sees the drive. The client computer can reconnect over AFP but the drive will not be accessible unless I restart the TC. Then if I do some Disk Utility repairs on the external drive and on the virtual volumes it contains, I can start backups again...until the next spontaneous unmounting of the drive. Which leaves me talking to you as a completely frustrated and disappointed Apple user. This is so not Apple quality experience.
The only shot in the dark I've seen is that the TC repeatedly updates its DHCP lease every 5 minutes or so despite having a 4 hour TTL. Weird.

How to back up external drive attached to time capsule

How can I backup an external 1 TB drive containing my itunes library that I have attached to my time capsule usb port to my time capsule?
Over the weekend I purchased a timecapsule and I love it! I thought the idea of not having to mount and unmount my usb external drive from my laptop would help with my itunes library intergrity (keep loosing large chunks of music). I have now plugged the drive into the timecapsule usb port but the only configuration time machine allows that I can find is to tell it what not to back up on my laptop and now that the external drive is not attached to my mac it doesn't even appear. what now? I want to get this completed prior to upgrading to snow leopard.

go system preferences > time machine > options and make sure the external is not excluded from backups.
that's it. time machine should automatically backup any drive connected directly to your computer (unless it is told not to and given there's sufficient space on the TC).
JGG

Best practices with external drives connected to Time Capsule?

I'm enjoying my new MBP but the storage limitations are a challenge with twenty+ years of data. I know it's not technically sanctioned by Apple but in another forum I found a discussion about successfully connecting an external drive to the Time Capsule. I tried this for a few months and had some problems, so I wonder if anyone here might have some insight into which of my drives would be best to use in this way and what, if anything, I must do to bless it for the task.
The drive most highly recommended in the forums at the time is the WD My Book. After buying it I learned that is Windows users install a package and update the driver for use with Time Machine, which Mac users are not able to do. The driver is available on the web but it's said to cause problems with Mountain Lion, which I can confirm. It's USB 3.0 and powered, though, which my two alternatives are not. It's also 2 TB and presently in two partitions. I also have a Seagate Free Agent GoFlex 500 which gets extremely hot with any use and an Iomega eGo Helium 500 I've been using for backups. Both are USB 2.0.
My goal is to put my iTunes Library and Time Capsule on the net (running 2.4 Ghz and 5 Ghz, averages 50Mbs). When I did this for a few months with the WD both its shares frequently dropped off my Desktop, as if powered down or something. Also there were the issues with Time Machine many others are having. Right now our video collection sits on the Time Capsule. Would it make sense to move our video to the WD and run iTunes and Time Machine on it? If so, do you have any tips for formatting, petitioning, or drivers (or anything else) to help this run smoothly? The WD works fine when hard-wired and the TC, too is fine without the WD at the party.
With apologies for the tome.

kevlee64 wrote:
Thanks, but the drive is connected directly to the back of the Time Capsule by an ethernet cable.
Ah, that's a different colored horse.
You have a NAS (Network Attached Storage) drive, not a USB external drive connected to the USB port.
Many of those need software/firmware updates to work with Lion. Check with Iomega.

I want to add more capacity on hard drive of time capsule. Can i add a normal usb driver? I will see it as an external drive in the time capsule network? It will work as fast than time capsule? Thanks

I want to add more capacity on hard drive of time capsule. Can i add a normal usb driver? I will see it as an external drive in the time capsule network? It will work as fast than time capsule? Thanks

Can i add a normal usb driver?
Yes, but be sure that the drive is formatted correctly for Mac in Mac OS Extended (Journaled)
I will see it as an external drive in the time capsule network?
The drive will appear as a shared network drive, like the Time Capsule.
It will work as fast than time capsule?
No, the drive will operate at about half or 50% of the speed of the Time Capsule.

I have a time machine backup file on a USB hard drive. I bought a time capsule / airport extreme, flat 3TB. I wish to transfer the backup file from the usb hard drive to the time capsule hard drive. 10.6.8

I have a time machine backup file on a USB hard drive. I bought a time capsule / airport extreme, flat 3TB. I wish to transfer the backup file from the usb hard drive to the time capsule hard drive. 10.6.8

Unfortunately, Time Machine backups that are stored on a drive that has been connected directly to a Mac are completely different than Time Machine backups that are stored on a Time Capsule.
Frankly, it is not worth the effort and trouble to try to transfer the old backups to the new Time Capsule.....my opinion....having done this in the past.
It is possible though, but I would not recommend it due to the complexity and downsides involved with this. To give you an idea of how to do this, check out this support article.
http://pondini.org/TM/18.html
Even if you transfer the "old" backups over to the Time Capsule successfully, Time Machine will not simply "add on" to the old backups.
Time Machine will make a new complete backup of your Mac and then add incremental backups from that point.
My advice.....start a new backup on the Time Capsule and move forward. Keep the USB hard drive around for a month, maybe 2 or 3 in case you need to go back to an old backup for some reason. At that time, you will not likely need the old backups at all since you will have a current 2-3 month history of new backups. At that point, you can erase the USB drive and use it for another purpose.

Is there way to store my movies on my Time Capsule instead of laptop drive? I will then run an external drive to backup Time Capsule.

Is there way to store and run my iMovies on my Time Capsule instead of laptop drive? I will then run an external drive to backup Time Capsule as my backup. I want to dothis because my hard drive is full and I still have many movies to import form camcorder.

I do not know about iMovie, but the experts in the iPhoto and Aperture support areas strongly advise against trying to install your "working" image library on the Time Capsule.
You might want to ask about this in the iMovie support area.
iMovie for Mac
It would be much easier and much better if you use the external drive to connect to your Mac via USB or FireWire and then store the movies there.
Then, Time Machine will back up both your Mac and the external hard drive automatically once you tell it to do so.

New External Drive connected to Time Capsule moving files problem

I have a late 2009 13" unibody MacBook Pro, that I primarily use for video editing/converting. I use my Time Capsule as a network through which I can connect to my external hard drives via USB for videos and such. I've used at least two other external hard drives along with my Time Capsule for a year and a half with very few problems, aside from the inevitable crash of one. Before yesterday, I had a 1TB Western Digital MyBook (http://www.wdc.com/en/products/products.aspx?id=210) and a 2TB Verbatim Desktop HD (http://www.verbatim.com/prod/hard-drives/desktop/usb-2.0/) connected through my 1TB Time Capsule and aside from the Verbatim drive being rather sluggish most of the time, everything was working fine.
Yesterday, I got a new external drive, an iOmega MiniMax 2TB (http://go.iomega.com/en-us/products/external-hard-drive-desktop/ultramax-minimax /minimax800/?partner=4760). I spent yesterday and most of today moving files around and whatnot through a wired connection (iOmega via firewire 800, Verbatim via USB, MyBook via USB, and Time Capsule via Ethernet), and everything moved quickly and without any problems.
I hooked my Time Capsule up to my modem, plugged in the iOmega and Verbatim drives via USB to the TC, and started my laptop. When I opened the drives, everything was working fine... And then I tried to move a file to the iOmega drive... I was moving an episode of The Killing. I dragged it into the folder and went to Safari to look something up and suddenly realized ten minutes later that I still hadn't heard the noise telling me that the file had finished. I looked at the move dialogue box and it said "156.8 MB of 323.8 MB - About 10 Seconds". I watched it for another ten minutes and it didn't move. So I clicked cancel move and the rainbow wheel of death came up and I had to force reboot my computer.
When I restarted, I opened up finder to access the drives through my Time Capsule, and it "failed to connect" to my Time Capsule. So I went back into my office to flip the switch on the surge protector in order to restart the process. I turned on my computer and I had no problem accessing my hard drives... Until I tried to move an episode of United States of Tara into the iOmega hard drive. This time, it said, "192.5 MB of 202.6 MB - About 5 Seconds" and completely stopped moving again. And the same thing happened when I clicked the little grey "x" to cancel the move.
I repeated the process several more times with no luck. Then I thought it might help to see if it does the same thing with documents. So I dragged just a random document to the iOmega and it took about 30 seconds, but it did it successfully. So I tried to move the episode of The Killing again and I let it go for, like, 25-30 minutes. After this time, I got a notification from finder saying, "Finder cannot complete the operation because some data in "[the file]" can't be read or written. (Error Code -36)". Then when I went back into the "Shared" part of the sidebar to go back into my Time Capsule folder, it said "Connection Failed"
So what exactly does this mean? Are the Time Capsule and iOmega not compatible? Can I only move the files through a wired connection [which would be unfortunate]? Do I need to rejigger the USB configuration? Is the error code just for these two episodes and it's just a random coincidence that it happened the day after I got a new drive?
Thanks for any help anyone can give me!
- Alex

I have attached the macbook to the tc via ethernet cable. Should I turn off my wireless connection or will itunes recognize to go with the faster connection on it's own?
You MBP will try to connect based on the order of the list of network devices on the System Preferences > Network window. If Ethernet is not at the top of the list, then go ahead and temporarily disable AirPort.
After all this is done will the wireless connection be fast enough for normal itunes operation?
For audio streaming it should be, but just be aware that your iTunes host will have to get the audio source wirelessly from the TC, which in turn will have to get the data from the USB hard drive. Finally, the iTunes host will have to wirelessly stream the iTunes audio via AirTunes to the AirPort Express.

Problem mapping USB external drive connected to Airport Extreme on my PC

I am having a problem mapping my USB external drive in my PC running WIndows Vista. Here is what I have so far:
USB External Drive connected to my AirPort Extreme which is connected to my Century Link modem/router.
I have installed the USB drive using the Airport Utility. In the Disks section the Enable File Sharing is checked, Secure Shared Disks is set to With a Disk Password, I have entered the password in the next 2 rows, and finally AirPort Disks Gues Access is set to Not Allowed. The section below named These Settings Configure Windows File Sharing is empty. Am I supposed to put something here?
I was also told I need to map the drive in my PC, but when I go to do that via the Computer and the Map Network Drive, I get stuck where it asks me to enter a folder name. I read many of the posts which tell me I need to enter among other things the disk's ip address, but I am unable to find it anywhere. Where do I find what to put here?
Can someone please help this frustrated user?

I had my USB drive on my APE working with Time Machine under 10.5.1 very reliably. A few days ago however, I needed to suspend a backup operation, and when I came back to restart it, time machine refused to mount the disk image on the drive. After several attempts to get it to connect with no luck I decided to delete the image (the sparce image file) and start over. Now TM refuses to create a new image.
BTW, on the Mac OSX hints site there have been suggestions to start a backup with the drive directly connected, then stop the backup, move the sparce image file to the root of the drive, reconnect the drive to the APE base station to get it working. I tried this again, but I think Apple has changed something in 10.5.2, because when directly connected TM no longer creates a sparce image file.
Anybody else seen this behavior after upgrading to 10.5.2?

Searching external hard drive attached to Time Capsule

I have a 1 TB Time Capsule which I use for backing up my 2011 MacBook Pro and for providing my WiFi. I also have a 1 TB external hard drive plugged into my Time Capsule which I can access via WiFi. I can go to Finder on my laptop and browse the folders/files on my external hard drive. It appears under Shared in the sidebar of the Finder window. I can open files from it and I can save files to the drive, so it appears to be working fine. I have hundreds of gigs of files on the drive. But when I was recently hunting for a specific file, I noticed that my Spotlight wasn't doing a very good job at finding files on my external hard drive. I tried many different searches - by name, by type, by date - and had no luck. But as I was searching, I realized that I had more files of certain file types than Spotlight was showing me. So I tried searching for files I first confirmed were actually on the external drive. And again Spotlight failed to find them. If I used a partial filename search, it would find some files that matched but not the ones I was looking for.
So, this led me to think the index is corrupt. I'm not sure if this problem is related to my recently upgrading to Lion or not, since I haven't had to search the drive in awhile. I tried to force Spotlight to recreate the index on the drive by using the Privacy panel trick (of the Spotlight Preferences) but that didn't work. I then tried to get Spotlight to recreate its entire index and I think all that did was recreate the index for my internal harddrive.
So, are there things I need to know about attaching an external hard drive to a Time Capsule that I perhaps forgot to do? Should I be able to search the drive with Spotlight? Do I have to somehow force Spotlight to look in external drive when doing a search or is it supposed to search everything it can?
I should mention I have been having a little trouble with my Time Capsule as well. I recently had to erase the drive and set up a whole new backup since the backup was failing - not sure what happened to it, but it seems to be working again now. But I did notice yesterday that my Time Machine hadn't backed up all day but it was not giving me a warning message. It was just sitting there not backing up. I had tried resetting my PRAM and after doing so, my Time Machine was back to backing up. I'm not sure if the PRAM reset helped with that or if it was just the restart of the laptiop.
One more thing - I feel like since upgrading to Lion I have had to restart my laptop more than ever. Things just start acting funny, especially when I am using Safari and I find myself resetting Safari and then restarting my laptop all the time. Odd.

It should be HFS+.. it may work with fat32 but that is a lousy format.
The actual format of the drive is irrelevant to the PC.. the TC offers SMB connection.. so it is a true file sharing device.. the format used to store the files cannot be directly read by windows but is "interpreted, translated" via the firmware of the TC.
BTW this is true of all network storage.. A NAS can store files in whatever format its OS requires.. freebsd like freenas might use XFS.. or linux use EXT2 or REISFS.. it makes no difference as long as it offers that store to the windows (and apple) network as SMB.. then windows can handle it.

Problem with 2 External Drives on my new iMac

I am having a problem when I daisy-chain a second external HD to my first external HD connected to my new iMac. This is the second external HD I've tried this with, with similar problems arising.
My setup: OS 10.5.6. First external HD: G-Tech Q 1TB; 2nd External HD: also a G-Tech Q 1TB (the first time I was daisy-chaining a LaCie 250GB drive to my first external drive).
Problem: when my second external HD is daisy-chained to the first external HD my system starts to go wonky. I can't force quit apps for one. My system hangs. On reboot I don't get past the blue screen. If I remove the daisy-chain all is fine.
I initially had this problem with another external HD I tried to daisy-chain to the first. Same issue.
I was trying to partition the second external using Disk Utility. When I hit the Partition button, Disk Utility just hung with the beach ball.
When I attached a second external the first time I tried to do this all sorts of havoc ensued. A lot of apps were hanging and I couldn't Force Quit them. The whole system seemed to go wonky.
Can anyone tell me what might be happening here?

I've been doing a bit of research on these boards about daisy-chaining problems and am reading that sometimes daisy-chaining can overwhelm the Firewire bus and even corrupt data. This is what I had experienced the first time I tried to daisy-chain. Someone recommended a powered Firewire repeater (like this: http://tinyurl.com/kl84n5) would be a better solution.
Given I've got only 1 Firewire port on my iMac, what do you think?

Access exFAT formatted USB hard drive partition through Time Capsule 2013

I am trying to move data, mostly music, from my old PC to a wirelessly accessible HDD that we can get to from our MacBooks running OS 10.6.8. I have a 2013 Time Capsule with a USB hard drive attached, but I can't see the exFAT partition containing all of the data (on my Mac). I can see the other two partitions, which are formatted for a Mac. I can also see the exFAT partition on my Mac when it is plugged in directly, I just can't access that partition through the Time Capsule. Any ideas on how to remedy this? Or if there is a better solution for moving this data. We don't care about accessing the data from the PC any longer. We are going to get rid of it. We just need a place to keep all of the data where we can get to it.
Message was edited by: A2Laurel

You need to connect the drive directly to a Mac, copy the data to another location, reformat that partition as Mac OS Extended (Journaled), and put the data back onto it.
(85877)

Is it possible to connect an external drive to the time capsule that I could use to store and access my primary iTunes files?

I would like to move my music files to an external drive that my iMac iTunes could access wirelessly and I'm wondering if it is possible to do so through connecting a drive to my Time Capsule.

This can be done....but if you move your iTunes Media folder to the drive that is connected to the Time Capsule, you might first want to think about how you will backup these important files.
Time Machine cannot backup the files back to the Time Capsule, so you will need to use a commercial backup application like Carbon Copy Cloner or SuperDuper to copy the files back to the Time Capsule drive.
As long as you plan to add a hard drive, you might want to consider an alternate plan:
Connect a hard drive directly to your Mac using USB or FireWire and move the iTunes Media Library there. Then, Time Machine will back up both your Mac and the hard drive, so you have original copies on one drive and backups on another.
Whatever you decide, be sure to follow the correct instructions to move the iTunes Media Folder. You cannot simply drag and drop.
http://support.apple.com/kb/HT1449

Problem with USB External Hard Disk Drive

I have similar problem with hard disk MK6025GAS in Sweex casing connected via USB as Raistlfiren in this post but I am not sure if it has something to do with kernel. The problem is that when I plug the hard disk via USB it is not even shown with in /dev/ or by fdisk -l. I had similar problems with the drive before but it was always shown in /dev.
I got same output from dmesg as Raistlfiren in the post before
# dmesg | tail
sd 4:0:0:0: [sdd] ASC=0x0 ASCQ=0x0
sd 4:0:0:0: [sdd] Sense Key : 0x0 [current]
Info fld=0x0
I was browsing net for a lot of time to find a solution but nothing helped a lot. The problem is closes to the one described on Gentoo Forum
I can see that it is recognized by computer since it is shown with lsusb
# lsusb
Bus 001 Device 005: ID 13fd:0540 Initio Corporation
# lsusb -d 13fd:0540 -v
Bus 001 Device 005: ID 13fd:0540 Initio Corporation
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x13fd Initio Corporation
idProduct 0x0540
bcdDevice 0.00
iManufacturer 1 Initio
iProduct 2 MK6025GAS
iSerial 3 0010100500000000
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 2mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk (Zip)
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0001
Self Powered
From the beginning I though and I still think that the partition table is screwed up but the programs like TestDisk and fixdisktable work only with disks shown in /dev/
Additionally, I have checked the content of /var/log/kernel.log
Sep 16 22:03:58 hramat kernel: usb 1-2: new high speed USB device using ehci_hcd and address 5
Sep 16 22:03:58 hramat kernel: usb 1-2: configuration #1 chosen from 1 choice
Sep 16 22:03:58 hramat kernel: scsi4 : SCSI emulation for USB Mass Storage devices
Sep 16 22:03:58 hramat kernel: usb-storage: device found at 5
Sep 16 22:03:58 hramat kernel: usb-storage: waiting for device to settle before scanning
Sep 16 22:04:03 hramat kernel: scsi 4:0:0:0: Direct-Access Initio MK6025GAS 2.23 PQ: 0 ANSI: 0
Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: Attached scsi generic sg4 type 0
Sep 16 22:04:03 hramat kernel: usb-storage: device scan complete
Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] 117210240 512-byte hardware sectors: (60.0 GB/55.8 GiB)
Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] Write Protect is off
Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] Mode Sense: 86 0b 00 02
Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] Assuming drive cache: write through
Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] Assuming drive cache: write through
Sep 16 22:04:03 hramat kernel: sdd:<6>sd 4:0:0:0: [sdd] Sense Key : 0x0 [current]
Sep 16 22:04:03 hramat kernel: Info fld=0x0
Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] ASC=0x0 ASCQ=0x0
Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] Sense Key : 0x0 [current]
and /var/log/errors.log
Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] Assuming drive cache: write through
Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] Assuming drive cache: write through
Sep 16 22:07:35 hramat kernel: INFO: task async/0:3957 blocked for more than 120 seconds.
Sep 16 22:07:35 hramat kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
The only thing I understand from these logs is that the disk is blocked, therefore not listed in /dev.
Assuming the newer kernel problems I could try to use some older live linux CD to see if that would work. I am also thinking of connecting this hard drive directly to my laptop, using live linux CD and maybe check the output of hdparm. Is there anything else I could check or try?
Thank you for any help or suggestions
Matej

Thank you nTia89 for response. Sorry for not providing enough information.
I believe the problem is not system dependent. I have dual boot with windows and there the disk has also problems. However, I do have Arch32 with Kernel 2.6.30, using Gnome. hal and dbus are also running.
I did not tried to connect the disk to the computer directly, I will try it today.
Yesterday I have used SystemRescueCD 0.4.1 with Kernel 2.6.22. I wanted to see if it will be recognized by the system and placed in /dev/. Yes it was. This means that the problem highlighted in Gentoo forum can be true, but it doesn't solve my problem. I have tried to connect the drive several times to Arch and it was not shown in /dev/sd*, in SystemRescueCD it was placed as /dev/sdb. Now I am sure that the partition table is screwed up.
So I have started to play with the drive in SystemRescueCD with TestDisk and FixDiskTable but without success.
% fdisk -l
Disk /dev/sda: 100.0 GB, 100030242816 bytes
255 heads, 63 sectors/track, 12161 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 1530 12289693+ 7 HPFS/NTFS
/dev/sda2 1531 6672 41303115 7 HPFS/NTFS
/dev/sda3 6673 12161 44090392+ f W95 Ext'd (LBA)
/dev/sda5 * 6673 11908 42058138+ 83 Linux
/dev/sda6 11909 12161 2032191 82 Linux swap / Solaris
Disk /dev/sdb: 60.0 GB, 60011642880 bytes
64 heads, 32 sectors/track, 57231 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Disk /dev/sdb doesn't contain a valid partition table
Manufacturer disk geometry: Heads: 16; Cylinders: 16383; Sectors: 63; Logical Blocks (LBA): 117210240
TestDisk found only Linux partitions with 43Gb while disk had only one 60Gb partitioned with FAT32/NTFS.
Also recognized 64 heads, 57231 cylinders and 32 sectors (same as from fdisk -l), which obviously differs from manufacturer disk geometry.
testdisk.log:
Thu Sep 17 19:09:26 2009
Command line: TestDisk
TestDisk 6.8, Data Recovery Utility, August 2007
Christophe GRENIER
Linux version (ext2fs lib: 1.40.2, ntfs lib: 9:0:0, reiserfs lib: 0.3.1-rc8, ewf lib: none)
Using locale 'C'.
Hard disk list
Disk /dev/sda - 100 GB / 93 GiB - CHS 12161 255 63, sector size=512
Disk /dev/sdb - 60 GB / 55 GiB - CHS 57231 64 32, sector size=512
Disk /dev/sdb - 60 GB / 55 GiB
Partition table type: Intel
Interface Advanced
New options :
Dump : No
Cylinder boundary : Yes
Allow partial last cylinder : No
Expert mode : No
Analyse Disk /dev/sdb - 60 GB / 55 GiB - CHS 57231 64 32
Current partition structure:
Partition sector doesn't have the endmark 0xAA55
Ask the user for vista mode
Computes LBA from CHS for Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
Allow partial last cylinder : Yes
search_vista_part: 1
search_part()
Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
Search for partition aborted
Results
interface_write()
No partition found or selected for recovery
search_part()
Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
Search for partition aborted
Results
interface_write()
No partition found or selected for recovery
simulate write!
write_mbr_i386: starting...
Store new MBR code
write_all_log_i386: starting...
No extended partition
Analyse Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
Current partition structure:
Partition sector doesn't have the endmark 0xAA55
Ask the user for vista mode
Allow partial last cylinder : Yes
search_vista_part: 1
search_part()
Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
Results
interface_write()
No partition found or selected for recovery
search_part()
Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
NTFS at 8956/63/32
heads/cylinder 255 (NTFS) != 64 (HD)
sect/track 63 (NTFS) != 32 (HD)
filesystem size 24579387
sectors_per_cluster 8
mft_lcn 1024141
mftmirr_lcn 1650676
clusters_per_mft_record -10
clusters_per_index_record 1
NTFS part_offset=9392094720, part_size=12584646144, sector_size=512
NTFS partition cannot be added (part_offset<part_size).
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 34129 1 1 75201 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=69896224, size=84116272, end=154012495, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 34632 2 1 75704 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=70926400, size=84116272, end=155042671, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 34668 0 1 75740 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=71000064, size=84116272, end=155116335, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 34673 1 1 75745 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=71010336, size=84116272, end=155126607, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 34699 2 1 75771 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=71063616, size=84116272, end=155179887, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 34708 2 1 75780 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=71082048, size=84116272, end=155198319, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 36338 0 1 77410 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=74420224, size=84116272, end=158536495, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 36367 0 1 77439 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=74479616, size=84116272, end=158595887, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 36401 2 1 77473 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=74549312, size=84116272, end=158665583, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 36414 2 1 77486 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=74575936, size=84116272, end=158692207, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 37949 1 1 79021 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=77719584, size=84116272, end=161835855, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 37955 1 1 79027 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=77731872, size=84116272, end=161848143, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 37989 1 1 79061 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=77801504, size=84116272, end=161917775, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 38404 0 1 79476 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=78651392, size=84116272, end=162767663, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 39636 2 1 80708 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=81174592, size=84116272, end=165290863, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 41263 1 1 82335 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=84506656, size=84116272, end=168622927, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 41266 1 1 82338 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=84512800, size=84116272, end=168629071, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 41660 0 1 82732 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=85319680, size=84116272, end=169435951, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 42898 0 1 83970 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=87855104, size=84116272, end=171971375, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 43244 1 1 84316 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=88563744, size=84116272, end=172680015, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 44870 2 1 85942 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=91893824, size=84116272, end=176010095, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 44930 2 1 86002 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=92016704, size=84116272, end=176132975, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 46961 0 1 88033 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=96176128, size=84116272, end=180292399, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 47312 0 1 88384 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=96894976, size=84116272, end=181011247, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 48393 2 1 89465 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=99108928, size=84116272, end=183225199, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 49633 2 1 90705 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=101648448, size=84116272, end=185764719, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 50767 1 1 91839 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=103970848, size=84116272, end=188087119, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 51150 1 1 92222 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=104755232, size=84116272, end=188871503, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 51941 1 1 93013 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=106375200, size=84116272, end=190491471, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 52759 0 1 93831 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=108050432, size=84116272, end=192166703, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 53069 1 1 94141 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=108685344, size=84116272, end=192801615, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 53768 0 1 94840 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=110116864, size=84116272, end=194233135, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 54287 0 1 95359 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=111179776, size=84116272, end=195296047, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 54493 2 1 95565 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=111601728, size=84116272, end=195717999, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 54861 1 1 95933 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=112355360, size=84116272, end=196471631, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 54890 2 1 95962 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=112414784, size=84116272, end=196531055, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 54953 2 1 96025 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=112543808, size=84116272, end=196660079, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 56330 1 1 97402 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=115363872, size=84116272, end=199480143, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 56334 0 1 97406 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=115372032, size=84116272, end=199488303, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 57203 0 1 98275 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=117151744, size=84116272, end=201268015, disk end=117211136)
Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
Check the harddisk size: HD jumpers settings, BIOS detection...
The harddisk (60 GB / 55 GiB) seems too small! (< 103 GB / 95 GiB)
The following partitions can't be recovered:
D Linux 34129 1 1 75201 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 34632 2 1 75704 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 34668 0 1 75740 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 34673 1 1 75745 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 34699 2 1 75771 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 34708 2 1 75780 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 36338 0 1 77410 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 36367 0 1 77439 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 36401 2 1 77473 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 36414 2 1 77486 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 37949 1 1 79021 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 37955 1 1 79027 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 37989 1 1 79061 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 38404 0 1 79476 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 39636 2 1 80708 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 41263 1 1 82335 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 41266 1 1 82338 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 41660 0 1 82732 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 42898 0 1 83970 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 43244 1 1 84316 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 44870 2 1 85942 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 44930 2 1 86002 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 46961 0 1 88033 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 47312 0 1 88384 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 48393 2 1 89465 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 49633 2 1 90705 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 50767 1 1 91839 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 51150 1 1 92222 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 51941 1 1 93013 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 52759 0 1 93831 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 53069 1 1 94141 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 53768 0 1 94840 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 54287 0 1 95359 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 54493 2 1 95565 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 54861 1 1 95933 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 54890 2 1 95962 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 54953 2 1 96025 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 56330 1 1 97402 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 56334 0 1 97406 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 57203 0 1 98275 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
Results
interface_write()
No partition found or selected for recovery
simulate write!
write_mbr_i386: starting...
Store new MBR code
write_all_log_i386: starting...
No extended partition
Interface Advanced
Disk /dev/sdb - 60 GB / 55 GiB
Partition table type: Intel
Disk /dev/sdb - 60 GB / 55 GiB
Partition table type: Intel
New options :
Dump : No
Cylinder boundary : Yes
Allow partial last cylinder : No
Expert mode : No
New options :
Dump : No
Cylinder boundary : Yes
Allow partial last cylinder : No
Expert mode : No
Analyse Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
Current partition structure:
Partition sector doesn't have the endmark 0xAA55
Ask the user for vista mode
Allow partial last cylinder : No
search_vista_part: 0
search_part()
Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
Search for partition aborted
Results
Can't open backup.log file: No such file or directory
interface_load
interface_write()
No partition found or selected for recovery
simulate write!
write_mbr_i386: starting...
Store new MBR code
write_all_log_i386: starting...
No extended partition
TestDisk exited normally.
fixdisktable first output:
% ./fixdisktable -d /dev/sdb
Getting hard disk geometry
cylinders=57231, heads=64, sectors=32
end_offset: 2147482624
FfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSs
EXT2 partition at offset 56832, length=(41072.398 MB) 43067531264
Sectors: start= 111, end= 84116382, length= 84116272
Hd,Sec,Cyl: start(3,16,0) end(28,31,41072)
Done searching for partitions.
Nr AF Hd Sec Cyl Hd Sec Cyl Start Size ID
1 80 3 16 0 63 32 1023 111 84116273 83 (Interpretted)
1 80 3 16 0 63 224 255 111 84116273 83 (RAW)
1: 8003 1000 833f e0ff 6f00 0000 3183 0305
2: 0000 0000 0000 0000 0000 0000 0000 0000
3: 0000 0000 0000 0000 0000 0000 0000 0000
4: 0000 0000 0000 0000 0000 0000 0000 0000
Do you wish to write this partition table to disk (yes/no)? no
fixdisktable second output:
% ./fixdisktable -d -r -v /dev/sdb
Getting hard disk geometry
cylinders=57231, heads=64, sectors=32
end_offset: 2147482624
FfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSs
NTFS partition at offset 17483776, length=(17592186043512.582 MB) 184467440727622 49216
Sectors: start= 34148, end=36028797017147916, length=36028797017113768
Hd,Sec,Cyl: start(43,5,16) end(16,12,2096265)
Done searching for partitions.
Nr AF Hd Sec Cyl Hd Sec Cyl Start Size ID
1 80 43 5 16 63 32 1023 34148 -1850199 07 (Interpretted)
1 80 43 5 16 63 224 255 34148 -1850199 07 (RAW)
1: 802b 0510 073f e0ff 6485 0000 a9c4 e3ff
2: 0000 0000 0000 0000 0000 0000 0000 0000
3: 0000 0000 0000 0000 0000 0000 0000 0000
4: 0000 0000 0000 0000 0000 0000 0000 0000
Do you wish to write this partition table to disk (yes/no)? no
This string "FfEeSsNnBbUu" was repeating there for longer time and it was most probably related to debugging or a verbose mode of fixdisktable
As I have mentioned I will try to connect the disk directly to the computer and see what will happen.
Shall I try to correct the disk geometry to the one specified by manufacturer? Is it possible?
Any suggestions?

IMac G5 Won't Sleep with USB Hard Drive Attached

I purchased an external USB powered hard drive, connected it, put the computer to sleep, and the computer immediately awoke saying the device was not put away properly.
I then unmounted the drive, put the computer to sleep, and got the same message.
Called Seagate support, and they said it's an OS issue.
Returned the drive.
Bought a Hitachi USB powered hard drive. Exact same thing happens.
Is it not possible to put this machine to sleep when attached to a USB powered hard drive? I had no problem with a powered USB drive.

Every external drive in an enclosure has an on/off switch, read the manual that came with the drive, or ask Hitachi. You seem to have it turned on permanently. If you don't turn it off before unplugging it, of course the computer will complain that it was improperly put away - you need to drag the image of the drive to the Trash to eject it before removing the USB cable or click on eject under File in the Menu bar.

Problems with USB external drive attached to time capsule

Similar Messages

Maybe you are looking for