Linux за българи: Форуми

От какво може да се получава този еррор
това е през ден (вече почва да ме е яд че съм на първия етаж)
14 харда са на пц-то

Примерен код

root@slackware:/mnt/hd/hd10# dmesg hdi: dma_timer_expiry: dma status == 0x61 hdi: 252 bytes in FIFO hdi: timeout waiting for DMA hdi: error waiting for DMA hdi: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest } hdi: status timeout: status=0xd0 { Busy } hdj: DMA disabled hdi: drive not ready for command ide4: reset: success blk: queue c03b8070, I/O limit 4095Mb (mask 0xffffffff) hdi: dma_timer_expiry: dma status == 0x21 hdi: 252 bytes in FIFO hdi: timeout waiting for DMA hdi: error waiting for DMA hdi: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest } hdi: status timeout: status=0xd0 { Busy } hdi: drive not ready for command ide4: reset: success hdi: dma_timer_expiry: dma status == 0x21 hdi: 252 bytes in FIFO hdi: timeout waiting for DMA hdi: error waiting for DMA hdi: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest } hdi: status timeout: status=0xd0 { Busy } hdi: drive not ready for command ide4: reset: success hdi: dma_timer_expiry: dma status == 0x21 hdi: 252 bytes in FIFO hdi: timeout waiting for DMA hdi: error waiting for DMA hdi: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest } hdi: status timeout: status=0xd0 { Busy } hdi: drive not ready for command ide4: reset: success root@slackware:/mnt/hd/hd10# ps x   PID TTY      STAT   TIME COMMAND     1 ?        S      0:04 init [3]     2 ?        S      0:00 [keventd]     3 ?        SN     0:02 [ksoftirqd_CPU0]     4 ?        S      0:25 [kswapd]     5 ?        S      0:00 [bdflush]     6 ?        S      0:23 [kupdated]     7 ?        S      0:00 [scsi_eh_0]     8 ?        S      0:00 [scsi_eh_1]     9 ?        S<     0:00 [mdrecoveryd]    10 ?        S      0:00 [kreiserfsd]    35 ?        S      0:00 [kapmd]    70 ?        Ss     0:00 /usr/sbin/syslogd    73 ?        Ss     0:00 /usr/sbin/klogd -c 3 -x   135 ?        Ss     0:00 /sbin/dhcpcd -d -t 60 eth2   207 ?        Ss     0:00 /usr/sbin/rpc.statd   209 ?        S      0:08 [rpciod]   630 ?        Ss     0:00 /usr/sbin/inetd   634 ?        Ss     0:00 /usr/sbin/sshd   638 ?        Ss     0:00 /usr/sbin/named   653 ?        Ss     0:00 /usr/sbin/cupsd   700 ?        S      0:02 /usr/sbin/crond -l10   705 ?        Ss     0:00 sendmail: accepting connections   711 ?        Ss     0:00 /usr/sbin/apmd   766 ?        Ss     0:00 /usr/sbin/gpm -m /dev/mouse -t ps2   870 ?        S      0:00 /usr/local/programs/upsmon/upsmon /dev/ttyS0 1200 120   890 ?        Ss     0:00 /usr/bin/perl /etc/webmin-1.250/miniserv.pl /etc/webmin/miniserv.conf   899 ?        S      0:01 /usr/local/programs/net-snmp/sbin/snmpd -c /usr/local/programs/net-snmp/etc/snmpd.conf   927 ?        Ss     0:12 /usr/bin/perl -w /usr/local/programs/mrtg-2/bin/mrtg /usr/local/programs/mrtg-2/etc/mrtg.cfg   944 ?        Ss     0:09 /usr/bin/perl -w /usr/local/programs/mrtg-2/bin/mrtg /usr/local/programs/mrtg-2/etc/cpu.cfg   961 ?        Ss     0:25 /usr/bin/perl -w /usr/local/programs/mrtg-2/bin/mrtg /usr/local/programs/mrtg-2/etc/server-info.cfg  1018 ?        Ss     0:03 /usr/bin/perl -w /usr/local/programs/mrtg-2/bin/mrtg /usr/local/programs/mrtg-2/etc/mysql.cfg  1087 ?        Ss     0:00 /usr/sbin/dhcpd  1109 ?        Ss     0:00 /usr/local/programs/pptpd/sbin/pptpd  1204 ?        S      0:00 pptp: call manager for 10.10.0.1  1256 pts/0    Ss+    0:00 /usr/sbin/pppd /dev/pts/0 38400 call optisprint  1277 ?        S      0:00 /usr/bin/bash /usr/local/programs/verlihub/bin/vh_restart /usr/local/programs/verlihub/bin/verlihub  1279 ?        S      0:03 /usr/local/programs/verlihub/bin/verlihub  1290 ?        Ss     0:31 pptp: GRE-to-PPP gateway on (null)  1309 tty1     Ss+    0:00 -bash  1311 tty3     Ss+    0:00 /sbin/agetty 38400 tty3 linux  1312 tty4     Ss+    0:00 /sbin/agetty 38400 tty4 linux  1313 tty5     Ss+    0:00 /sbin/agetty 38400 tty5 linux  1314 tty6     Ss+    0:00 /sbin/agetty 38400 tty6 linux  2790 tty2     Ss+    0:00 /sbin/agetty 38400 tty2 linux 15702 ?        S      0:00 BitchX 127.0.0.1 server1 12558 ?        Ss     0:00 /usr/local/programs/squid/sbin/squid -sY -f /usr/local/programs/squid/etc/squid.conf 27969 ?        Ss     0:00 /usr/sbin/smbd -D 27971 ?        Ss     0:01 /usr/sbin/nmbd -D 27972 ?        S      0:00 /usr/sbin/smbd -D 32604 ?        S      0:05 /usr/sbin/smbd -D   917 ?        S      0:00 /usr/sbin/smbd -D  6176 ?        S      0:00 /usr/sbin/smbd -D 23330 ?        S      0:00 /usr/sbin/smbd -D 10320 ?        S      0:00 /usr/sbin/smbd -D 17586 ?        S      0:00 /usr/sbin/smbd -D 12907 ?        S      0:54 /usr/sbin/smbd -D 12908 ?        S      0:00 /usr/sbin/smbd -D 30377 ?        S      0:00 /usr/sbin/smbd -D 31209 ?        Ss     0:03 sshd: root@pts/1 31361 pts/1    Ss     0:00 -bash 20669 ?        Ss     0:00 /sbin/mount.smbfs //badmad/dvd /mnt/hd/hd29 -o rw username guest password 21971 pts/1    R+     0:00 ps x root@slackware:/mnt/hd/hd10# hdparm -d 0 /dev/hdj /dev/hdj:  setting using_dma to 0 (off)  using_dma    =  0 (off) root@slackware:/mnt/hd/hd10# dmesg hdi: dma_timer_expiry: dma status == 0x61 hdi: 252 bytes in FIFO hdi: timeout waiting for DMA hdi: error waiting for DMA hdi: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest } hdi: status timeout: status=0xd0 { Busy } hdj: DMA disabled hdi: drive not ready for command ide4: reset: success blk: queue c03b8070, I/O limit 4095Mb (mask 0xffffffff) hdi: dma_timer_expiry: dma status == 0x21 hdi: 252 bytes in FIFO hdi: timeout waiting for DMA hdi: error waiting for DMA hdi: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest } hdi: status timeout: status=0xd0 { Busy } hdi: drive not ready for command ide4: reset: success hdi: dma_timer_expiry: dma status == 0x21 hdi: 252 bytes in FIFO hdi: timeout waiting for DMA hdi: error waiting for DMA hdi: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest } hdi: status timeout: status=0xd0 { Busy } hdi: drive not ready for command ide4: reset: success hdi: dma_timer_expiry: dma status == 0x21 hdi: 252 bytes in FIFO hdi: timeout waiting for DMA hdi: error waiting for DMA hdi: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest } hdi: status timeout: status=0xd0 { Busy } hdi: drive not ready for command ide4: reset: success blk: queue c03b81ac, I/O limit 4095Mb (mask 0xffffffff) hdj: DMA disabled root@slackware:/mnt/hd/hd10# ls mp3_old_collection/  mp3albums_part1/  music/ root@slackware:/mnt/hd/hd10# dmesg hdi: dma_timer_expiry: dma status == 0x61 hdi: 252 bytes in FIFO hdi: timeout waiting for DMA hdi: error waiting for DMA hdi: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest } hdi: status timeout: status=0xd0 { Busy } hdj: DMA disabled hdi: drive not ready for command ide4: reset: success blk: queue c03b8070, I/O limit 4095Mb (mask 0xffffffff) hdi: dma_timer_expiry: dma status == 0x21 hdi: 252 bytes in FIFO hdi: timeout waiting for DMA hdi: error waiting for DMA hdi: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest } hdi: status timeout: status=0xd0 { Busy } hdi: drive not ready for command ide4: reset: success hdi: dma_timer_expiry: dma status == 0x21 hdi: 252 bytes in FIFO hdi: timeout waiting for DMA hdi: error waiting for DMA hdi: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest } hdi: status timeout: status=0xd0 { Busy } hdi: drive not ready for command ide4: reset: success hdi: dma_timer_expiry: dma status == 0x21 hdi: 252 bytes in FIFO hdi: timeout waiting for DMA hdi: error waiting for DMA hdi: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest } hdi: status timeout: status=0xd0 { Busy } hdi: drive not ready for command ide4: reset: success blk: queue c03b81ac, I/O limit 4095Mb (mask 0xffffffff) hdj: DMA disabled root@slackware:/mnt/hd/hd10# dmesg hdi: dma_timer_expiry: dma status == 0x61 hdi: 252 bytes in FIFO hdi: timeout waiting for DMA hdi: error waiting for DMA hdi: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest } hdi: status timeout: status=0xd0 { Busy } hdj: DMA disabled hdi: drive not ready for command ide4: reset: success blk: queue c03b8070, I/O limit 4095Mb (mask 0xffffffff) hdi: dma_timer_expiry: dma status == 0x21 hdi: 252 bytes in FIFO hdi: timeout waiting for DMA hdi: error waiting for DMA hdi: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest } hdi: status timeout: status=0xd0 { Busy } hdi: drive not ready for command ide4: reset: success hdi: dma_timer_expiry: dma status == 0x21 hdi: 252 bytes in FIFO hdi: timeout waiting for DMA hdi: error waiting for DMA hdi: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest } hdi: status timeout: status=0xd0 { Busy } hdi: drive not ready for command ide4: reset: success hdi: dma_timer_expiry: dma status == 0x21 hdi: 252 bytes in FIFO hdi: timeout waiting for DMA hdi: error waiting for DMA hdi: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest } hdi: status timeout: status=0xd0 { Busy } hdi: drive not ready for command ide4: reset: success blk: queue c03b81ac, I/O limit 4095Mb (mask 0xffffffff) hdj: DMA disabled

