Ho comprato 10 giorni fa un hard disk da 4 TB. Provvisoriamente l’ho inserito dentro il case al posto del secondo hard disk; ho creato con gparted una tavola delle partizioni gtp, poi ho creato un’unica partizione ntfs di 4 TB, e ho copiato nel nuovo hard disk, con pazienza, tutta una serie di files (ci sono voluti diversi giorni). Ho fatto il controllo dello sha1sum, che corrisponde file per file, spento e riacceso il computer varie volte, quindi è tutto a posto. Ho letto e scritto files nel nuovo hard disk da 4 TB senza problemi.
Ora, però, l’ho tolto dal case e inserito in un box esterno sata marca novita, collegato al computer con cavo usb, in cui tenevo in precedenza un altro hard disk da 2 TB, ma non riesco più a leggere nulla:
[code]# gdisk /dev/sdc
GPT fdisk (gdisk) version 0.8.5
Warning! Disk size is smaller than the main header indicates! Loading
secondary header from the last sector of the disk! You should use ‘v’ to
verify disk integrity, and perhaps options on the experts’ menu to repair
the disk.
Caution: invalid backup GPT header, but valid main header; regenerating
backup header from main header.
Warning! One or more CRCs don’t match. You should repair the disk!
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: damaged
Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk
verification and recovery are STRONGLY recommended.
Command (? for help): v
Caution: The CRC for the backup partition table is invalid. This table may
be corrupt. This program will automatically create a new backup partition
table when you save your partitions.
Problem: The secondary header’s self-pointer indicates that it doesn’t reside
at the end of the disk. If you’ve added a disk to a RAID array, use the ‘e’
option on the experts’ menu to adjust the secondary header’s and partition
table’s locations.
Problem: Disk is too small to hold all the data!
(Disk size is 3519069872 sectors, needs to be 7814037168 sectors.)
The ‘e’ option on the experts’ menu may fix this problem.
Problem: partition 1 is too big for the disk.
Identified 4 problems!
Command (? for help): [/code]
Se può servire, allego l’output di lsusb relativo all’hard disk incriminato:
$ lsusb | grep SATALink
Bus 002 Device 007: ID 04fc:0c25 Sunplus Technology Co., Ltd SATALink SPIF225A
[code]$ (lsusb -v 2>/dev/null) | grep -a46 SATALink
Bus 002 Device 007: ID 04fc:0c25 Sunplus Technology Co., Ltd SATALink SPIF225A
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x04fc Sunplus Technology Co., Ltd
idProduct 0x0c25 SATALink SPIF225A
bcdDevice 1.03
iManufacturer 2
iProduct 3
iSerial 1
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 4
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-Only
iInterface 5
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 0 [/code]
Ovviamente, l’hard disk non viene più montato, e risulta impossibile leggere i files che contiene.
Pensate che debba comprare un case nuovo, o si può fare qualcosa?