Fui tan tonto que apagué mi Readynas Ultra 4 cuando estaba instalando el disco (3TB WD Green), no tuve tiempo de esperar porque lo iba a devolver (era demasiado ruidoso). La instalación del disco estaba al 0% y permaneció así durante 2 minutos, así que decidí apagarlo sin pensar realmente en las consecuencias. De todos modos, ya está hecho y necesito instalarlo en mi nuevo NAS (Synology 413j), pero eso no va muy bien. El disco se reconoce en BIOS y lo aparece como /dev/sdc cuando ejecuto gparted live en USB. Pero no se muestra en el administrador de dispositivos de Windows ni en Ubuntu. Cuando ejecuto Sudo gparted en un USB ubuntu en vivo, aparece un error de entrada/salida durante la lectura en /dev/sdc.
He probado más cosas en gparted live, pero para resumir, es muy similar a lo que está sucediendo aquí:http://ubuntuforums.org/archive/index.php/t-1492414.html Hasta la parte en la que ejecuta badsectors y obtiene muchos errores, ejecuté badsectors -vs (supongo que solo se lee y muestra el resultado. Lo ejecuté durante aproximadamente 3000 sectores, y para cada bloque contó, el resultado fue: ( etcétera)
1
2
3
4
5
6
7
8
9
10
11
12
13
140.00% done, 0:01 elapsed. (14/0/0 errors)
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
310.00% done, 0:02 elapsed. (31/0/0 errors)
En gparted(live), se muestra el disco /dev/sdc, pero no está asignado y muestra un error de lectura de entrada/salida cuando escanea todos los discos. Cuando intento crear una nueva partición, aparece un error sin tabla de particiones. Voy al dispositivo: crear tabla de particiones y selecciono gpt, obtengo entre 5 y 6 errores con la lectura de entrada/salida y también escribo en /dev/sdc.
Cuando entro a gdisk en gparted(live) obtengo:
Warning! Read error 5; strange behavior now likely!
Warning! Read error 5; strange behavior now likely!
Partition table scan:
MBR: not present
BSD: not present
APM: not present
GPT: not present
Creating new GPT entries.
Cuando ejecuto smartctl:
ubuntu@ubuntu:~$ sudo smartctl --all /dev/sdc
smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.2.0-29-generic] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF INFORMATION SECTION ===
Device Model: WDC WD30EZRX-00MMMB0
Serial Number: WD-WCAWZ2205xxxxx
LU WWN Device Id: 5 0014ee 25c5f8480
Firmware Version: 80.00A80
User Capacity: 3,000,592,982,016 bytes [3.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 8
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Sat Sep 29 15:53:44 2012 UTC
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x84) Offline data collection activity
was suspended by an interrupting command from host.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: (50700) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 255) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x3035) SCT Status supported.
SCT Feature Control supported.
SCT Data Table supported.
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 200 200 051 Pre-fail Always - 0
3 Spin_Up_Time 0x0027 199 140 021 Pre-fail Always - 7050
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 483
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0
9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 572
10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0
11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 142
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 31
193 Load_Cycle_Count 0x0032 198 198 000 Old_age Always - 8522
194 Temperature_Celsius 0x0022 114 095 000 Old_age Always - 38
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 1
198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed: read failure 90% 569 42084912
# 2 Short offline Completed without error 00% 388 -
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
Mi sesión de gdisk aquí abajo: Pero lo más útil que encontré al final: ¡Advertencia! ¡La tabla de particiones principal se superpone a la primera partición en 34 bloques! Deberá eliminar esta partición o cambiar su tamaño en otra utilidad.
user@debian:~$ sudo gdisk
GPT fdisk (gdisk) version 0.8.5
Type device filename, or press <Enter> to exit: /dev/sdc
Warning! Read error 5; strange behavior now likely!
Warning! Read error 5; strange behavior now likely!
Partition table scan:
MBR: not present
BSD: not present
APM: not present
GPT: not present
Creating new GPT entries.
Command (? for help): ?
b back up GPT data to a file
c change a partition's name
d delete a partition
i show detailed information on a partition
l list known partition types
n add a new partition
o create a new empty GUID partition table (GPT)
p print the partition table
q quit without saving changes
r recovery and transformation options (experts only)
s sort partitions
t change a partition's type code
v verify disk
w write table to disk and exit
x extra functionality (experts only)
? print this menu
Command (? for help): n
Partition number (1-128, default 1): 1
First sector (34-5860533134, default = 2048) or {+-}size{KMGTP}: 2048
Last sector (2048-5860533134, default = 5860533134) or {+-}size{KMGTP}: 5860533134
Current type is 'Linux filesystem'
Hex code or GUID (L to show codes, Enter = 8300): l
0700 Microsoft basic data 0c01 Microsoft reserved 2700 Windows RE
4200 Windows LDM data 4201 Windows LDM metadata 7501 IBM GPFS
7f00 ChromeOS kernel 7f01 ChromeOS root 7f02 ChromeOS reserved
8200 Linux swap 8300 Linux filesystem 8301 Linux reserved
8e00 Linux LVM a500 FreeBSD disklabel a501 FreeBSD boot
a502 FreeBSD swap a503 FreeBSD UFS a504 FreeBSD ZFS
a505 FreeBSD Vinum/RAID a580 Midnight BSD data a581 Midnight BSD boot
a582 Midnight BSD swap a583 Midnight BSD UFS a584 Midnight BSD ZFS
a585 Midnight BSD Vinum a800 Apple UFS a901 NetBSD swap
a902 NetBSD FFS a903 NetBSD LFS a904 NetBSD concatenated
a905 NetBSD encrypted a906 NetBSD RAID ab00 Apple boot
af00 Apple HFS/HFS+ af01 Apple RAID af02 Apple RAID offline
af03 Apple label af04 AppleTV recovery af05 Apple Core Storage
be00 Solaris boot bf00 Solaris root bf01 Solaris /usr & Mac Z
bf02 Solaris swap bf03 Solaris backup bf04 Solaris /var
bf05 Solaris /home bf06 Solaris alternate se bf07 Solaris Reserved 1
bf08 Solaris Reserved 2 bf09 Solaris Reserved 3 bf0a Solaris Reserved 4
bf0b Solaris Reserved 5 c001 HP-UX data c002 HP-UX service
ef00 EFI System ef01 MBR partition scheme ef02 BIOS boot partition
fd00 Linux RAID
Hex code or GUID (L to show codes, Enter = 8300): ef01
Changed type of partition to 'MBR partition scheme'
Command (? for help): ?
b back up GPT data to a file
c change a partition's name
d delete a partition
i show detailed information on a partition
l list known partition types
n add a new partition
o create a new empty GUID partition table (GPT)
p print the partition table
q quit without saving changes
r recovery and transformation options (experts only)
s sort partitions
t change a partition's type code
v verify disk
w write table to disk and exit
x extra functionality (experts only)
? print this menu
Command (? for help): w
Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!
Do you want to proceed? (Y/N): Y
OK; writing new GUID partition table (GPT) to /dev/sdc.
Unable to save backup partition table! Perhaps the 'e' option on the experts'
menu will resolve this problem.
Warning! An error was reported when writing the partition table! This error
MIGHT be harmless, or the disk might be damaged! Checking it is advisable.
Command (? for help): o
This option deletes all partitions and creates a new protective MBR.
Proceed? (Y/N): Y
Command (? for help): p
Disk /dev/sdc: 5860533168 sectors, 2.7 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 3995C753-D73D-4386-8818-3A9AF06E3B2C
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 5860533134
Partitions will be aligned on 2048-sector boundaries
Total free space is 5860533101 sectors (2.7 TiB)
Number Start (sector) End (sector) Size Code Name
Command (? for help): o
This option deletes all partitions and creates a new protective MBR.
Proceed? (Y/N): Y
Command (? for help): w
Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!
Do you want to proceed? (Y/N): Y
OK; writing new GUID partition table (GPT) to /dev/sdc.
Unable to save backup partition table! Perhaps the 'e' option on the experts'
menu will resolve this problem.
Warning! An error was reported when writing the partition table! This error
MIGHT be harmless, or the disk might be damaged! Checking it is advisable.
Command (? for help): p
Disk /dev/sdc: 5860533168 sectors, 2.7 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): F1AE4B7D-9CCE-4211-BE3D-88DFFCCD3696
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 5860533134
Partitions will be aligned on 2048-sector boundaries
Total free space is 5860533101 sectors (2.7 TiB)
Number Start (sector) End (sector) Size Code Name
Command (? for help): o
This option deletes all partitions and creates a new protective MBR.
Proceed? (Y/N): n
Command (? for help): ?
b back up GPT data to a file
c change a partition's name
d delete a partition
i show detailed information on a partition
l list known partition types
n add a new partition
o create a new empty GUID partition table (GPT)
p print the partition table
q quit without saving changes
r recovery and transformation options (experts only)
s sort partitions
t change a partition's type code
v verify disk
w write table to disk and exit
x extra functionality (experts only)
? print this menu
Command (? for help): d
No partitions
Command (? for help): i
No partitions
Command (? for help): r
Recovery/transformation command (? for help): ?
b use backup GPT header (rebuilding main)
c load backup partition table from disk (rebuilding main)
d use main GPT header (rebuilding backup)
e load main partition table from disk (rebuilding backup)
f load MBR and build fresh GPT from it
g convert GPT into MBR and exit
h make hybrid MBR
i show detailed information on a partition
l load partition data from a backup file
m return to main menu
o print protective MBR data
p print the partition table
q quit without saving changes
t transform BSD disklabel partition
v verify disk
w write table to disk and exit
x extra functionality (experts only)
? print this menu
Recovery/transformation command (? for help): f
Warning! This will destroy the currently defined partitions! Proceed? (Y/N): Y
Problem loading MBR! GPT is untouched; regenerating protective MBR!
Recovery/transformation command (? for help): ?
b use backup GPT header (rebuilding main)
c load backup partition table from disk (rebuilding main)
d use main GPT header (rebuilding backup)
e load main partition table from disk (rebuilding backup)
f load MBR and build fresh GPT from it
g convert GPT into MBR and exit
h make hybrid MBR
i show detailed information on a partition
l load partition data from a backup file
m return to main menu
o print protective MBR data
p print the partition table
q quit without saving changes
t transform BSD disklabel partition
v verify disk
w write table to disk and exit
x extra functionality (experts only)
? print this menu
Recovery/transformation command (? for help): v
No problems found. 5860533101 free sectors (2.7 TiB) available in 1
segments, the largest of which is 5860533101 (2.7 TiB) in size.
Recovery/transformation command (? for help): b
Recovery/transformation command (? for help): c
Warning! This will probably do weird things if you've converted an MBR to
GPT form and haven't yet saved the GPT! Proceed? (Y/N): Y
Warning! Read error 5! Misbehavior now likely!
Caution! After loading partitions, the CRC doesn't check out!
Recovery/transformation command (? for help): w
Warning! Main partition table overlaps the first partition by 34 blocks!
You will need to delete this partition or resize it in another utility.
Aborting write of new partition table.
No importa lo que intente hacer, parece que aparece el error de entrada/salida, intenté instalar ubuntu en él y parece crear la tabla de particiones, pero cuando inicio la instalación... error de entrada/salida.
¿Alguien tiene alguna idea de cómo puedo solucionar este problema? Estaré feliz de publicar más archivos de registro o lo que sea, pero no tengo experiencia con Linux, solo lo uso para este tipo de cosas. El disco es muy nuevo, solo tiene algunos meses, así que dudo que se trate de sectores defectuosos.
¡Gracias por todos los aportes!
Respuesta1
Hay sectores defectuosos al principio del disco, donde debería ubicarse la tabla de particiones. Y parece que su intento de reasignarlos no tuvo éxito.
Normalmente reasigno los sectores defectuosos conMHDD; Es una utilidad gratuita que se ejecuta en DOS, por lo que puede omitir la caché del sistema operativo y trabajar directamente con el controlador de disco. Verifique los datos de monitoreo SMART para asegurarse de que no haya sectores defectuosos no reasignados; si hay alguno, ejecute MHDD nuevamente hasta que no haya ninguno.
Después de reasignar todos los sectores defectuosos, intente reparticionar su disco duro en Linux. Agregar el primer megabyte con ceros puede ser útil si los restos de la tabla de particiones anterior confunden su fdisk.
Otra posible causa de sus problemas podría ser un cable de datos defectuoso o una fuente de alimentación demasiado débil; pero deshazte primero de los sectores defectuosos.
También existen los softbads: sectores defectuosos que se producen como resultado de una escritura interrumpida (debido a una pérdida accidental de energía o a una potencia insuficiente en el suministro de energía); Por lo general, se reparan mediante el hardware del disco sin reasignarlos si ese sector en particular se reescribe muchas veces (como lo hace MHDD).
Respuesta2
Mikhail tiene la respuesta a tu problema más o menos en la bolsa, pero le falta un punto clave.
Si es posible, cuando corte la energía, podría estropear el MBR, que al igual que la tabla de particiones se encuentra al principio del disco, pero si está dañado de alguna manera, deberá reescribir manualmente los 512 bytes del MBR o intentar hacerlo. use la reparación de MBR para solucionar el problema, como verá, los últimos 72 bytes del MBR son donde se encuentra la tabla de particiones.
Hablo por experiencia, como lo admito, hice lo mismo que tú y me tomó muchísimo tiempo descubrir exactamente qué había hecho y cómo solucionarlo, la mayoría de los problemas como este generalmente simplemente se descartan. falla de hardware porque la mayoría no quiere tomar el trabajo solo para guardar un disco duro.