Nie jesteś zalogowany.
Jeśli nie posiadasz konta, zarejestruj je już teraz! Pozwoli Ci ono w pełni korzystać z naszego serwisu. Spamerom dziękujemy!
Prosimy o pomoc dla małej Julki — przekaż 1% podatku na Fundacji Dzieciom zdazyć z Pomocą.
Więcej informacji na dug.net.pl/pomagamy/.

Użytkownik


Witam
Kiedys sie z tym meczylem ale jakos przestalo po upgrade jajka. Teraz powrocilo jak bumerang. Nie wiem co jest grane bo podczas odczytu i zapsu jeden dyzk odlacza sie z maciezy i nastepuje degradacja.
jajko 2.6.26-1-686
ata2: exception Emask 0x10 SAct 0x0 SErr 0x1990000 action 0xe frozen
[ 176.922642] ata2: SError: { PHYRdyChg 10B8B Dispar LinkSeq TrStaTrns }
[ 176.922642] ata2: hard resetting link
[ 177.644012] ata2: SATA link down (SStatus 0 SControl 300)
[ 177.644021] ata2: failed to recover some devices, retrying in 5 secs
[ 182.648017] ata2: hard resetting link
[ 182.968011] ata2: SATA link down (SStatus 0 SControl 300)
[ 182.968020] ata2: failed to recover some devices, retrying in 5 secs
[ 187.972019] ata2: hard resetting link
[ 188.292011] ata2: SATA link down (SStatus 0 SControl 300)
[ 188.292020] ata2.00: disabled
[ 188.796011] ata2: EH complete
[ 188.796517] ata2.00: detaching (SCSI 1:0:0:0)
[ 188.797779] sd 1:0:0:0: [sda] Synchronizing SCSI cache
[ 188.797812] sd 1:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
[ 188.797817] sd 1:0:0:0: [sda] Stopping disk
[ 188.797825] sd 1:0:0:0: [sda] START_STOP FAILED
[ 188.797827] sd 1:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
[ 198.800003] ata4: exception Emask 0x10 SAct 0x0 SErr 0x1990000 action 0xe frozen
[ 198.800003] ata4: SError: { PHYRdyChg 10B8B Dispar LinkSeq TrStaTrns }
[ 198.800003] ata4: hard resetting link
[ 200.708016] ata4: SATA link down (SStatus 0 SControl 300)
[ 200.708028] ata4: failed to recover some devices, retrying in 5 secs
[ 205.712032] ata4: hard resetting link
[ 206.032011] ata4: SATA link down (SStatus 0 SControl 300)
[ 206.032020] ata4: failed to recover some devices, retrying in 5 secs
[ 211.036012] ata4: hard resetting link
[ 211.356001] ata4: SATA link down (SStatus 0 SControl 300)
[ 211.356001] ata4.00: disabled
[ 211.860010] ata4: EH complete
[ 211.860286] ata4.00: detaching (SCSI 3:0:0:0)
[ 211.860464] sd 3:0:0:0: [sdc] Synchronizing SCSI cache
[ 211.861372] sd 3:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
[ 211.861379] sd 3:0:0:0: [sdc] Stopping disk
[ 211.861388] sd 3:0:0:0: [sdc] START_STOP FAILED
[ 211.861391] sd 3:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
[ 221.888007] ata2: hard resetting link
[ 222.392021] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 222.416211] ata2.00: ATA-8: SAMSUNG HD501LJ, CR100-12, max UDMA7
[ 222.416216] ata2.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 0/32)
[ 222.424209] ata2.00: configured for UDMA/133
[ 222.424216] ata2: EH complete
[ 222.424307] scsi 1:0:0:0: Direct-Access ATA SAMSUNG HD501LJ CR10 PQ: 0 ANSI: 5
[ 222.424409] sd 1:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB)
[ 222.424423] sd 1:0:0:0: [sdc] Write Protect is off
[ 222.424426] sd 1:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[ 222.424447] sd 1:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 222.424498] sd 1:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB)
[ 222.424510] sd 1:0:0:0: [sdc] Write Protect is off
[ 222.424512] sd 1:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[ 222.424532] sd 1:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 222.424537] sdc: sdc1
[ 222.432808] sd 1:0:0:0: [sdc] Attached SCSI disk
[ 225.459057] ata2: exception Emask 0x10 SAct 0x0 SErr 0x1850000 action 0xe frozen
[ 225.459057] ata2: SError: { PHYRdyChg CommWake LinkSeq TrStaTrns }
[ 225.459057] ata2: hard resetting link
[ 231.220008] ata2: link is slow to respond, please be patient (ready=0)
[ 234.120017] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 234.152210] ata2.00: configured for UDMA/133
[ 234.152216] ata2: EH complete
[ 234.152260] sd 1:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB)
[ 234.152275] sd 1:0:0:0: [sdc] Write Protect is off
[ 234.152278] sd 1:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[ 234.152300] sd 1:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 305.385651] md: md3 stopped.
[ 305.385672] md: unbind<sdb1>
[ 305.385677] md: export_rdev(sdb1)
[ 305.385926] md: unbind<sda1>
[ 305.385932] md: export_rdev(sda1)
[ 305.460937] md: bind<sdc1>
[ 305.461233] md: bind<sdb1>
[ 312.444012] md: kicking non-fresh sdc1 from array!
[ 312.444012] md: unbind<sdc1>
[ 312.444012] md: export_rdev(sdc1)
[ 312.554116] xor: automatically using best checksumming function: pIII_sse
[ 312.572003] pIII_sse : 5720.000 MB/sec
[ 312.572006] xor: using function: pIII_sse (5720.000 MB/sec)
[ 312.588190] async_tx: api initialized (async)
[ 312.680070] raid6: int32x1 724 MB/s
[ 312.748055] raid6: int32x2 793 MB/s
[ 312.816046] raid6: int32x4 654 MB/s
[ 312.884079] raid6: int32x8 370 MB/s
[ 312.952021] raid6: mmxx1 1515 MB/s
[ 313.020005] raid6: mmxx2 2668 MB/s
[ 313.088018] raid6: sse1x1 1283 MB/s
[ 313.156004] raid6: sse1x2 2157 MB/s
[ 313.224013] raid6: sse2x1 2140 MB/s
[ 313.292005] raid6: sse2x2 3031 MB/s
[ 313.292007] raid6: using algorithm sse2x2 (3031 MB/s)
[ 313.292011] md: raid6 personality registered for level 6
[ 313.292013] md: raid5 personality registered for level 5
[ 313.292016] md: raid4 personality registered for level 4
[ 313.293445] raid5: device sdb1 operational as raid disk 0
[ 313.293451] raid5: not enough operational devices for md3 (2/3 failed)
[ 313.293508] RAID5 conf printout:
[ 313.293510] --- rd:3 wd:1
[ 313.293512] disk 0, o:1, dev:sdb1dysk nie ma badow
czy spotkaliscie sie tym juz kiedys ?
jaki kontroler sata znacie ktory ma conajmniej 4 porty i bardzo dobrze sie sprawuje pod debkiem ? cena max 200 zl
Ostatnio edytowany przez ukasz (2009-01-03 17:14:51)

