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!

Ogłoszenie

Prosimy o pomoc dla małej Julki — przekaż 1% podatku na Fundacji Dzieciom zdazyć z Pomocą.
Więcej informacji na dug.net.pl/pomagamy/.

Strony: 1

 

#1  2007-04-05 15:57:56

  GuruPL - Członek DUG

GuruPL
Członek DUG
Zarejestrowany: 2006-03-13
Serwis

problem z DMA@MSI-6712 Ver-1.1 [SOLVED]

od ponad 6 miechow moj serverek smigal jak mazenie
mialem podpiete
1x 80GB - hda1-SWAP(512); hda2-Debian 3.1 (20GB) + hda3
2x 250 GB WD
1x 320 GB Seagate
1x 200 GB WD
wszystkie dyski podpiete pod ide
80 pod ide na plycie
reszta na Promise Fasttrak 100TX2
kernel mam wlasny z patchem 2.4.34-ps24


wszystkie dyski smigaja na DMA i maja ustawione Standby na 10 min (przez hdparm'a), dyski WD maja rowniez ustawione Acoustic Management na "quiet"

i tak sobie wszystko ladnie smigalo

niedawno kupilem nowe 2 dyski dla serverka
1x Seagate 320GB IDE
1x Seagate 500GB IDE

odkod podpiolem nowe dyski mam ciagle problemy z DMA. po ok 30min dostaje

Kod:

hda Interupt lost

po analizie logow wykrylem ze problemy zaczynaja sie podczas ladowania modulu apm.o, system  nie mogl go znalesc a potem juz tylko interupt lost.
wiec dodalem do mojego jajka apm.o, ale system dalej pada :(


teraz mam podpiete
PM 80GB
PS 500GB
SM 250 GB
SS 250 GB

KERN.LOG

Kod:


Apr  5 14:13:55 localhost kernel: ip_tables: (C) 2000-2002 Netfilter core team
Apr  5 14:13:55 localhost kernel: ip_conntrack version 2.1 (4095 buckets, 32760 max) - 328 bytes per conntrack
Apr  5 14:13:55 localhost kernel: IPP2P v0.8.2 loading
--          -- IPP2P laduje sie automatycznie przy bootowaniu podczas 
--          -- ladowania mojego skryptu dla firewall'a
Apr  5 14:15:12 localhost kernel: eth1: Promiscuous mode enabled.
Apr  5 14:15:12 localhost kernel: device eth1 entered promiscuous mode
Apr  5 14:15:15 localhost kernel: apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16)
Apr  5 14:15:15 localhost kernel: apm: overridden by ACPI.
Apr  5 14:49:18 localhost kernel: hdc: dma_timer_expiry: dma status == 0x60
Apr  5 14:49:18 localhost kernel: hdc: timeout waiting for DMA
Apr  5 14:49:18 localhost kernel: hdc: timeout waiting for DMA
Apr  5 14:49:18 localhost kernel: hdc: (__ide_dma_test_irq) called while not waiting
Apr  5 14:49:18 localhost kernel: hdd: status timeout: status=0xd0 { Busy }
Apr  5 14:49:18 localhost kernel: 
Apr  5 14:49:18 localhost kernel: hdd: drive not ready for command
Apr  5 14:49:23 localhost kernel: hdc: status timeout: status=0xd0 { Busy }
Apr  5 14:49:23 localhost kernel: 
Apr  5 14:49:23 localhost kernel: hdd: DMA disabled
Apr  5 14:49:23 localhost kernel: hdc: drive not ready for command
Apr  5 14:49:30 localhost kernel: ide1: reset: master: error (0x00?)
Apr  5 14:55:14 localhost kernel: hdd: irq timeout: status=0xd0 { Busy }
Apr  5 14:55:14 localhost kernel: 
Apr  5 14:55:14 localhost kernel: hdd: status timeout: status=0xd0 { Busy }
Apr  5 14:55:14 localhost kernel: 
Apr  5 14:55:14 localhost kernel: hdd: drive not ready for command
Apr  5 14:56:13 localhost kernel: hdd: status timeout: status=0xd0 { Busy }
Apr  5 14:56:13 localhost kernel: 
Apr  5 14:56:13 localhost kernel: hdc: DMA disabled
Apr  5 14:56:13 localhost kernel: hdd: drive not ready for command
Apr  5 14:56:13 localhost kernel: ide1: reset: success
Apr  5 15:12:16 localhost kernel: eth1: Promiscuous mode enabled.
Apr  5 15:12:16 localhost kernel: eth0: link down
Apr  5 15:12:16 localhost kernel: eth1: link down
Apr  5 15:12:16 localhost kernel: eth1: Promiscuous mode enabled.
Apr  5 15:12:16 localhost last message repeated 4 times
Apr  5 15:12:16 localhost kernel: eth2: Setting full-duplex based on MII #1 link partner capability of 45e1.
Apr  5 15:18:47 localhost kernel: klogd 1.4.1#17, log source = /proc/kmsg started.

SYSLOG

Kod:

Apr  5 14:49:18 localhost kernel: hdc: dma_timer_expiry: dma status == 0x60
Apr  5 14:49:18 localhost kernel: hdc: timeout waiting for DMA
Apr  5 14:49:18 localhost kernel: hdc: timeout waiting for DMA
Apr  5 14:49:18 localhost kernel: hdc: (__ide_dma_test_irq) called while not waiting
Apr  5 14:49:18 localhost kernel: hdd: status timeout: status=0xd0 { Busy }
Apr  5 14:49:18 localhost kernel: 
Apr  5 14:49:18 localhost kernel: hdd: drive not ready for command
Apr  5 14:49:23 localhost kernel: hdc: status timeout: status=0xd0 { Busy }
Apr  5 14:49:23 localhost kernel: 
Apr  5 14:49:23 localhost kernel: hdd: DMA disabled
Apr  5 14:49:23 localhost kernel: hdc: drive not ready for command
Apr  5 14:49:30 localhost kernel: ide1: reset: master: error (0x00?)
Apr  5 14:50:01 localhost /USR/SBIN/CRON[1452]: (root) CMD (if [ -x /usr/bin/vnstat ] && [ `ls /var/lib/vnstat/ | wc -l` -ge 1 ]; then /usr/bin/vnstat -u; fi)
Apr  5 14:50:01 localhost /USR/SBIN/CRON[1453]: (root) CMD (if [ -x /usr/bin/mrtg ] && [ -r /etc/mrtg.cfg ]; then env LANG=C /usr/bin/mrtg /etc/mrtg.cfg >> /var/log/mrtg/mrtg.log 2>&1; fi)
Apr  5 14:55:01 localhost /USR/SBIN/CRON[1471]: (root) CMD (if [ -x /usr/bin/vnstat ] && [ `ls /var/lib/vnstat/ | wc -l` -ge 1 ]; then /usr/bin/vnstat -u; fi)
Apr  5 14:55:01 localhost /USR/SBIN/CRON[1472]: (root) CMD (if [ -x /usr/bin/mrtg ] && [ -r /etc/mrtg.cfg ]; then env LANG=C /usr/bin/mrtg /etc/mrtg.cfg >> /var/log/mrtg/mrtg.log 2>&1; fi)
Apr  5 14:55:14 localhost kernel: hdd: irq timeout: status=0xd0 { Busy }
Apr  5 14:55:14 localhost kernel: 
Apr  5 14:55:14 localhost kernel: hdd: status timeout: status=0xd0 { Busy }
Apr  5 14:55:14 localhost kernel: 
Apr  5 14:55:14 localhost kernel: hdd: drive not ready for command
Apr  5 14:56:13 localhost kernel: hdd: status timeout: status=0xd0 { Busy }
Apr  5 14:56:13 localhost kernel: 
Apr  5 14:56:13 localhost kernel: hdc: DMA disabled
Apr  5 14:56:13 localhost kernel: hdd: drive not ready for command
Apr  5 14:56:13 localhost kernel: ide1: reset: success
Apr  5 15:00:01 localhost /USR/SBIN/CRON[1489]: (root) CMD (if [ -x /usr/bin/vnstat ] && [ `ls /var/lib/vnstat/ | wc -l` -ge 1 ]; then /usr/bin/vnstat -u; fi)
Apr  5 15:00:01 localhost /USR/SBIN/CRON[1490]: (root) CMD (if [ -x /usr/bin/mrtg ] && [ -r /etc/mrtg.cfg ]; then env LANG=C /usr/bin/mrtg /etc/mrtg.cfg >> /var/log/mrtg/mrtg.log 2>&1; fi)
Apr  5 15:05:01 localhost /USR/SBIN/CRON[1503]: (root) CMD (if [ -x /usr/bin/vnstat ] && [ `ls /var/lib/vnstat/ | wc -l` -ge 1 ]; then /usr/bin/vnstat -u; fi)
Apr  5 15:05:01 localhost /USR/SBIN/CRON[1504]: (root) CMD (if [ -x /usr/bin/mrtg ] && [ -r /etc/mrtg.cfg ]; then env LANG=C /usr/bin/mrtg /etc/mrtg.cfg >> /var/log/mrtg/mrtg.log 2>&1; fi)
Apr  5 15:09:01 localhost /USR/SBIN/CRON[1511]: (root) CMD (  [ -d /var/lib/php4 ] && find /var/lib/php4/ -type f -cmin +$(/usr/lib/php4/maxlifetime) -print0 | xargs -r -0 rm)
Apr  5 15:10:01 localhost /USR/SBIN/CRON[1520]: (root) CMD (if [ -x /usr/bin/vnstat ] && [ `ls /var/lib/vnstat/ | wc -l` -ge 1 ]; then /usr/bin/vnstat -u; fi)
Apr  5 15:10:01 localhost /USR/SBIN/CRON[1522]: (root) CMD (if [ -x /usr/bin/mrtg ] && [ -r /etc/mrtg.cfg ]; then env LANG=C /usr/bin/mrtg /etc/mrtg.cfg >> /var/log/mrtg/mrtg.log 2>&1; fi)
Apr  5 15:12:16 localhost dhcpd: receive_packet failed on eth0: Network is down
Apr  5 15:12:16 localhost kernel: eth1: Promiscuous mode enabled.
Apr  5 15:12:16 localhost dhcpd: receive_packet failed on eth1: Network is down
Apr  5 15:12:16 localhost kernel: eth0: link down
Apr  5 15:12:16 localhost kernel: eth1: link down
Apr  5 15:12:16 localhost kernel: eth1: Promiscuous mode enabled.

Offline

 

#2  2007-04-06 14:15:21

  GuruPL - Członek DUG

GuruPL
Członek DUG
Zarejestrowany: 2006-03-13
Serwis

Re: problem z DMA@MSI-6712 Ver-1.1 [SOLVED]

hmm

moze cuda sie zdazaja, moze nie.

ja informatykiem jestem i w prawa murphy'ego wierze. ale coz mam czynic gdy DMA zaczyna dzialac :)

nic tylko sie cieszyc :).

