[SOLVED] Error with usb external HD

Since 1.5.x kernel serie I get the following message on attaching a external usb hb:
ago 14 10:21:42 udisksd[429]: Error performing initial housekeeping for drive /org/freedesktop/UDisks2/drives/ST1000LM024_HN_M101MBB_S2ZPJ9BD491796: Error updating SMART data: sk_disk_check_sleep_mode: Operation not supported (udisks-error-quark, 0)
ago 14 10:21:42 nono kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88020fc5bc48
ago 14 10:21:42 nono kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88020fc5bcd8
ago 14 10:21:42 nono kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88020fc5bc00
ago 14 10:21:42 nono kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88020fc5bc90
ago 14 10:21:42 nono kernel: scsi host6: uas_eh_bus_reset_handler success
ago 14 10:21:42 nono systemd-udevd[150]: worker [500] terminated by signal 9 (Killed)
I've been solving this issue installing an old local 1.4.x kernel file.
Today I have installed a new 1.6.x. kernel and this problem still persists.
Thanks in advance for your help.
Last edited by Miles28 (2014-08-14 14:24:18)

Try disabling the UAS driver, check here [1] how to disable it for a particular drive.
[1] https://bbs.archlinux.org/viewtopic.php?id=183190

Similar Messages

Getting Communication error with the external tax system(VERTEX_MS0018)

Hi All,
I am a new SAP HCM self learner. I am practicing it on company's sandbox system. When I am trying to create a company and saving the address, it is returning Communication error with the external tax system(VERTEX_MS0018). I have already tried to solve is issue by going thru previous related to same issue like
Communication error with the external tax system (VERTEX_MS0018) ...Urgent
but coudn't solve the issue.
Please help. Is this issue coming as I am using a training environment? any alternate approach?

Hi Ravi,
To disable the connection to Vertex:
Goto tcode SPRO > Cross Application Components > Transaction Tax Engine >
Technical Settings> Define External Tax System
Here an RFC would be defined. Remove it and try again.
Also in SPRO > Cross Application Components > Tax Determination based on Jurisdiction Codes > External Tax Jurisdiction > Activate External Tax Jurisdiction.
Remove the entry 'V' here.
Regards,
Srikishan

Portege R500: XP installation with USB external CD/DVD drive - SOLUTION

Hello all !
Just wanted to take five minutes to inform you that installing XP on a Portege R500 with USB external CD/DVD drive is possible, even if you already have erased Vista and only with a bootable CD of Win XP in hand.
First go into your BIOS and check / set first boot device is CD/DVD drive
Start your installation of win XP from the CD without the F6 thing and let it go his way
After a while, the installation stops and says "can't find the file xxxx" and you are invited to say where this file is
You "just" have to replace the drive letter "C:" that is given by default with the drive letter of your CD/DVD (and let the rest just like it is) and the installation will continue until the next "can't find..." and you will again replace the drive letter, etc..
After a complete "manually assisted automatic" installation, you are welcome in Win XP !
Next question is "Where can I find my CD/DVD drive letter ?" and the answer is "this is the next letter after your last HDD letter" (I consider you have only your Portege with nothing else plugged than your CD/DVD) so in most cases it will be "E" because C: is the first partition of your HDD and D: is the hidden / recovery partition that win creates.
But do not worry, if you type the wrong letter you will have as many tries as you wish until you find the good one and for the following "can't find..." it will remain the same.
I hope these pieces of information will help some of you who want a clean install of win XP starting from a newly formatted HDD.
With kind Regards,
Mage.

What a great information!
Thanks a lot for this posting.
I think it could be useful for others here.
Bye

Communication error with the external tax system(vertex_ms0018)

Hi All
I have installed ECC6 IDES S/W on my PC. I have activated SAP Insurance module (FS-CD). When I try to create business partner using FPP1 with US address, It is throwing error as follows:
"communication error with the external tax system(vertex_ms0018)"
I dont want to use any external Tax system like Vertex etc. because I am not calculating any taxes.
I gave correct US address with valid ZIP etc. but no use.
Please help me if any one of you has idea. How to overcome this error. How to deactivate connection to external tax system.
Your help will be greatly appreciated.
Thanks
Giri

