salve a tutti
vengo subito al dunque ho comprato un hard disk maxtor 320 GB tutto per fedora 11 vado per installare la nuova versione sull’hard disk ( accoppiato con quello vecchio su cui ho installato fedora 10) e tutto procede regolarmente al primo avvio funziona aggiorno il sistema e lo riavvio per ben due volte .poi improvvisamente compare un errore e all’avvio mi da il kernel panic !
leggendo tra le cose che mi sono saltate subito all’occhio era questa stringa
:…Write Protect is off
…doesn’t support dpo or fua
scusatemi se è davvero poco ma essendo un problema all’avvio non so come postare il risultato; Condiretato che sto scrivendo dall’altro hard disk
credo di aver fatto tutto correttamente ho pure abilitato AHCI dal bios e non è cambiato niente
grazie mille
cordiali saluti
Romeo
- cosa significa ?:
vogliamo scrivere con cura, per cortesia ?
- posta attraverso il sistema residente sul disco funzionante:
# fdisk -lScusatemi ma andavo di fretta…
volevo scrivere "considerato che sto scrivendo dall’altro hard disk "
ecco questo è il risultato
fdisk -l
Disco /dev/sda: 320.0 GB, 320072933376 byte
255 testine, 63 settori/tracce, 38913 cilindri
Unità = cilindri di 16065 * 512 = 8225280 byte
Identificativo disco: 0x000878c9
Dispositivo Boot Start End Blocks Id System
/dev/sda1 * 1 64 512000 83 Linux
La partizione 1 non termina al limite del cilindro.
/dev/sda2 64 574 4096000 83 Linux
La partizione 2 non termina al limite del cilindro.
/dev/sda3 574 37544 296960000 8e Linux LVM
Disco /dev/sdb: 41.1 GB, 41110142976 byte
255 testine, 63 settori/tracce, 4998 cilindri
Unità = cilindri di 16065 * 512 = 8225280 byte
Identificativo disco: 0xb198b198
Dispositivo Boot Start End Blocks Id System
/dev/sdb1 * 1 25 200781 83 Linux
/dev/sdb2 26 4998 39945622+ 8e Linux LVM
ecco l’output di dmesg riguardo il nuovo hard disk
ahci 0000:00:11.0: version 3.0
ahci 0000:00:11.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
ahci 0000:00:11.0: AHCI 0001.0100 32 slots 6 ports 3 Gbps 0x3f impl SATA mode
ahci 0000:00:11.0: flags: 64bit ncq sntf ilck pm led clo pmp pio slum part
scsi0 : ahci
scsi1 : ahci
scsi2 : ahci
scsi3 : ahci
scsi4 : ahci
scsi5 : ahci
ata1: SATA max UDMA/133 abar m1024@0xfbbff800 port 0xfbbff900 irq 22
ata2: SATA max UDMA/133 abar m1024@0xfbbff800 port 0xfbbff980 irq 22
ata3: SATA max UDMA/133 abar m1024@0xfbbff800 port 0xfbbffa00 irq 22
ata4: SATA max UDMA/133 abar m1024@0xfbbff800 port 0xfbbffa80 irq 22
ata5: SATA max UDMA/133 abar m1024@0xfbbff800 port 0xfbbffb00 irq 22
ata6: SATA max UDMA/133 abar m1024@0xfbbff800 port 0xfbbffb80 irq 22
ata1: softreset failed (device not ready)
ata1: failed due to HW bug, retry pmp=0
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: ATA-8: MAXTOR STM3320613AS, MC1H, max UDMA/133
ata1.00: 625142448 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata1.00: configured for UDMA/133
ata2: SATA link down (SStatus 0 SControl 300)
ata3: SATA link down (SStatus 0 SControl 300)
ata4: SATA link down (SStatus 0 SControl 300)
ata5: SATA link down (SStatus 0 SControl 300)
ata6: SATA link down (SStatus 0 SControl 300)
scsi 0:0:0:0: Direct-Access ATA MAXTOR STM332061 MC1H PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 625142448 512-byte hardware sectors (320073 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn’t support DPO or FUA
sd 0:0:0:0: [sda] 625142448 512-byte hardware sectors (320073 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn’t support DPO or FUA
sda: sda1 sda2 sda3
sd 0:0:0:0: [sda] Attached SCSI disk
sd 0:0:0:0: Attached scsi generic sg0 type 0
scusate se insisto ma ho avuto diversi problemi e credo che la causa sia l’hard disk !
anzitutto all’avvio il bios non mi riconosce sempre l’hard disk certe volte è come se non fosse collegato e le poche volte che lo riconosce mi dava questo errore :
S.M.A.R.T CAPABLE AND STATUS BAD
ho aggiornato il bios all’ultima versione e non è cambiato niente .l’hard disk è nuovo non ha neanke una settimana ovviamente in garanzia.
vi posto qui l’output di smartctl:
[code]# smartctl -a /dev/sda
smartctl version 5.38 [x86_64-redhat-linux-gnu] Copyright © 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF INFORMATION SECTION ===
Device Model: MAXTOR STM3320613AS
Serial Number: 9SZ2QAVS
Firmware Version: MC1H
User Capacity: 320,072,933,376 bytes
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 4
Local Time is: Sat Jun 13 10:42:20 2009 CEST
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: FAILED!
Drive failure expected in less than 24 hours. SAVE ALL DATA.
See vendor-specific Attribute list for failed Attributes.
General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
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: ( 625) 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: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 70) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x103f) SCT Status supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 090 085 006 Pre-fail Always - 55474193
3 Spin_Up_Time 0x0003 100 100 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 41
5 Reallocated_Sector_Ct 0x0033 001 001 036 Pre-fail Always FAILING_NOW 4084
7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 189250
9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 25
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 41
184 Unknown_Attribute 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 207
188 Unknown_Attribute 0x0032 100 097 000 Old_age Always - 12885164050
189 High_Fly_Writes 0x003a 095 095 000 Old_age Always - 5
190 Airflow_Temperature_Cel 0x0022 071 060 045 Old_age Always - 29 (Lifetime Min/Max 27/29)
194 Temperature_Celsius 0x0022 029 040 000 Old_age Always - 29 (0 26 0 0)
195 Hardware_ECC_Recovered 0x001a 040 033 000 Old_age Always - 55474193
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 11
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 11
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 231004816015385
241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 1301308703
242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 1116912055
SMART Error Log Version: 1
ATA Error Count: 310 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It “wraps” after 49.710 days.
Error 310 occurred at disk power-on lifetime: 22 hours (0 days + 22 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
04 71 04 9d 00 32 e0 Device Fault; Error: ABRT
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
a1 00 00 00 00 00 a0 00 00:33:50.760 IDENTIFY PACKET DEVICE
ec 00 00 00 00 00 a0 00 00:33:50.760 IDENTIFY DEVICE
ff 00 00 00 00 00 00 00 00:33:50.608 [VENDOR SPECIFIC]
00 00 00 00 00 00 00 04 00:33:50.608 NOP [Abort queued commands]
ff 00 00 00 00 00 00 00 00:33:50.455 [VENDOR SPECIFIC]
Error 309 occurred at disk power-on lifetime: 22 hours (0 days + 22 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
04 71 04 9d 00 32 e0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
ec 00 00 00 00 00 a0 00 00:33:50.760 IDENTIFY DEVICE
ff 00 00 00 00 00 00 00 00:33:50.608 [VENDOR SPECIFIC]
00 00 00 00 00 00 00 04 00:33:50.608 NOP [Abort queued commands]
ff 00 00 00 00 00 00 00 00:33:50.455 [VENDOR SPECIFIC]
00 00 00 00 00 00 00 04 00:33:50.455 NOP [Abort queued commands]
Error 308 occurred at disk power-on lifetime: 22 hours (0 days + 22 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
04 71 04 9d 00 32 e0 Device Fault; Error: ABRT
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
a1 00 04 9d 00 32 a0 00 00:33:40.971 IDENTIFY PACKET DEVICE
ec 00 01 01 00 00 a0 00 00:33:40.443 IDENTIFY DEVICE
ff 00 00 00 00 00 00 00 00:33:39.858 [VENDOR SPECIFIC]
00 00 00 00 00 00 00 04 00:33:39.858 NOP [Abort queued commands]
ff 00 00 00 00 00 00 00 00:33:36.727 [VENDOR SPECIFIC]
Error 307 occurred at disk power-on lifetime: 22 hours (0 days + 22 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
04 71 04 9d 00 32 e0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
ec 00 01 01 00 00 a0 00 00:33:40.443 IDENTIFY DEVICE
ff 00 00 00 00 00 00 00 00:33:39.858 [VENDOR SPECIFIC]
00 00 00 00 00 00 00 04 00:33:39.858 NOP [Abort queued commands]
ff 00 00 00 00 00 00 00 00:33:36.727 [VENDOR SPECIFIC]
00 00 00 00 00 00 00 ff 00:33:36.727 NOP [Abort queued commands]
Error 306 occurred at disk power-on lifetime: 22 hours (0 days + 22 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
04 71 04 9d 00 32 e0 Device Fault; Error: ABRT
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
a1 00 04 9d 00 32 a0 00 00:32:53.704 IDENTIFY PACKET DEVICE
ec 00 01 01 00 00 a0 00 00:32:53.176 IDENTIFY DEVICE
ff 00 00 00 00 00 00 00 00:32:52.592 [VENDOR SPECIFIC]
00 00 00 00 00 00 00 04 00:32:52.592 NOP [Abort queued commands]
ff 00 00 00 00 00 00 00 00:32:49.460 [VENDOR SPECIFIC]
SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]
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.
[/code]
credete vada sostituito ?qual è il problema ?
grazie per l’aiuto e scusatemi per il risultato assai lungo
Ciao, guarda caso l’altro giorno sono entrato nel negozio di informatica sotto casa per fare vari acquisti, il gestore era molto irritato in quanto ha dovuto mandare indietro molti “stack” di hard disk MAXTOR appena arrivati in quanto molti clienti che hanno acquistato hard disk MAXTOR di elevata capienza gli hanno restituito l’hard disk lamentandosi che non funziona, appunto non sempre viene rilevato, smette di girare durante l’esecuzione del sistema operativo (e questo è molto grave) e si sente proprio l’hard disk che stacca, etc…
Appena ha finito di speigare al cliente con l’hard disk in mano la situazione, ne è entrato un altro con un hd MAXTOR in mano…
Quindi è evidente che hli gd MAXTOR di questo periodo hanno problemi, io ho 4 hd MAXTOR ma li ho acquistati circa 3 anni fa e funzionano tutti.
Secondo me devi riportarlo indietro, magari fanno un controllo dove lo hai acquistato
Ciao
grazie per la risposta ho chiamato il negozio e lunedi porterò l’hard disk per farlo controllare . Io ho gia provato sia con smartools che con l’utility fornita dalla stessa casa seagate ( che ha assorbito la maxtor) per quello specifico hard disk: risultati? il test breve lo ha passato mentre il test lungo si è bloccato al primo settore con risultato ovviamente negativo !spero solo che non mi facciano problemi ! vi infermerò al più presto anche sull’installazione di fedora 11! infatti sarà forse stata colpa dell’hard disk ma ho tentato qualche 6 volte l’installazione e si bloccava sempre in qualche punto ! 2 volte riuscita e 2 volte dopo qualche avvio nessun segno di vita .
grazie mille lo stesso
Una buona marca di hardisk in questo periodo è samsung