I have XP installed on the internal 40GB HDD, and it boots/functions just fine.
I have adopted a policy of backing up my windows boxes to my server, and currently do this by pulling the drive, and hooking it up to a PATA/SATA USB adapter to my gentoo box. Normally, with any other drive I've ever hooked up, dmesg shows the drive and its partitions, then I use ntfsclone and other tools to image said partitions.
With the drive from this IBM R51 however, I get the following dmesg output:
Code: Select all
usb 1-3: new high speed USB device using ehci_hcd and address 17
usb 1-3: New USB device found, idVendor=152d, idProduct=2338
usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=5
usb 1-3: Product: USB to ATA/ATAPI Bridge
usb 1-3: Manufacturer: JMicron
usb 1-3: SerialNumber: 222254302304
scsi19 : usb-storage 1-3:1.0
scsi 19:0:0:0: Direct-Access TOSHIBA MK4026GAX 6E PQ: 0 ANSI: 2 CCS
sd 19:0:0:0: Attached scsi generic sg1 type 0
sd 19:0:0:0: [sdb] 70194159 512-byte logical blocks: (35.9 GB/33.4 GiB)
sd 19:0:0:0: [sdb] Write Protect is off
sd 19:0:0:0: [sdb] Mode Sense: 00 38 00 00
sd 19:0:0:0: [sdb] Assuming drive cache: write through
sd 19:0:0:0: [sdb] Assuming drive cache: write through
sdb: sdb1
sdb: p1 size 78140097 extends beyond EOD, enabling native capacity
sd 19:0:0:0: [sdb] Assuming drive cache: write through
sdb: sdb1
sdb: p1 size 78140097 extends beyond EOD, truncated
sd 19:0:0:0: [sdb] Assuming drive cache: write through
sd 19:0:0:0: [sdb] Attached SCSI diskThen using fdisk, view the partition table:
Code: Select all
# fdisk -l /dev/sdb
Disk /dev/sdb: 35.9 GB, 35939409408 bytes
240 heads, 63 sectors/track, 4642 cylinders, total 70194159 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
Disk identifier: 0x39bf772f
Device Boot Start End Blocks Id System
/dev/sdb1 * 63 78140159 39070048+ 7 HPFS/NTFSCode: Select all
# mount /dev/sdb1 /mnt/client
Failed to read last sector (78140096): Invalid argument
HINTS: Either the volume is a RAID/LDM but it wasn't setup yet,
or it was not setup correctly (e.g. by not using mdadm --build ...),
or a wrong device is tried to be mounted,
or the partition table is corrupt (partition is smaller than NTFS),
or the NTFS boot sector is corrupt (NTFS size is not valid).
Failed to mount '/dev/sdb1': Invalid argument
The device '/dev/sdb1' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?Did some googling, and saw other similar errors, though all seeming to be in relation to RAID configurations. That is definitely NOT the case here, at least as far as I know. I've had other think pad T-series laptops that never seemed to have any issues with this kind of thing. Is it possible that the BIOS on this unit is doing some funky RAID things with the drive? Why would the kernel see it as a 35.9GB drive instead of the full 40?
Any ideas?
Thanks!