това е dmesg от зареждането на пц-то

Примерен код

NFORCE2-U400R: 00:09.0 (rev a3) UDMA133 controller     ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA     ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA HPT370: IDE controller at PCI slot 01:09.0 HPT370: chipset revision 3 HPT370: not 100% native mode: will probe irqs later HPT37X: using 33MHz PCI clock     ide2: BM-DMA at 0xd700-0xd707, BIOS settings: hde:DMA, hdf:DMA     ide3: BM-DMA at 0xd708-0xd70f, BIOS settings: hdg:DMA, hdh:DMA HPT370: IDE controller at PCI slot 01:0b.0 HPT370: chipset revision 3 HPT370: not 100% native mode: will probe irqs later HPT37X: using 33MHz PCI clock     ide4: BM-DMA at 0xdc00-0xdc07, BIOS settings: hdi:pio, hdj:pio     ide5: BM-DMA at 0xdc08-0xdc0f, BIOS settings: hdk:pio, hdl:pio hda: WDC WD2500JB-00EVA0, ATA DISK drive hdb: Maxtor 7Y250P0, ATA DISK drive blk: queue c03b6f20, I/O limit 4095Mb (mask 0xffffffff) blk: queue c03b705c, I/O limit 4095Mb (mask 0xffffffff) hdc: ST3250823A, ATA DISK drive hdd: HDS722525VLAT80, ATA DISK drive blk: queue c03b7374, I/O limit 4095Mb (mask 0xffffffff) blk: queue c03b74b0, I/O limit 4095Mb (mask 0xffffffff) hde: ST3250823A, ATA DISK drive hdf: ST3250823A, ATA DISK drive blk: queue c03b77c8, I/O limit 4095Mb (mask 0xffffffff) blk: queue c03b7904, I/O limit 4095Mb (mask 0xffffffff) hdg: ST3120026A, ATA DISK drive hdh: ST3160023A, ATA DISK drive blk: queue c03b7c1c, I/O limit 4095Mb (mask 0xffffffff) blk: queue c03b7d58, I/O limit 4095Mb (mask 0xffffffff) hdi: IC35L120AVVA07-0, ATA DISK drive hdj: WDC WD1200BB-00CAA1, ATA DISK drive blk: queue c03b8070, I/O limit 4095Mb (mask 0xffffffff) blk: queue c03b81ac, I/O limit 4095Mb (mask 0xffffffff) hdk: IC35L120AVV207-1, ATA DISK drive hdl: WDC WD1200PB-00FBA0, ATA DISK drive blk: queue c03b84c4, I/O limit 4095Mb (mask 0xffffffff) blk: queue c03b8600, I/O limit 4095Mb (mask 0xffffffff) ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide1 at 0x170-0x177,0x376 on irq 15 ide2 at 0xd300-0xd307,0xd402 on irq 7 ide3 at 0xd500-0xd507,0xd602 on irq 7 ide4 at 0xd800-0xd807,0xd902 on irq 5 ide5 at 0xda00-0xda07,0xdb02 on irq 5 hda: attached ide-disk driver. hda: host protected area => 1 hda: 488397168 sectors (250059 MB) w/8192KiB Cache, CHS=30401/255/63, UDMA(100) hdb: attached ide-disk driver. hdb: host protected area => 1 hdb: setmax_ext LBA 490234752, native  490232639 hdb: 490232639 sectors (250999 MB) w/7936KiB Cache, CHS=30515/255/63, UDMA(133) hdc: attached ide-disk driver. hdc: host protected area => 1 hdc: 488397168 sectors (250059 MB) w/8192KiB Cache, CHS=30401/255/63, UDMA(100) hdd: attached ide-disk driver. hdd: host protected area => 1 hdd: 488397168 sectors (250059 MB) w/7938KiB Cache, CHS=30401/255/63, UDMA(100) hde: attached ide-disk driver. hde: host protected area => 1 hde: 488397168 sectors (250059 MB) w/8192KiB Cache, CHS=30401/255/63, UDMA(100) hdf: attached ide-disk driver. hdf: host protected area => 1 hdf: 488397168 sectors (250059 MB) w/8192KiB Cache, CHS=30401/255/63, UDMA(100) hdg: attached ide-disk driver. hdg: host protected area => 1 hdg: 234441648 sectors (120034 MB) w/8192KiB Cache, CHS=14593/255/63, UDMA(100) hdh: attached ide-disk driver. hdh: host protected area => 1 hdh: 312581808 sectors (160042 MB) w/8192KiB Cache, CHS=19457/255/63, UDMA(100) hdi: attached ide-disk driver. hdi: host protected area => 1 hdi: 241254720 sectors (123522 MB) w/1863KiB Cache, CHS=239340/16/63, UDMA(100) hdj: attached ide-disk driver. hdj: host protected area => 1 hdj: 234441648 sectors (120034 MB) w/2048KiB Cache, CHS=232581/16/63, UDMA(100) hdk: attached ide-disk driver. hdk: host protected area => 1 hdk: 241254720 sectors (123522 MB) w/7965KiB Cache, CHS=15017/255/63, UDMA(100) hdl: attached ide-disk driver. hdl: host protected area => 1 hdl: 234441648 sectors (120034 MB) w/8192KiB Cache, CHS=14593/255/63, UDMA(100) Partition check:  hda: hda1 hda2 hda3  hdb: hdb1  hdc: hdc1  hdd: hdd1  hde: hde1  hdf: hdf1  hdg: hdg1  hdh: hdh1  hdi: [PTBL] [15017/255/63] hdi1  hdj: [PTBL] [14593/255/63] hdj1  hdk: hdk1  hdl: hdl1 SCSI subsystem driver Revision: 1.00 libata version 1.11 loaded. sata_nv version 0.6 PCI: Setting latency timer of device 00:0b.0 to 64 ata1: SATA max UDMA/133 cmd 0x9F0 ctl 0xBF2 bmdma 0xE900 irq 11 ata2: SATA max UDMA/133 cmd 0x970 ctl 0xB72 bmdma 0xE908 irq 11 ata1: dev 0 cfg 49:2f00 82:346b 83:7d01 84:4003 85:3469 86:3c01 87:4003 88:407f ata1: dev 0 ATA, max UDMA/133, 390721968 sectors: lba48 ata1: dev 0 configured for UDMA/133 ata2: dev 0 cfg 49:2f00 82:346b 83:7d01 84:4003 85:3469 86:3c01 87:4003 88:407f ata2: dev 0 ATA, max UDMA/133, 390721968 sectors: lba48 ata2: dev 0 configured for UDMA/133 scsi0 : sata_nv scsi1 : sata_nv   Vendor: ATA       Model: ST3200822AS       Rev: 3.01   Type:   Direct-Access                      ANSI SCSI revision: 05   Vendor: ATA       Model: ST3200822AS       Rev: 3.01   Type:   Direct-Access                      ANSI SCSI revision: 05 Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0 SCSI device sda: 390721968 512-byte hdwr sectors (200050 MB)  sda: sda1 sda2 sda3 SCSI device sdb: 390721968 512-byte hdwr sectors (200050 MB)  sdb: sdb1