Hi Giri,
I've notice that you took the 'V' from the configuration but you left the RFC destination.
Clearly the RFC destination is not working thus the reason you get the error (in your case, your server can't determine a valid IP address for the host iwdf8334.wdf.sap.corp).
To sort out the problem you got I can think of at least two ways:
1. Get the RFC connection working (get the correct setup for it) using transaction SM59
2. Or if you don't really need the external tax calculations, remove the RFC configuration from TAXUJ under Assign RFC Destination to Country on the Cross-Application SPRO entry.
3. You can always add TAXUS to transaction OBBG if you require it (as it comes out of the box).
This should fix the problem you are having but I'm assuming you don't need the external tax calculations.
If you do, just fix the connection using SM59 (you may want to ask for help from your Basis team if you don't know how to do it).
Cheers
Jorge Laranjo
[email protected]
+44 741 847 5946

Airport Extreme n: error with USB HDD; Update 5.1 crashes

Ok, seems to be a few bugs for me:
I have no Macs as yet, so operating with an old IBM T30 WinXP laptop until WWDC in June when (hopefully) Steve will announce a new MBP
1) Cannot connect to my 300Gb Maxstor external HDD, keep getting the 'disk needs repair' error with the Airport Utility. It's previously formatted to NTFS, cannot format to FAT32 as the volume is too big according to Windows....
2) I can't update the Utility to 5.1 so can't update the Firmware either. Have tried unsuccessfully to update to 5.1 but when I do, it just crashes when I try to run it so I'm stuck with v5.0 for the meantime.
Any ideas or peeps getting the same from their Windows machines ?
Most important for me is to see the external HD, it's got all my media on it.
Cheers in advance

Hi!
I've found a good tutorial that can help you format harddrives to FAT32, for volumes under 2TB. You have to download a small application called fat32format.exe, and execute it in a command prompt in Win XP. But take a look at the tutorial:
http://www.crapcontrol.com/content.php?article.14
-Martin
PC Windows XP

[SOLVED] errors with fdisk and cryptsetup; is my drive going bad?

