I've posted the message below to linux-kernel, but there were no replies. Does anyone here have any suggestions?
I am building a file server with 5 drive software RAID5 array. I am using three IWill SIDE-100 (Highpoint 370A) controllers as my IDE interfaces, not using their RAID functionality. One Maxtor 160GB drive per channel, two channels per controller. I plan on adding hot spare as the sixth drive in the future. There's one 160GB partition on each drive. Linux version 2.4.19-pre7smp-020502b (root@production) (gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-98)) #6 SMP Thu May 2 12:15:34 CDT 2002
This is a dual Athlon 2000+ MP on Tyan Tiger S2466N-4 with 1GB RAM. OS and swap runs on separate drives and controllers. This array will be just for data once it is configured.
Below are the most relevant parts of my logs. I will post further details if anyone is willing to help, just let me know what info you need. Any suggestions greatly appreciated.
Artur
After issuing mkraid the system went to syncing RAID and following appeared in my syslog:
May 7 17:34:39 production kernel: RAID5 conf printout:
May 7 17:34:39 production kernel: --- rd:5 wd:5 fd:0
May 7 17:34:39 production kernel: disk 0, s:0, o:1, n:0 rd:0 us:1 dev:hde1
May 7 17:34:39 production kernel: disk 1, s:0, o:1, n:1 rd:1 us:1 dev:hdg1
May 7 17:34:39 production kernel: disk 2, s:0, o:1, n:2 rd:2 us:1 dev:hdi1
May 7 17:34:39 production kernel: disk 3, s:0, o:1, n:3 rd:3 us:1 dev:hdk1
May 7 17:34:39 production kernel: disk 4, s:0, o:1, n:4 rd:4 us:1 dev:hdm1
May 7 17:34:39 production kernel: md: updating md3 RAID superblock on device
May 7 17:34:39 production kernel: md: hdm1 [events: 00000001]<6>(write) hdm1's sb offset: 160079552
May 7 17:34:39 production kernel: md: syncing RAID array md3
May 7 17:34:39 production kernel: md: minimum _guaranteed_ reconstruction speed: 100 KB/sec/disc.
May 7 17:34:39 production kernel: md: using maximum available idle IO bandwith (but not more than 100000 KB/sec) for reconstruction.
May 7 17:34:39 production kernel: md: using 124k window, over a total of 160079488 blocks.
May 7 17:34:39 production kernel: md: hdk1 [events: 00000001]<6>(write) hdk1's sb offset: 160079552
May 7 17:34:39 production kernel: hde: 0 bytes in FIFO
May 7 17:34:39 production kernel: ide_dmaproc: chipset supported ide_dma_timeout func only: 14
May 7 17:34:39 production kernel: hde: dma_intr: bad DMA status (dma_stat=1)
May 7 17:34:39 production kernel: hde: dma_intr: status=0x50 { DriveReady SeekComplete }
May 7 17:34:39 production kernel: hdi: 4 bytes in FIFO
May 7 17:34:39 production kernel: ide_dmaproc: chipset supported ide_dma_timeout func only: 14
May 7 17:34:39 production kernel: hdi: dma_intr: bad DMA status (dma_stat=1)
May 7 17:34:39 production kernel: hdi: dma_intr: status=0x50 { DriveReady SeekComplete }
May 7 17:34:39 production kernel: hdi: 192 bytes in FIFO
May 7 17:34:39 production kernel: ide_dmaproc: chipset supported ide_dma_timeout func only: 14
May 7 17:34:39 production kernel: hdi: dma_intr: bad DMA status (dma_stat=1)
May 7 17:34:39 production kernel: hdi: dma_intr: status=0x50 { DriveReady SeekComplete }
May 7 17:34:39 production kernel: md: hdi1 [events: 00000001]<6>(write) hdi1's sb offset: 160079552
May 7 17:34:39 production kernel: hdi: 128 bytes in FIFO
May 7 17:34:39 production kernel: ide_dmaproc: chipset supported ide_dma_timeout func only: 14
May 7 17:34:39 production kernel: hdi: dma_intr: bad DMA status (dma_stat=1)
May 7 17:34:39 production kernel: hdi: dma_intr: status=0x50 { DriveReady SeekComplete }
May 7 17:34:39 production kernel: hdk: 128 bytes in FIFO
[...snip...]
May 7 17:34:41 production kernel: hdk: 64 bytes in FIFO
May 7 17:34:41 production kernel: ide_dmaproc: chipset supported ide_dma_timeout func only: 14
May 7 17:34:41 production kernel: hdk: dma_intr: bad DMA status (dma_stat=1)
May 7 17:34:41 production kernel: hdk: dma_intr: status=0x50 { DriveReady SeekComplete }
May 7 17:34:41 production kernel: hdk: recal_intr: status=0xd0 { Busy }
May 7 17:34:41 production kernel: hdk: DMA disabled
May 7 17:34:41 production kernel: ide5: reset: success
May 7 17:34:50 production kernel: hdi: timeout waiting for DMA
May 7 17:34:50 production kernel: hdi: 12 bytes in FIFO
May 7 17:34:50 production kernel: ide_dmaproc: chipset supported ide_dma_timeout func only: 14
May 7 17:34:50 production kernel: hdi: status error: status=0x58 { DriveReady SeekComplete DataRequest }
May 7 17:34:50 production kernel: hdi: drive not ready for command
Simillar messages were reported for /dev/hdm, hdi, hde, hdk
I've mdstopped the process and disbled DMA for all RAID members with hdparm -d 0. Tried mdrun again and got following messages:
May 7 18:43:26 production kernel: hdi: status error: status=0x58 { DriveReady SeekComplete DataRequest }
May 7 18:43:26 production kernel: hdi: drive not ready for command
May 7 18:44:40 production kernel: hdi: status error: status=0x58 { DriveReady SeekComplete DataRequest }
May 7 18:44:40 production kernel: hdi: drive not ready for command
May 7 18:44:52 production kernel: hdi: status error: status=0x58 { DriveReady SeekComplete DataRequest }
May 7 18:44:52 production kernel: hdi: drive not ready for command
May 7 18:46:45 production kernel: hdi: status error: status=0x58 { DriveReady SeekComplete DataRequest }
May 7 18:46:45 production kernel: hdi: drive not ready for command
May 7 18:47:11 production kernel: hdi: status error: status=0x58 { DriveReady SeekComplete DataRequest }
May 7 18:47:11 production kernel: hdi: drive not ready for command
May 7 18:47:32 production kernel: hdi: status error: status=0x58 { DriveReady SeekComplete DataRequest }
May 7 18:47:32 production kernel: hdi: drive not ready for command
May 7 18:47:57 production kernel: hdi: status error: status=0x58 { DriveReady SeekComplete DataRequest }
May 7 18:47:57 production kernel: hdi: drive not ready for command
May 7 18:48:09 production kernel: hdi: status error: status=0x58 { DriveReady SeekComplete DataRequest }
May 7 18:48:09 production kernel: hdi: drive not ready for command
May 7 18:48:18 production kernel: hdk: write_intr error1: nr_sectors=128, stat=0xd0
May 7 18:48:18 production kernel: hdk: write_intr: status=0xd0 { Busy }
May 7 18:48:18 production kernel: ide5: reset: success
May 7 18:48:27 production kernel: hdi: status error: status=0x58 { DriveReady SeekComplete DataRequest }
May 7 18:48:27 production kernel: hdi: drive not ready for command
May 7 18:48:27 production kernel: hdi: status timeout: status=0xd0 { Busy }
May 7 18:48:27 production kernel: hdi: drive not ready for command
May 7 18:48:28 production kernel: ide4: reset: success
May 7 18:48:43 production kernel: raid5: parity resync was not fully finished, restarting next time.
May 7 18:48:43 production kernel: md: md_do_sync() got signal ... exiting
May 7 18:48:44 production kernel: raid5: resync aborted!
:.˛mkabzwmb˛mb)w* jg ݢjG j:+vwjm wfh٥