moje problemy zaczely sie gdy dostalem nowe dyski od SEAGATE'a, wtedy wlasnie skorzystalem z okazji ze server poszedl offline i wymontowalem 2 dyski WD 250GB i podpiolem je pod winde i przy pomocy "winaam" aktywowalem i wyedytowalem AAM dla tych dyskow. ustawilem je wtedy na 128 - lub 'quiet'
i to byl chyba moj blad.
zdesperowany, metoda prob i bledow probowalem wszelkich kombinacji WD na plyte SEAGATE na Promisa itp itd. az wreszcie siadlem i zamiast walczyc z objawami skoncentrowalem sie na przyczynach.
podpiolem WD 250 tki pod winde i wylaczylem aam. podpiolem na serverek

Plyta
PM WD 80
PS WD 200
SM WD 250
SS WD 250

Promise
PM ---------
PS SEAGATE 500
SM SEAGATE 350
SS SEAGATE 350

i dziala.
dyski ida po 10min do standby a jak wywolam je po sambie to smigaja
na WD mam po hdparm -t 55MB a SEAGATY daja ladne 75MB

WNIOSKI:
1. AAM jest niebezpieczne !
2. lepiej SEAGATY i WD na oddzielnych kontrolerach trzymac :)

Offline

 

 

Strony: 1