I'm having issues with re-formatting an external hard drive using dm-crypt. It was previously formatted with TrueCrypt/NTFS, which I used as a shared backup drive between Windows and Arch. At some point, it stopped being able to mount, which I attributed to allowing Windows to "fix" it after improper dismount (e.g. a hard kill).
I decided to re-format with ext4 and only use it from Arch, but now I'm wondering if I may have a hardware issue with the drive. I've tried a lot more (like going through the full zero write after mounting the drive as a temporary dm-crypt device), but here's the condensed version to illustrate the problem.
system info
This is on a fresh boot. Just adding that as I've had issues with kernel modules after updating if a new kernel comes through. A fresh boot removes that potential issue.
$ uname -a
Linux arch_840 4.0.3-1-ARCH #1 SMP PREEMPT Wed May 13 15:38:47 CEST 2015 x86_64 GNU/Linux
$ lsmod | grep dm_
dm_crypt 28672 2
dm_mod 98304 5 dm_crypt
$ lsmod |grep xts
xts 16384 2 serpent_sse2_x86_64,twofish_x86_64_3way
gf128mul 16384 2 lrw,xts
smartctl status
Figured I should check the drive. There's a lot of old age and pre-fail warnings, but this post would seem to suggest I'm okay?
# smartctl -A /dev/sdb
smartctl 6.3 2014-07-26 r3976 [x86_64-linux-4.0.3-1-ARCH] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF READ SMART DATA SECTION ===
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 0
2 Throughput_Performance 0x0026 252 252 000 Old_age Always - 0
3 Spin_Up_Time 0x0023 090 089 025 Pre-fail Always - 3330
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 703
5 Reallocated_Sector_Ct 0x0033 252 252 010 Pre-fail Always - 0
7 Seek_Error_Rate 0x002e 252 252 051 Old_age Always - 0
8 Seek_Time_Performance 0x0024 252 252 015 Old_age Offline - 0
9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 3707
10 Spin_Retry_Count 0x0032 252 252 051 Old_age Always - 0
11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 104
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 734
191 G-Sense_Error_Rate 0x0022 100 100 000 Old_age Always - 17
192 Power-Off_Retract_Count 0x0022 252 252 000 Old_age Always - 0
194 Temperature_Celsius 0x0002 064 053 000 Old_age Always - 24 (Min/Max 16/47)
195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always - 0
196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 252 252 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0036 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 3
223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 104
225 Load_Cycle_Count 0x0032 079 079 000 Old_age Always - 214068
Disk info, delete existing partition, new MBR, create new partition
# fdisk /dev/sdb
Welcome to fdisk (util-linux 2.26.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Command (m for help): p
Disk /dev/sdb: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x76d37b6d
Device Boot Start End Sectors Size Id Type
/dev/sdb1 63 976768064 976768002 465.8G 83 Linux
Command (m for help): d
Selected partition 1
Partition 1 has been deleted.
Command (m for help): o
Created a new DOS disklabel with disk identifier 0x2cd60f13.
Command (m for help): n
Partition type
p primary (0 primary, 0 extended, 4 free)
e extended (container for logical partitions)
Select (default p): p
Partition number (1-4, default 1):
First sector (2048-976773167, default 2048):
Last sector, +sectors or +size{K,M,G,T,P} (2048-976773167, default 976773167):
Created a new partition 1 of type 'Linux' and of size 465.8 GiB.
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.
trying to format with cryptsetup
I had a bunch of custom options, but other Arch posts suggested just trying the default, which is what I've done here. It fails with the same error as when I try to pass a cipher, key size, etc. ("Command failed with code 5: IO error while encrypting keyslot.").
# truecrypt -v --debug luksFormat /dev/sdb1
bash: truecrypt: command not found
[root@arch_840 jwhendy]# cryptsetup -v --debug luksFormat /dev/sdb1
# cryptsetup 1.6.6 processing "cryptsetup -v --debug luksFormat /dev/sdb1"
# Running command luksFormat.
# Locking memory.
# Installing SIGINT/SIGTERM handler.
# Unblocking interruption on signal.
WARNING!
========
This will overwrite data on /dev/sdb1 irrevocably.
Are you sure? (Type uppercase yes): YES
# Allocating crypt device /dev/sdb1 context.
# Trying to open and read device /dev/sdb1.
# Initialising device-mapper backend library.
# Timeout set to 0 miliseconds.
# Iteration time set to 1000 miliseconds.
# Interactive passphrase entry requested.
Enter passphrase:
Verify passphrase:
# Formatting device /dev/sdb1 as type LUKS1.
# Crypto backend (gcrypt 1.6.3) initialized.
# Detected kernel Linux 4.0.3-1-ARCH x86_64.
# Topology: IO (512/0), offset = 0; Required alignment is 1048576 bytes.
# Checking if cipher aes-xts-plain64 is usable.
# Using userspace crypto wrapper to access keyslot area.
# Generating LUKS header version 1 using hash sha1, aes, xts-plain64, MK 32 bytes
# KDF pbkdf2, hash sha1: 996745 iterations per second.
# Data offset 4096, UUID 181fed4d-42f2-4f0f-8b70-cb7ba459e25f, digest iterations 121625
# Updating LUKS header of size 1024 on device /dev/sdb1
# Key length 32, device size 976771120 sectors, header size 2050 sectors.
# Reading LUKS header of size 1024 from device /dev/sdb1
# Key length 32, device size 976771120 sectors, header size 2050 sectors.
# Adding new keyslot -1 using volume key.
# Calculating data for key slot 0
# KDF pbkdf2, hash sha1: 1008246 iterations per second.
# Key slot 0 use 492307 password iterations.
# Using hash sha1 for AF in key slot 0, 4000 stripes
# Updating key slot 0 [0x1000] area.
# Using userspace crypto wrapper to access keyslot area.
IO error while encrypting keyslot.
# Releasing crypt device /dev/sdb1 context.
# Releasing device-mapper backend.
# Unlocking memory.
Command failed with code 5: IO error while encrypting keyslot.
Things also tend to hang with respect to the drive at this point. For example, fdisk -l spits out /dev/sda partitions immediately and then just hangs instead of printing out /dev/sdb info, then eventually quits (without ever writing it).
Any suggestions on where to look/how to troubleshoot? I found some possibly related posts, but nothing that looks promising:
- Impossible to crypt the drive using cryptsetup (fixed by rebooting)
- cryptsetup fails to open Udev cookie 0xd4d94f5 (semid 0) waiting for z (no responses; the hang after seems similar)
There's a couple odds and ends references to cryptsetup 1.6.6 having issues. I downloaded 1.6.4-1 and 1.6.5-1 and -2 from ARM to try, but wanted to post this in the meantime in case something stuck out.
Last edited by jwhendy (2015-05-29 16:01:40)

@qinohe I thought of that and the other day started formatting with mkfs.ext4; unfortunately, it was at work and I had to leave before I could let it finish. It had been chugging along a good few hours, and I was surprised it would take that long. I was able to format it with ext4 using Windows 7 (I dual boot) with the MiniTool Partition Wizard but I didn't use it like that before trying to solve the cryptsetup issue again.
This last time around, I was getting unresponsive behavior. I think I need to reboot each time I try something with cryptsetup, as any commands related to that drive seem to hang afterwards (fdisk, umount, eject, mkfs, or trying crypsetup again). Perhaps I'll just let it cook overnight with mkfs and see if I can at least have an unencrypted, but functional drive.
One interesting tidbit is that even though cryptsetup fails, when I've tried to issue mkfs afterward, it asks me to confirm that I want to format the disk since it has a LUKS header... so something appears to have been written. Is it possible the header is causing some issues? I don't know much about the structure of a disk (like what range the MBR resides in, what constitutes a header, etc.) but have been wondering if there's some way to start really, really clean with the disk. Like I'd just bought it -- something appears to be lingering around from previous efforts?
@frostschutz I'll check tomorrow. That's a good question. Just checked journalctl and here are some of the errors that appear; unfortunately, I wasn't watching so I can't tell you what matches up with what command:
May 23 09:32:22 arch_840 systemd-udevd[7784]: inotify_add_watch(7, /dev/sdb1, 10) failed: No such file or directory
May 23 09:32:22 arch_840 kernel: usb 3-4: stat urb: status -108
### there's lots like this; like 10 in a row with various sector values listed
May 23 09:32:19 arch_840 kernel: Buffer I/O error on dev sdb1, logical block 61341696, lost async page write
May 23 09:32:19 arch_840 kernel: blk_update_request: I/O error, dev sdb, sector 490735616
### there's also a bunch like this, from tab #0 -> #29 (not colored red, so not sure they're errors?)
May 23 09:32:19 arch_840 kernel: sd 2:0:0:0: [sdb] tag#0 CDB: opcode=0x2a 2a 00 1d 07 bc 10 00 04 00 00
May 23 09:32:18 arch_840 kernel: sd 2:0:0:0: [sdb] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD OUT
I paged down quite a ways and those seem like the unique messages when I search the journal for "sdb". Anything stand out? I will say that the same sector numbers appeared in multiple blocks of the third error type listed, so that makes me wonder if something is genuinely wrong with the disk. I'll post the output of the full smartctl scan when I hopefully run it tomorrow.
Thanks for chiming in!

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?

Solve Problem with USB Connection / Read this it i...

i can not load maps on my n97 mini. the error 'usb connection lost...' show on the screen in map loader but at the first day i had no problems.
i wonder why. i look for driver, ovi suite, pc suite, usb at the pc, read in the forum and many more. but nothing solve the problem. after 2 days i use accidentally the original cable which comes with the nokia n97 mini (it is a ca-101) and all my problems are gone ! bevor i use an 'old' ca-101 cabel from my n82 and i can not upload a map but the handy is shown in the pc system with all drivers and no problems. only loading big megabytes data on the handy crashes the usb connection. with the n97 mini ca-101 cabel no problem with gigabytes. i look for another ca-101 cable from the 6220 from my wife and i have the same problems (i never used bevor this cable for a connection to any handy ! it was brand new !). it seems that 'old' ca-101 cabels do not handle big data with the n97 mini. i look on the gold spring clips in the micro usb and could see that the are a little smaller and not so high in the jack in the 'old' cables. all three cables are original from nokia and not from china ! if you are also problems look on the produkt id on the plastics. if the letters are gold you have a cable like my n97 mini cable, but if the letters are black on a silver button you have an 'old' cable.
i hope i can help another with this maniac problem
greetings

I can verify this on win7 with latest PC suite.
I was using the cable that came with my 6500s as I didn't want to tackle the rats nest of wiring behind my pc.
This cable is a ca101 with silver writing on the plastic tab, made in China.
Using this cable, my 6620c would not complete a backup, it would just sit for hours on 2-4%.
Tested with the ca101 cable that came with the 6620c (gold writing, made in Thailand).
This time the backup completed in about 2 minutes.
Thank you so much for finding this, it has been driving me crazy!

Upgrade to Yosemite, iPhoto won't open and NTFS-3G could not mount error with new external HD

Help!
I just did a software update to get OS X Yosemite 10.10.2 on my MacBook Pro.
Now iPhoto won't open and I get this error:
"Your photo library is either in use by another application or has become unreadable....Shut down and restart your computer, and then open iPhoto again. If the problem persists, try rebuilding your photo library. To do this, quit iPhoto, and then reopen it while keeping the Option and Command keys pressed. You can also try restoring your photo library from a backup."
So I do this and try to repair the database as suggested and I get another error:
"iPhoto will open as soon as the iPhoto library is available. Time Machine might be backing it up."
But it's not - no external hard drive is connected.
I'm terrified I can't get access to my photos (and I admit I haven't backed up with Time Machine for over a year - my mistake that I won't make again).
So I bought a brand new external hard drive (seagate for mac and pc, 2TB) so I could save only my photos to the hard drive (because I googled and read you can manually save your photos to disk by dragging and dropping the photo library onto the external hard drive).
But I can't even get the hard drive to work....I get this error
"NTFS-3G could not mount /dev/disk2s1
at /Volumes/Seagate Backup Plus Drive because the following problem occurred:
/Library/Filesystems/fusefs.fs/Support/fusefs.kext failed to load - (libkern/kext) link error; check the system/kernel logs for errors or try kextutil(8).
the MacFUSE file system is not available (71)"
I google the issue again and it says to uninstall NTFS-3G but I actually think I just deleted it a long ago without uninstalling it properly?? I don't know....
(a) how do i fix iphoto
(b) how do i get external hard drives to work with this OS (I've read lots of posts and don't really understand the advice)
(c) how do i get all my photos onto the hard drive safely so I can import them onto a PC
Any assistance would be magic for this little lady!

(c) how do i get all my photos onto the hard drive safely so I can import them onto a PC
First see if you can reformat the EHD to MS-DOS FAT with Disk Utility. If you can
open iPhoto and select all of the Events in the Events mode. Use the File ➙ Export ➙ File Export menu option and export to the EHD with these settings:
Select the destination for the export to be the EHD or a folder on the EHD. This process will create a folder for each Event in your library with the same name as the Event and contain the original image files. The EHD will be useable by a PC and the photos will be available also.

[SOLVED]Error with xf86-video-ati 6.12.99.git20091221-1 + mesa-7.6.1-1

Upgrade mesa (7.6-2 -> 7.6.1-1), libgl (7.6-2 -> 7.6.1-1), libgl (7.6-2 -> 7.6.1-1) and ati-dri (7.6-2 -> 7.6.1-1) from testing broke my resolution in KDE - X start only with vesa driver.
I don't use xorg.conf, kernel is kernel26 2.6.32.2-1 from testing, KMS disabled (don't work with this kernel)
/var/log/Xorg.0.log:
(II) LoadModule: "radeon"
(II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so
dlopen: libdrm_radeon.so.1: cannot open shared object file: No such file or directory
(EE) Failed to load /usr/lib/xorg/modules/drivers/radeon_drv.so
(II) UnloadModule: "radeon"
(EE) Failed to load module "radeon" (loader failed, 7)
(II) LoadModule: "vesa"
Compiling xf86-video-ati-git (20091223-1) solve this problem
Last edited by Tapan (2009-12-23 14:19:23)

I have kernel 2.6.31-ARCH, nothing testing repository but in my
grep EE /var/log/Xorg.0.log
Current Operating System: Linux skynet 2.6.31-ARCH #1 SMP PREEMPT Tue Nov 10 19:01:40 CET 2009 x86_64
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(II) Loading extension MIT-SCREEN-SAVER
(EE) Failed to load module "fbdev" (module does not exist, 0)
(EE) RADEON(0): [dri] RADEONDRIGetVersion failed because of a version mismatch.
(EE) Microsoft Comfort Curve Keyboard 2000: failed to initialize for relative axes.
and, for example, switch for different desktop is very slow. Also maximized windows is very slow (I'm using xfce with compositing)

Problem with USB/External-HDD/etc... not writing?

Hello...
Recently I've been having a problem with my USB, and external harddrive. It seems that for some reason when I copy files to the device, they do not write. If I go and view the device contents on another PC, my files aren't there, but on this PC they are.
The only way that they will copy is if I right click and select "Safely Remove Drive."
I never used to have to do this; Is there a way to make files auto write?
Thanks in advance,
Stephen

Hi, you need to use -sync mount option.

Wireless Router with USB + External Hard Drive = Time Capsule?

So I bought a TP-Link WR710N wireless router http://www.tp-link.com/en/products/details/?model=TL-WR710N which seems to support external storage in its USB port. I tried with various storage media and it kinda works. The bad thing is that it only sees NTFS drives. I tried an external hard drive formated for Windows and a USB stick, also formated for Windows and it discovered them. But when I tried my external hard drive which is formatted as Mac OS Extended (Journaled), which I was using for Time Machine, it couldn't see it. Neither the TP-Link software, nor the Time Machine software.
Is there any way I could use this router with this hard drive for wireless backing up with Time Machine NOT buying extra equipment (NAS, AirPort Extreme or Time Capsule) ?
Thanks.

m3adi3c wrote:
Is there any way I could use this router with this hard drive for wireless backing up with Time Machine NOT buying extra equipment (NAS, AirPort Extreme or Time Capsule) ?
Thanks.
No
Take it back and get a Time Capsule or keep it and buy a regular external drive and connect it to the Mac directly.

Time Machine freezes with USB External attached to iMac

I've got a WD 320GB external USB HD attached to my iMac. I've formatted the external and set it up for Time Machine backups, but it freezes every single time midway through the backup process. Yesterday I tried for the third time, wiped the drive and again set it up for Time Machine. I then started the backup process, with an estimated 8-9 hours remaining. Woke up this morning and the time machine process stopped backing up at ~70gb, still saying it was in progress but nothing was being accomplished. My computer is not set to sleep whatsoever and the hard drive is having no issues with SMART status. It's been formatted properly as Time Machine recognizes this and does start the backup process.
How can I ever utilize Time Machine if something in Lion keeps preventing the backup from being completed? Any suggestions/recommendations?

Boot in safe mode. First, disconnect all wired peripherals except keyboard, mouse, and backup drive, if applicable. The instructions provided by Apple are as follows:
Be sure your Mac is shut down.
Press the power button.
Immediately after you hear the startup tone, hold the Shift key. The Shift key should be held as soon as possible after the startup tone, but not before the tone.
Release the Shift key when you see the gray Apple icon and the progress indicator (looks like a spinning gear).
The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
Safe mode is much slower to boot and run than normal, and some things won’t work at all, including your login items.
Manually start a backup from the Time Machine menu or preference pane. Same result?
After backing up, reboot as usual (i.e., not in safe mode.)

[SOLVED] Error with the php5 module for apache

Hi!
I've installed Apache 2.0.55-1 and PHP5 5.1.4-4. When I try to run the apache server it fails. Then I do httpd -k start and I get:
Syntax error on line 262 of /etc/httpd/conf/httpd.conf:
API module structure `php5_module' in file /usr/lib/apache/libphp5.so is garbled - perhaps this is not an Apache module DSO?
The file libphp5 exists, but seems corrupted.
See you
NeOnsKuLL

That version of the package has been built with apache 2.2.x. Be sure to use that version of apache too, as 2.0 won't work with that specific package.

[Partially Solved] Error with bsdtar and symbolic links

I'm trying to install a package (asymptote) from AUR but am running into an odd error. During the extract phase I get errors like
asymptote-1.70/base/asy-keywords.el: Can't update time for asymptote-1.70/base/asy-keywords.el: Function not implemented
bsdtar: Error exit delayed from previous errors.
I found a post that may help: http://bbs.archlinux.org/viewtopic.php?id=50750. Do I really have to do this?
By the way, I too am running on a Linode (Xen virtualization).
Thanks,
Luis
Last edited by banbh (2009-05-24 00:22:13)

I have not got to the bottom of my problems with bsdtar and symlinks. I suspect it must have something to do with either my configuration (derived from the Arch image provided by Linode) or running under virtualisation.
However, others might find my work-around useful, so I document it below.
I downloaded asymptote from AUR using wget ("wget http://aur.archlinux.org/packages/asymptote/asymptote.tar.gz"), unpacked it, then patched the PKGBUILD
$ diff -u PKGBUILD.orig PKGBUILD
--- PKGBUILD.orig 2009-05-23 17:58:47.000000000 -0400
+++ PKGBUILD 2009-05-23 18:00:49.000000000 -0400
@@ -11,9 +11,12 @@
'used if present at compile time: freeglut, gsl, fftw')
source=(http://downloads.sourceforge.net/sourceforge/asymptote/$pkgname-$pkgver.src.tgz)
md5sums=('1ded335bc63b662a6eb920a4c065706c')
+noextract=($pkgname-$pkgver.src.tgz)
build() {
- cd $srcdir/$pkgname-$pkgver
+ cd $srcdir
+ tar xzf $pkgname-$pkgver.src.tgz
+ cd $pkgname-$pkgver
./configure --enable-gc=/usr --prefix=/usr \
--with-latex=/usr/share/texmf/tex/latex || return 1
make asy || return 1
After that I simply did a "makepkg" followed by "sudo pacman -U asymptote-1.73-1-i686.pkg.tar.gz"

[SOLVED] Error with usb external HD

Similar Messages

Maybe you are looking for