Здравей. Няма да те зарадва това което ще ти кажа. Имах същия проблем с ST3160023A (Сигеийт 160 гб)... Та след окололо седмица-две след като се появи тоя пролем харда спря да работи. Дано да имаш гаранция.

сатата работи без грешка
още един еррор от една друга машина
hdd: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hdd: drive_cmd: error=0x04 { DriveStatusError }
къса ми са сърцето като знам че всичко съм купувал с пари от моя джоб
сложих едно сисинфо http://www.bulclima.net за да се види горе долу какъв хардуер има на пц-то
ако случайно някой може да помогне ще съм адски благодарен

може да пробваш да прегледаш файловата система за грешки с fsck,но появят ли се такива грешки ,както хората ти казват по-горе , това означава че скоро ще ти се наложи да смениш този хдд.

Затова прави backup и сменяй докато работи !

Успех.

благодаря за отговорите
на няколко пъти се скапва харда
форматирам и работи временно
явно ще се наложи да сменя всички който
бъкат еррори за по сигурно

Проблема е в самите IBM хардове. Серийте DLTA и IC35 си имат идиотски бъг във fimware. IBM даже изкараха препоръка че тия дискове не трябвало да работят повече от 8 часа на ден. Писанията по разни форуми че тия хардове в idle не паркирали главите и при над 8 часа работа главите опирали в плочите са пълна глупост.

Проблема им е следния: в резултат от бъг във самия firmware се случва при писане на сектор да не се изключват записващите глави навреме. И при seek с работещи в режим запис глави харда просто забърсва областите над които минава. Ако се случи над област с данни обикновенно не се усеща, защото се повреждат по няколко бита на сектор и в последствие при четене се кориригат с допълителната информация записана към всеки сектор. Обаче ако ако главите минат над сервизната информация в началото на сектора, той просто изчезва. И вместо смислено съобщение 'sector not found' харда връща цитираните грешки.

Физически харда не е повреден и затова след low level формат с ibm-ското drive fitness tool се оправя 100%, като съответно се губи всичко от него. Кога ще се скапе пак е въпрос на късмет.

Имам към 10 харда ibm IC35060AVV-1. Всичките са low level форматирани и нямат лоши сектори. Oбаче толкова често са правили този номер че вече седят само в шкафа и се ползват за тестове на операционни системи или временно запазване на изключително маловажна информация.

Всъщност в един от линковете които дадох имаше препратка към firmware за тия хардове, който ужким решавал проблема като след минимално време неактивност паркирал главите. Ефективноста е съмнителна според мене, но нищо не пречи да се опита.