Stopka forum

Powered by PunBB
© Copyright 2002–2005 Rickard Andersson
Możesz wyłączyć AdBlock — tu nie ma reklam ;-)

[ Generated in 0.007 seconds, 11 queries executed ]

Informacje debugowania

Time (s) Query
0.00007 SET CHARSET latin2
0.00004 SET NAMES latin2
0.00074 SELECT u.*, g.*, o.logged FROM punbb_users AS u INNER JOIN punbb_groups AS g ON u.group_id=g.g_id LEFT JOIN punbb_online AS o ON o.ident='3.145.62.46' WHERE u.id=1
0.00054 REPLACE INTO punbb_online (user_id, ident, logged) VALUES(1, '3.145.62.46', 1738411153)
0.00049 SELECT * FROM punbb_online WHERE logged<1738410853
0.00045 SELECT topic_id FROM punbb_posts WHERE id=56837
0.00067 SELECT id FROM punbb_posts WHERE topic_id=7465 ORDER BY posted
0.00055 SELECT t.subject, t.closed, t.num_replies, t.sticky, f.id AS forum_id, f.forum_name, f.moderators, fp.post_replies, 0 FROM punbb_topics AS t INNER JOIN punbb_forums AS f ON f.id=t.forum_id LEFT JOIN punbb_forum_perms AS fp ON (fp.forum_id=f.id AND fp.group_id=3) WHERE (fp.read_forum IS NULL OR fp.read_forum=1) AND t.id=7465 AND t.moved_to IS NULL
0.00007 SELECT search_for, replace_with FROM punbb_censoring
0.00093 SELECT u.email, u.title, u.url, u.location, u.use_avatar, u.signature, u.email_setting, u.num_posts, u.registered, u.admin_note, p.id, p.poster AS username, p.poster_id, p.poster_ip, p.poster_email, p.message, p.hide_smilies, p.posted, p.edited, p.edited_by, g.g_id, g.g_user_title, o.user_id AS is_online FROM punbb_posts AS p INNER JOIN punbb_users AS u ON u.id=p.poster_id INNER JOIN punbb_groups AS g ON g.g_id=u.group_id LEFT JOIN punbb_online AS o ON (o.user_id=u.id AND o.user_id!=1 AND o.idle=0) WHERE p.topic_id=7465 ORDER BY p.id LIMIT 0,25
0.00087 UPDATE punbb_topics SET num_views=num_views+1 WHERE id=7465
Total query time: 0.00542 s