Newsgroup: it.comp.hardware
Titolo: Sata

Salve,
ho intenzione di utilizzare un vecchio Poweredge 1800
come nas.
Il server monta attualmente due HD scsi 320 da 67GB in raid.
Visto che ha anche due porte sata sulla scheda madre ho provato a 
montare un HD sata con esito positivo.
1.Quanti HD posso collegare ad ogni porta sata??
2.Quali caratteristiche devono avere gli HD che acquistero'
3.Consigli vari ed eventuali
Grazie 1k

 3.Consigli vari ed eventuali
 
Io aggiungerei altri scsi ma sono un "aficionado" :-)
Bye


Uhm...dipende :)


Io pure, ma il mio budget e' limitato.
Corro a comprare sto sata da 1 Tera :D
grazie 1k


????

Il 11/06/11, Diego x80 ha detto :

Volendo esistono i cosiddetti Port Multiplier i quali ti permettono di 
collegare più HD SA ad una stessa porta SA presente sulla MB...

 grazie 1k
 
Utima cosa, okkio alla dimensione dei settori
il vecchio sistema era a 256 ora ci sono anche i 4096
ma xp nativamente non li vede correttamente e anche installando
l'apposita utility di emulazione e' comunque lento
(ad esempio il WD10EARS western digital e' un tera con settori 4096)
Quindi meglio il classico 256.
Da win7 in poi invece no problem.
Bye

 collegare più HD SA ad una stessa porta SA presente sulla MB...
Ottimo..
Grazie


Grzie, spero che con freenas e linux 2.6.35 non abbia problemi visto che 
ho comprato proprio un WD.
Per win no problem..non lo uso :D
Ciao e grazie ancora


Ho comprato il SATA.. SATA3
inizialmente andava bene (primi 50 GB) poi freenas ha cominciato a fare 
i capricci. Ora riavviando il server, il sistema (BIOS??) mi avverte che 
il disco lavora in una modalita' non standard e mi chiede se voglio 
continuare. Ricordo che il server e' un vecchio Poweredge 1800 e il 
disco sata e' un WD da un tera.
E' possibile continuare ad utilizzare il disco su questa macchina?
Ciao diego

 Ciao diego
Sembrerebbe un bug di BSD..
ora, dopo aver settato il jumper per forzare a sata2, sto andando di 
debian; comunque che il BIOS mi continui a bloccare l'avvio con quel 
warning non mi convince tanto.
Saluti diego

Dopo dura riflessione, Diego x80 ha scritto :

Secondo me il messaggio in questione non pregiudica il corretto 
funzionamento dell'HD.


CVD
[ 1863.904187] kjournald starting.  Commit interval 5 seconds
[ 1863.904634] EXT3 FS on sdb1, internal journal
[ 1863.904642] EXT3-fs: mounted filesystem with ordered data mode.
[ 2361.848181] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 2361.848252] ata3.00: BMDMA stat 0x4
[ 2361.848309] ata3.00: failed command: READ DMA EXT
[ 2361.848372] ata3.00: cmd 25/00:08:df:b0:34/00:00:3a:00:00/e0 tag 0 
dma 4096 in
[ 2361.848374]          res 51/40:00:df:b0:34/40:00:3a:00:00/e0 Emask 
0x9 (media error)
[ 2361.848556] ata3.00: status: { DRDY ERR }
[ 2361.848617] ata3.00: error: { UNC }
[ 2361.873766] ata3.00: configured for UDMA/133
[ 2361.873777] ata3: EH complete
[ 2363.606050] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 2363.606116] ata3.00: BMDMA stat 0x4
[ 2363.606172] ata3.00: failed command: READ DMA EXT
[ 2363.606234] ata3.00: cmd 25/00:08:df:b0:34/00:00:3a:00:00/e0 tag 0 
dma 4096 in
[ 2363.606236]          res 51/40:00:df:b0:34/40:00:3a:00:00/e0 Emask 
0x9 (media error)
[ 2363.606377] ata3.00: status: { DRDY ERR }
[ 2363.606433] ata3.00: error: { UNC }
[ 2363.628434] ata3.00: configured for UDMA/133
[ 2363.628445] ata3: EH complete
[ 2365.347904] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 2365.347965] ata3.00: BMDMA stat 0x4
[ 2365.348026] ata3.00: failed command: READ DMA EXT
[ 2365.348088] ata3.00: cmd 25/00:08:df:b0:34/00:00:3a:00:00/e0 tag 0 
dma 4096 in
[ 2365.348089]          res 51/40:00:df:b0:34/40:00:3a:00:00/e0 Emask 
0x9 (media error)
[ 2365.348231] ata3.00: status: { DRDY ERR }
[ 2365.348286] ata3.00: error: { UNC }
[ 2365.368437] ata3.00: configured for UDMA/133
[ 2365.368447] ata3: EH complete
[ 2367.097779] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 2367.097846] ata3.00: BMDMA stat 0x4
[ 2367.097902] ata3.00: failed command: READ DMA EXT
[ 2367.097964] ata3.00: cmd 25/00:08:df:b0:34/00:00:3a:00:00/e0 tag 0 
dma 4096 in
[ 2367.097966]          res 51/40:00:df:b0:34/40:00:3a:00:00/e0 Emask 
0x9 (media error)
[ 2367.098106] ata3.00: status: { DRDY ERR }
[ 2367.098162] ata3.00: error: { UNC }
[ 2367.120430] ata3.00: configured for UDMA/133
[ 2367.120441] ata3: EH complete
[ 2368.839637] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 2368.839699] ata3.00: BMDMA stat 0x4
[ 2368.839759] ata3.00: failed command: READ DMA EXT
[ 2368.839821] ata3.00: cmd 25/00:08:df:b0:34/00:00:3a:00:00/e0 tag 0 
dma 4096 in
[ 2368.839822]          res 51/40:00:df:b0:34/40:00:3a:00:00/e0 Emask 
0x9 (media error)
[ 2368.839963] ata3.00: status: { DRDY ERR }
[ 2368.840018] ata3.00: error: { UNC }
[ 2368.860428] ata3.00: configured for UDMA/133
[ 2368.860438] ata3: EH complete
[ 2370.589514] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 2370.589575] ata3.00: BMDMA stat 0x4
[ 2370.589636] ata3.00: failed command: READ DMA EXT
[ 2370.589697] ata3.00: cmd 25/00:08:df:b0:34/00:00:3a:00:00/e0 tag 0 
dma 4096 in
[ 2370.589699]          res 51/40:00:df:b0:34/40:00:3a:00:00/e0 Emask 
0x9 (media error)
[ 2370.589839] ata3.00: status: { DRDY ERR }
[ 2370.589894] ata3.00: error: { UNC }
[ 2370.612426] ata3.00: configured for UDMA/133
[ 2370.612437] sd 2:0:0:0: [sdb] Unhandled sense code
[ 2370.612441] sd 2:0:0:0: [sdb] Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
[ 2370.612446] sd 2:0:0:0: [sdb] Sense Key : Medium Error [current] 
[descriptor]
[ 2370.612453] Descriptor sense data with sense descriptors (in hex):
[ 2370.612456]         72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 2370.612470]         3a 34 b0 df
[ 2370.612476] sd 2:0:0:0: [sdb] Add. Sense: Unrecovered read error - 
auto reallocate failed
[ 2370.612484] sd 2:0:0:0: [sdb] CDB: Read(10): 28 00 3a 34 b0 df 00 00 
08 00
[ 2370.612501] end_request: I/O error, dev sdb, sector 976531679
[ 2370.612585] ata3: EH complete
[ 2370.612625] journal_bmap: journal block not found at offset 5132 on sdb1
[ 2370.612689] Aborting journal on device sdb1.
[ 2370.617176] __journal_remove_journal_head: freeing b_committed_data
[ 2370.660029] ext3_abort called.
[ 2370.660100] EXT3-fs error (device sdb1): ext3_journal_start_sb: 
Detected aborted journal
[ 2370.660287] Remounting filesystem read-only
[ 2371.271331] __journal_remove_journal_head: freeing b_committed_data
[ 2372.066551] __journal_remove_journal_head: freeing b_committed_data
[ 2372.066594] __journal_remove_journal_head: freeing b_frozen_data
[ 2372.066597] __journal_remove_journal_head: freeing b_committed_data
[ 2372.066600] __journal_remove_journal_head: freeing b_frozen_data
[ 2978.975831] __journal_remove_journal_head: freeing b_frozen_data
[ 2978.975842] __journal_remove_journal_head: freeing b_frozen_data
[ 2978.975851] __journal_remove_journal_head: freeing b_frozen_data
[ 2978.975868] ext3_abort called.
[ 2978.975927] EXT3-fs error (device sdb1): ext3_put_super: Couldn't 
clean up the journal
[ 3018.510976] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 3018.511045] ata3.00: BMDMA stat 0x5
[ 3018.511102] ata3.00: failed command: READ DMA EXT
[ 3018.511164] ata3.00: cmd 25/00:00:7f:89:34/00:01:3a:00:00/e0 tag 0 
dma 131072 in
[ 3018.511166]          res 51/40:1f:5d:8a:34/40:00:3a:00:00/e0 Emask 
0x9 (media error)
[ 3018.511307] ata3.00: status: { DRDY ERR }
[ 3018.511363] ata3.00: error: { UNC }
[ 3018.524893] ata3.00: configured for UDMA/133
[ 3018.524905] ata3: EH complete
[ 3024.051918] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 3024.051985] ata3.00: BMDMA stat 0x4
[ 3024.052041] ata3.00: failed command: READ DMA EXT
[ 3024.052104] ata3.00: cmd 25/00:08:df:b0:34/00:00:3a:00:00/e0 tag 0 
dma 4096 in
[ 3024.052105]          res 51/40:00:df:b0:34/40:00:3a:00:00/e0 Emask 
0x9 (media error)
[ 3024.052247] ata3.00: status: { DRDY ERR }
[ 3024.052302] ata3.00: error: { UNC }
[ 3024.080846] ata3.00: configured for UDMA/133
[ 3024.080857] ata3: EH complete
[ 3025.793779] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 3025.793841] ata3.00: BMDMA stat 0x4
[ 3025.793902] ata3.00: failed command: READ DMA EXT
[ 3025.793964] ata3.00: cmd 25/00:08:df:b0:34/00:00:3a:00:00/e0 tag 0 
dma 4096 in
[ 3025.793965]          res 51/40:00:df:b0:34/40:00:3a:00:00/e0 Emask 
0x9 (media error)
[ 3025.794106] ata3.00: status: { DRDY ERR }
[ 3025.794162] ata3.00: error: { UNC }
[ 3025.816691] ata3.00: configured for UDMA/133
[ 3025.816701] ata3: EH complete
[ 3027.527631] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 3027.527693] ata3.00: BMDMA stat 0x4
[ 3027.527753] ata3.00: failed command: READ DMA EXT
[ 3027.527815] ata3.00: cmd 25/00:08:df:b0:34/00:00:3a:00:00/e0 tag 0 
dma 4096 in
[ 3027.527817]          res 51/40:00:df:b0:34/40:00:3a:00:00/e0 Emask 
0x9 (media error)
[ 3027.527958] ata3.00: status: { DRDY ERR }
[ 3027.528013] ata3.00: error: { UNC }
[ 3027.548542] ata3.00: configured for UDMA/133
[ 3027.548552] ata3: EH complete
[ 3029.260484] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 3029.260564] ata3.00: BMDMA stat 0x4
[ 3029.260624] ata3.00: failed command: READ DMA EXT
[ 3029.260694] ata3.00: cmd 25/00:08:df:b0:34/00:00:3a:00:00/e0 tag 0 
dma 4096 in
[ 3029.260697]          res 51/40:00:df:b0:34/40:00:3a:00:00/e0 Emask 
0x9 (media error)
[ 3029.260843] ata3.00: status: { DRDY ERR }
[ 3029.260901] ata3.00: error: { UNC }
[ 3029.284424] ata3.00: configured for UDMA/133
[ 3029.284434] ata3: EH complete
[ 3030.994348] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 3030.994415] ata3.00: BMDMA stat 0x4
[ 3030.994471] ata3.00: failed command: READ DMA EXT
[ 3030.994533] ata3.00: cmd 25/00:08:df:b0:34/00:00:3a:00:00/e0 tag 0 
dma 4096 in
[ 3030.994534]          res 51/40:00:df:b0:34/40:00:3a:00:00/e0 Emask 
0x9 (media error)
[ 3030.994675] ata3.00: status: { DRDY ERR }
[ 3030.994730] ata3.00: error: { UNC }
[ 3031.017259] ata3.00: configured for UDMA/133
[ 3031.017270] ata3: EH complete
[ 3032.727192] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 3032.727258] ata3.00: BMDMA stat 0x4
[ 3032.727314] ata3.00: failed command: READ DMA EXT
[ 3032.727376] ata3.00: cmd 25/00:08:df:b0:34/00:00:3a:00:00/e0 tag 0 
dma 4096 in
[ 3032.727378]          res 51/40:00:df:b0:34/40:00:3a:00:00/e0 Emask 
0x9 (media error)
[ 3032.727519] ata3.00: status: { DRDY ERR }
[ 3032.727574] ata3.00: error: { UNC }
[ 3032.749110] ata3.00: configured for UDMA/133
[ 3032.749121] sd 2:0:0:0: [sdb] Unhandled sense code
[ 3032.749125] sd 2:0:0:0: [sdb] Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
[ 3032.749130] sd 2:0:0:0: [sdb] Sense Key : Medium Error [current] 
[descriptor]
[ 3032.749136] Descriptor sense data with sense descriptors (in hex):
[ 3032.749139]         72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3032.749154]         3a 34 b0 df
[ 3032.749164] sd 2:0:0:0: [sdb] Add. Sense: Unrecovered read error - 
auto reallocate failed
[ 3032.749172] sd 2:0:0:0: [sdb] CDB: Read(10): 28 00 3a 34 b0 df 00 00 
08 00
[ 3032.749184] end_request: I/O error, dev sdb, sector 976531679
[ 3032.749255] journal_bmap: journal block not found at offset 5289 on sdb1
[ 3032.749260] ata3: EH complete
[ 3032.749326] JBD: bad block at offset 5289
[ 3032.749389] JBD: recovery failed
[ 3032.749393] EXT3-fs: error loading journal.
il tutto dopo aver tentato di creare un file da 30 GB.
Ora passo a testare l'HD su un pc con MB piu' recente.
Ciao diego


Come immaginavo sul pc piu' recente (supporta sata2),
il problema non si verifica:
ho letto e scritto per piu' di un'ora e mezza.
Purtroppo il disco che ho acquistato (sata3) non e' compatibile con la 
MB sata1.
A presto diego

 MB sata1.
 
Non proprio.... sata3 e' retrocompatibile, probabilmente la colpa
e' del bios della mammaboard ( ci sono aggiornameti? )
Puoi ovviare con un controller sata pci
Bye


Come faccio ad essere sicuro che poi la scheda PCI e' compatibile con la MB?
Scusa ma riguardo all'hardware sono veramente carente..
Ciao diego