Offline




Moderator Mamut
mialem podobny (taki sam) problem ... czestotliwosc jego pojawiania sie ograniczylo (przynajmniej mialem takie wrazenie) ladne ulozenie tasiemki od dysku ... calkowicie problem rozwiazalo powrocenie do jajka 2.6.24 (wlasnie z 2.6.26 ... podobno to jakis bug w tym jajku)
//Edit:
u mnie problem dotyczyl pojedynczego dysku SATA nie bedacego czescia zadnego raida
Ostatnio edytowany przez bercik (2009-01-04 03:22:24)
Offline

Użytkownik


zmienilem port sata i dziala. nie wiesza sie. nic innego nie robilem.
a znacie jakis dobry kontroler sata ktory by obslugiwal hotpulgowanie dyskow sata ?
Ostatnio edytowany przez ukasz (2009-01-05 13:45:38)

Offline
wlansie mam podobny problem. Tylko nie moge przepiac do innego portu sata bo mam 4 zajete :/ Wymienilem kabel i zobaczmy co dalej.
ukasz znalazles moze jakis kontroler po rozsadnej cenie?
Offline

Użytkownik


tak.
01:04.0 RAID bus controller: Silicon Image, Inc. SiI 3114 [SATALink/SATARaid] Serial ATA Controller (rev 02)
4 portowy. na allegro upilem za jakiej 45 zl.

Offline