January 29, 200719 yr Well there is your problem. Something is amiss. I would check the syslog. Also search the forum. At one point there was a command given that would give the dma status of all the drives. A 'dmesg' command should give you the startup detecting info at least.
January 29, 200719 yr Hi, It sounds like you are experiencing a similar problem as I am. I have been struggling to get a 2-500gb Satas and 1 Pata array up. It took 12 hours to get 20% complete. I removed the Pata and it was only 1.5 hours to complete. I then added the Maxtor Pata back in and the system and it would nearly freeze and loose connection to my PC. I tried all sorts of bios and cable changes, but nothing helped. I pulled a 300gb sata out of another machine and installed it the same slot and it started up in unraid - no problem. It looks as though it is a IDE/MB configuration problem. What MB do you have?
January 29, 200719 yr Author I have the Asus P5LD2. I'm not sure if I should just wait until it's finished or interrupt it. But probably by the time I get home from work today, it should hopefully be done. When I was using the SATA for parity the parity rebuild completed in about 7hrs. Can I look at the syslog or run the command to check the DMA status while the parity is building?
January 30, 200719 yr Author Well 3 days later and parity is still going. The drive was a new unformatted 500GB drive. Here's the result of my drive status. Funny thing is when I go to the devices tab, all my drives are flashing green and the parity is a solid red. Parity states 80% complete. I installed the blue connector on the IDE drive to the MB and set the parity drive as master at the end of the ribbon. The second drive is set as slave and it's on the middle connection. Everything was working at a normal speed until I added the drive. I have a 500w Antec TruePower PS with 5 total drives. I know it's not a power problem because before I installed the new drive I had 5 drives attached. I disabled one whch was the old parity when setting up the new parity. This is really frustrating. Model=ST3500630A, FwRev=3.AAC, SerialNo=3QG04V5R Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% } RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4 BuffType=unknown, BuffSize=16384kB, MaxMultSect=16, MultSect=16 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=268435455 IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120} PIO modes: pio0 pio1 pio2 pio3 pio4 DMA modes: mdma0 mdma1 mdma2 UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5 AdvancedPM=no WriteCache=enabled Drive conforms to: device does not report version: * signifies the current active mode
January 30, 200719 yr Author Well I got up this morning AND....the d*mn thing had restarted building parity again!! It said 0.3% done. 8,600min to go. I stopped the parity and powered down the server for now. I'm not sure what to do. Help!
January 31, 200719 yr Author Well I tried making the parity drive the only drive connected on the cable. Tried it as master as as cable select. Tried a different cable. At no point when rebuilding parity does the speed go above 2,350KB/sec. I even removed some of the drives to see if that helped but it didn't. I guess I'll have to unplug the whole array and only have that drive installed. Then format and copy some files across and see what the syslog says.
January 31, 200719 yr Author Okay I now only have one single drive in my server. I formatted it and copy over some files. Everything seemed to be okay. Here's my syslog. Hopefully Tom can tell me if there's a problem with it. 0.4 Jan 30 08:20:53 Tower kernel: Type: Direct-Access ANSI SCSI revision: 02 Jan 30 08:20:53 Tower kernel: Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0 Jan 30 08:20:53 Tower kernel: SCSI device sda: 1000944 512-byte hdwr sectors (51 2 MB) Jan 30 08:20:53 Tower kernel: sda: Write Protect is off Jan 30 08:20:53 Tower kernel: sda: sda1 Jan 30 08:20:53 Tower kernel: Freeing initrd memory: 25252k freed Jan 30 08:20:53 Tower kernel: VFS: Mounted root (ext2 filesystem) readonly. Jan 30 08:20:53 Tower kernel: Freeing unused kernel memory: 80k freed Jan 30 08:20:53 Tower logger: /etc/rc.d/rc.inet1: /sbin/ifconfig lo 127.0.0.1 Jan 30 08:20:53 Tower logger: /etc/rc.d/rc.inet1: /sbin/route add -net 127.0.0. 0 netmask 255.0.0.0 lo Jan 30 08:20:53 Tower logger: /etc/rc.d/rc.hotplug start (entering script) Jan 30 08:20:54 Tower kernel: eth0: r10001.04, the Linux device driver for Realt ek Ethernet Controllers at 0xc800, 00:15:f2:08:16:4f, IRQ 10 Jan 30 08:20:54 Tower kernel: Realtek RTL8168/8111 Family PCI-E Gigabit Ethernet Network Adapter Jan 30 08:20:54 Tower kernel: Driver version:1.04 Jan 30 08:20:54 Tower kernel: Released date:2006/07/07 Jan 30 08:20:54 Tower kernel: Link Status:Linked Jan 30 08:20:54 Tower kernel: Link Speed:100Mbps Jan 30 08:20:54 Tower kernel: Duplex mode:Full-Duplex Jan 30 08:20:54 Tower kernel: I/O Base:0xC800(I/O port) Jan 30 08:20:54 Tower kernel: IRQ:10 Jan 30 08:20:54 Tower logger: /etc/rc.d/rc.inet1: /sbin/dhcpcd -d -t 60 -h Towe r eth0 Jan 30 08:20:54 Tower kernel: ata1: SATA max UDMA/133 cmd 0xA800 ctl 0xA402 bmdm a 0x9400 irq 10 Jan 30 08:20:54 Tower kernel: ata2: SATA max UDMA/133 cmd 0xA000 ctl 0x9802 bmdm a 0x9408 irq 10 Jan 30 08:20:55 Tower kernel: ATA: abnormal status 0x7F on port 0xA807 Jan 30 08:20:55 Tower kernel: ata1: disabling port Jan 30 08:20:55 Tower kernel: ATA: abnormal status 0x7F on port 0xA007 Jan 30 08:20:55 Tower kernel: ata2: disabling port Jan 30 08:20:55 Tower kernel: scsi1 : ata_piix Jan 30 08:20:55 Tower kernel: scsi2 : ata_piix Jan 30 08:21:12 Tower logger: /etc/rc.d/rc.hotplug start (exiting script) Jan 30 08:21:12 Tower emhttp[886]: UnRaid Management Utility version 3.0 Jan 30 08:21:12 Tower emhttp[886]: Copyright © 2005-2006, Lime Technology, LLC Jan 30 08:21:12 Tower emhttp[886]: shcmd (1): rmmod md-mod >>/var/log/go 2>&1 Jan 30 08:21:12 Tower ifplugd(eth0)[894]: ifplugd 0.28 initializing. Jan 30 08:21:12 Tower ifplugd(eth0)[894]: Using interface eth0/00:15:F2:08:16:4F Jan 30 08:21:12 Tower ifplugd(eth0)[894]: Using detection mode: IFF_RUNNING Jan 30 08:21:12 Tower ifplugd(eth0)[894]: Initialization complete, link beat det ected. Jan 30 08:21:12 Tower emhttp[886]: shcmd (2): modprobe md-mod super=/boot/config /super.dat slots=3,0 >>/var/log/go 2>&1 Jan 30 08:21:12 Tower kernel: md: unraid driver 0.91.0 Jan 30 08:21:12 Tower kernel: md: sizeof(mdp_super_t) = 4096 Jan 30 08:21:12 Tower kernel: md: measuring xor speed Jan 30 08:21:12 Tower kernel: 8regs : 3019.200 MB/sec Jan 30 08:21:12 Tower kernel: 32regs : 1953.200 MB/sec Jan 30 08:21:12 Tower kernel: pIII_sse : 4639.200 MB/sec Jan 30 08:21:12 Tower kernel: pII_mmx : 2854.000 MB/sec Jan 30 08:21:12 Tower kernel: p5_mmx : 2880.400 MB/sec Jan 30 08:21:12 Tower kernel: md: using function: pIII_sse (4639.200 MB/sec) Jan 30 08:21:12 Tower kernel: md: superblock -> /boot/config/super.dat Jan 30 08:21:12 Tower kernel: md: slot 0 device -> hda [3,0] Jan 30 08:21:12 Tower kernel: md: slot 1 device -> ? [0,0] Jan 30 08:21:12 Tower kernel: md: slot 2 device -> ? [0,0] Jan 30 08:21:12 Tower kernel: md: slot 3 device -> ? [0,0] Jan 30 08:21:12 Tower kernel: md: slot 4 device -> ? [0,0] Jan 30 08:21:12 Tower kernel: md: slot 5 device -> ? [0,0] Jan 30 08:21:12 Tower kernel: md: slot 6 device -> ? [0,0] Jan 30 08:21:12 Tower kernel: md: slot 7 device -> ? [0,0] Jan 30 08:21:12 Tower kernel: md: slot 8 device -> ? [0,0] Jan 30 08:21:12 Tower kernel: md: slot 9 device -> ? [0,0] Jan 30 08:21:12 Tower kernel: md: slot 10 device -> ? [0,0] Jan 30 08:21:12 Tower kernel: md: slot 11 device -> ? [0,0] Jan 30 08:21:12 Tower ifplugd(eth0)[894]: Executing '/etc/ifplugd/ifplugd.action eth0 up'. Jan 30 08:21:12 Tower kernel: md: reading superblock from /boot/config/super.dat Jan 30 08:21:12 Tower emhttp[886]: Device inventory: Jan 30 08:21:12 Tower emhttp[886]: /dev/hda (hda1) PATA:ST3500630A/3QG04V5R Jan 30 08:21:12 Tower kernel: md: warning! initializing superblock Jan 30 08:21:12 Tower kernel: md: import hda ST3500630A 3QG04V5R offset: 63 size : 488386552 Jan 30 08:21:12 Tower kernel: md0: new disk Jan 30 08:21:12 Tower emhttp[886]: shcmd (3): rmmod md-mod >>/var/log/go 2>&1 Jan 30 08:21:12 Tower kernel: md: unraid driver removed. Jan 30 08:21:12 Tower emhttp[886]: shcmd (4): modprobe md-mod super=/boot/config /super.dat slots=3,0,0,0,0,0,0,0,0,0,0,0 >>/var/log/go 2>&1 Jan 30 08:21:12 Tower ifplugd(eth0)[894]: Program executed successfully. Jan 30 08:21:12 Tower kernel: md: unraid driver 0.91.0 Jan 30 08:21:12 Tower kernel: md: sizeof(mdp_super_t) = 4096 Jan 30 08:21:12 Tower kernel: md: measuring xor speed Jan 30 08:21:12 Tower kernel: 8regs : 3019.200 MB/sec Jan 30 08:21:12 Tower kernel: 32regs : 1952.800 MB/sec Jan 30 08:21:12 Tower kernel: pIII_sse : 4638.000 MB/sec Jan 30 08:21:12 Tower kernel: pII_mmx : 2855.600 MB/sec Jan 30 08:21:12 Tower kernel: p5_mmx : 2880.400 MB/sec Jan 30 08:21:12 Tower kernel: md: using function: pIII_sse (4638.000 MB/sec) Jan 30 08:21:12 Tower kernel: md: superblock -> /boot/config/super.dat Jan 30 08:21:12 Tower kernel: md: slot 0 device -> hda [3,0] Jan 30 08:21:12 Tower kernel: md: slot 1 device -> ? [0,0] Jan 30 08:21:12 Tower kernel: md: slot 2 device -> ? [0,0] Jan 30 08:21:12 Tower kernel: md: slot 3 device -> ? [0,0] Jan 30 08:21:12 Tower kernel: md: slot 4 device -> ? [0,0] Jan 30 08:21:12 Tower kernel: md: slot 5 device -> ? [0,0] Jan 30 08:21:12 Tower kernel: md: slot 6 device -> ? [0,0] Jan 30 08:21:12 Tower kernel: md: slot 7 device -> ? [0,0] Jan 30 08:21:12 Tower kernel: md: slot 8 device -> ? [0,0] Jan 30 08:21:12 Tower kernel: md: slot 9 device -> ? [0,0] Jan 30 08:21:12 Tower kernel: md: slot 10 device -> ? [0,0] Jan 30 08:21:12 Tower kernel: md: slot 11 device -> ? [0,0] Jan 30 08:21:12 Tower kernel: md: reading superblock from /boot/config/super.dat Jan 30 08:21:12 Tower kernel: md: warning! initializing superblock Jan 30 08:21:12 Tower kernel: md: import hda ST3500630A 3QG04V5R offset: 63 size : 488386552 Jan 30 08:21:12 Tower kernel: md0: new disk Jan 30 08:21:12 Tower emhttp[886]: shcmd (5): killall -w smbd nmbd Jan 30 08:21:12 Tower nmbd[880]: [2007/01/30 08:21:12, 0] nmbd/nmbd.c:terminate( 56) Jan 30 08:21:12 Tower nmbd[880]: Got SIGTERM: going down... Jan 30 08:21:14 Tower emhttp[886]: Scanning user shares... Jan 30 08:21:14 Tower emhttp[886]: shcmd (6): rm -r /mnt/user/* 2>/dev/null Jan 30 08:21:14 Tower emhttp[886]: shcmd (7): /usr/sbin/nmbd -D Jan 30 08:21:14 Tower emhttp[886]: shcmd (: /usr/sbin/smbd -D Jan 30 08:21:50 Tower kernel: md: reading superblock from /boot/config/super.dat Jan 30 08:21:50 Tower kernel: md: warning! initializing superblock Jan 30 08:21:50 Tower kernel: md: import hda ST3500630A 3QG04V5R offset: 63 size : 488386552 Jan 30 08:21:50 Tower kernel: md0: new disk Jan 30 08:21:56 Tower kernel: md: reading superblock from /boot/config/super.dat Jan 30 08:21:56 Tower kernel: md: warning! initializing superblock Jan 30 08:21:56 Tower kernel: md: import hda ST3500630A 3QG04V5R offset: 63 size : 488386552 Jan 30 08:21:56 Tower kernel: md0: new disk Jan 30 08:22:00 Tower emhttp[886]: shcmd (9): rmmod md-mod >>/var/log/go 2>&1 Jan 30 08:22:00 Tower kernel: md: unraid driver removed. Jan 30 08:22:00 Tower emhttp[886]: shcmd (10): modprobe md-mod super=/boot/confi g/super.dat slots=0,0,0,0,0,0,0,0,0,0,0,0 >>/var/log/go 2>&1 Jan 30 08:22:01 Tower kernel: md: unraid driver 0.91.0 Jan 30 08:22:01 Tower kernel: md: sizeof(mdp_super_t) = 4096 Jan 30 08:22:01 Tower kernel: md: measuring xor speed Jan 30 08:22:01 Tower kernel: 8regs : 3019.600 MB/sec Jan 30 08:22:01 Tower kernel: 32regs : 1956.000 MB/sec Jan 30 08:22:01 Tower kernel: pIII_sse : 4648.000 MB/sec Jan 30 08:22:01 Tower kernel: pII_mmx : 2855.600 MB/sec Jan 30 08:22:01 Tower kernel: p5_mmx : 2880.400 MB/sec Jan 30 08:22:01 Tower kernel: md: using function: pIII_sse (4648.000 MB/sec) Jan 30 08:22:01 Tower kernel: md: superblock -> /boot/config/super.dat Jan 30 08:22:01 Tower kernel: md: slot 0 device -> ? [0,0] Jan 30 08:22:01 Tower kernel: md: slot 1 device -> ? [0,0] Jan 30 08:22:01 Tower kernel: md: slot 2 device -> ? [0,0] Jan 30 08:22:01 Tower kernel: md: slot 3 device -> ? [0,0] Jan 30 08:22:01 Tower kernel: md: slot 4 device -> ? [0,0] Jan 30 08:22:01 Tower kernel: md: slot 5 device -> ? [0,0] Jan 30 08:22:01 Tower kernel: md: slot 6 device -> ? [0,0] Jan 30 08:22:01 Tower kernel: md: slot 7 device -> ? [0,0] Jan 30 08:22:01 Tower kernel: md: slot 8 device -> ? [0,0] Jan 30 08:22:01 Tower kernel: md: slot 9 device -> ? [0,0] Jan 30 08:22:01 Tower kernel: md: slot 10 device -> ? [0,0] Jan 30 08:22:01 Tower kernel: md: slot 11 device -> ? [0,0] Jan 30 08:22:01 Tower kernel: md: reading superblock from /boot/config/super.dat Jan 30 08:22:01 Tower kernel: md: warning! initializing superblock Jan 30 08:22:03 Tower emhttp[886]: shcmd (11): rmmod md-mod >>/var/log/go 2>&1 Jan 30 08:22:03 Tower kernel: md: unraid driver removed. Jan 30 08:22:03 Tower emhttp[886]: shcmd (12): modprobe md-mod super=/boot/confi g/super.dat slots=0,0,3,0,0,0,0,0,0,0,0,0 >>/var/log/go 2>&1 Jan 30 08:22:04 Tower kernel: md: unraid driver 0.91.0 Jan 30 08:22:04 Tower kernel: md: sizeof(mdp_super_t) = 4096 Jan 30 08:22:04 Tower kernel: md: measuring xor speed Jan 30 08:22:04 Tower kernel: 8regs : 3019.200 MB/sec Jan 30 08:22:04 Tower kernel: 32regs : 1950.400 MB/sec Jan 30 08:22:04 Tower kernel: pIII_sse : 4635.200 MB/sec Jan 30 08:22:04 Tower kernel: pII_mmx : 2854.400 MB/sec Jan 30 08:22:04 Tower kernel: p5_mmx : 2879.200 MB/sec Jan 30 08:22:04 Tower kernel: md: using function: pIII_sse (4635.200 MB/sec) Jan 30 08:22:04 Tower kernel: md: superblock -> /boot/config/super.dat Jan 30 08:22:04 Tower kernel: md: slot 0 device -> ? [0,0] Jan 30 08:22:04 Tower kernel: md: slot 1 device -> hda [3,0] Jan 30 08:22:04 Tower kernel: md: slot 2 device -> ? [0,0] Jan 30 08:22:04 Tower kernel: md: slot 3 device -> ? [0,0] Jan 30 08:22:04 Tower kernel: md: slot 4 device -> ? [0,0] Jan 30 08:22:04 Tower kernel: md: slot 5 device -> ? [0,0] Jan 30 08:22:04 Tower kernel: md: slot 6 device -> ? [0,0] Jan 30 08:22:04 Tower kernel: md: slot 7 device -> ? [0,0] Jan 30 08:22:04 Tower kernel: md: slot 8 device -> ? [0,0] Jan 30 08:22:04 Tower kernel: md: slot 9 device -> ? [0,0] Jan 30 08:22:04 Tower kernel: md: slot 10 device -> ? [0,0] Jan 30 08:22:04 Tower kernel: md: slot 11 device -> ? [0,0] Jan 30 08:22:04 Tower kernel: md: reading superblock from /boot/config/super.dat Jan 30 08:22:04 Tower kernel: md: warning! initializing superblock Jan 30 08:22:04 Tower kernel: md: no device Jan 30 08:22:04 Tower kernel: md: import hda ST3500630A 3QG04V5R offset: 63 size : 488386552 Jan 30 08:22:04 Tower kernel: md1: new disk Jan 30 08:22:09 Tower kernel: md: reading superblock from /boot/config/super.dat Jan 30 08:22:09 Tower kernel: md: warning! initializing superblock Jan 30 08:22:09 Tower kernel: md: no device Jan 30 08:22:09 Tower kernel: md: import hda ST3500630A 3QG04V5R offset: 63 size : 488386552 Jan 30 08:22:09 Tower kernel: md1: new disk Jan 30 08:22:14 Tower kernel: md: reading superblock from /boot/config/super.dat Jan 30 08:22:14 Tower kernel: md: warning! initializing superblock Jan 30 08:22:14 Tower kernel: md: no device Jan 30 08:22:14 Tower kernel: md: import hda ST3500630A 3QG04V5R offset: 63 size : 488386552 Jan 30 08:22:14 Tower kernel: md1: new disk Jan 30 08:22:30 Tower kernel: md: reading superblock from /boot/config/super.dat Jan 30 08:22:30 Tower kernel: md: warning! initializing superblock Jan 30 08:22:30 Tower kernel: md: no device Jan 30 08:22:30 Tower kernel: md: import hda ST3500630A 3QG04V5R offset: 63 size : 488386552 Jan 30 08:22:30 Tower kernel: md1: new disk Jan 30 08:22:30 Tower emhttp[886]: shcmd (13): killall -w smbd nmbd Jan 30 08:22:30 Tower nmbd[935]: [2007/01/30 08:22:30, 0] nmbd/nmbd.c:terminate( 56) Jan 30 08:22:30 Tower nmbd[935]: Got SIGTERM: going down... Jan 30 08:22:31 Tower emhttp[886]: Scanning user shares... Jan 30 08:22:31 Tower emhttp[886]: shcmd (14): rm -r /mnt/user/* 2>/dev/null Jan 30 08:22:31 Tower emhttp[886]: shcmd (15): /usr/sbin/nmbd -D Jan 30 08:22:31 Tower emhttp[886]: shcmd (16): /usr/sbin/smbd -D Jan 30 08:22:31 Tower emhttp[964]: driver cmd: start NEW_ARRAY Jan 30 08:22:31 Tower kernel: mdcmd (5): start Jan 30 08:22:31 Tower kernel: md: reading superblock from /boot/config/super.dat Jan 30 08:22:31 Tower kernel: md: warning! initializing superblock Jan 30 08:22:31 Tower kernel: md: no device Jan 30 08:22:31 Tower kernel: md: import hda ST3500630A 3QG04V5R offset: 63 size : 488386552 Jan 30 08:22:31 Tower kernel: md1: new disk Jan 30 08:22:31 Tower kernel: unraid: allocated 2186kB for md0 Jan 30 08:22:31 Tower kernel: md1: running, size: 488386552 blocks Jan 30 08:22:31 Tower emhttp[964]: driver cmd: check Jan 30 08:22:31 Tower kernel: mdcmd (7): check Jan 30 08:22:31 Tower kernel: md: recovery thread got woken up ... Jan 30 08:22:31 Tower kernel: md: writing superblock to /boot/config/super.dat Jan 30 08:22:31 Tower emhttp[967]: shcmd (17): mount -t reiserfs -o noatime,nodi ratime /dev/md1 /mnt/disk1 Jan 30 08:22:31 Tower kernel: md: recovery thread has nothing to resync Jan 30 08:22:31 Tower kernel: reiserfs: found format "3.6" with standard journal Jan 30 08:22:41 Tower kernel: reiserfs: checking transaction log (device md(9,1) ) ... Jan 30 08:22:41 Tower kernel: for (md(9,1)) Jan 30 08:22:41 Tower kernel: is_tree_node: node level 59140 does not match to t he expected one 3 Jan 30 08:22:41 Tower kernel: md(9,1):vs-5150: search_by_key: invalid format fou nd in block 449222. Fsck? Jan 30 08:22:41 Tower kernel: md(9,1):vs-13070: reiserfs_read_inode2: i/o failur e occurred trying to find stat data of [1 2 0x0 SD] Jan 30 08:22:41 Tower kernel: md(9,1):Using r5 hash to sort names Jan 30 08:22:41 Tower kernel: is_tree_node: node level 59140 does not match to t he expected one 3 Jan 30 08:22:41 Tower kernel: md(9,1):vs-5150: search_by_key: invalid format fou nd in block 449222. Fsck? Jan 30 08:22:41 Tower kernel: md(9,1):vs-2140: finish_unfinished: search_by_key returned -2 Jan 30 08:22:42 Tower emhttp[964]: shcmd (17): killall -w smbd nmbd Jan 30 08:22:42 Tower nmbd[960]: [2007/01/30 08:22:42, 0] nmbd/nmbd.c:terminate( 56) Jan 30 08:22:42 Tower nmbd[960]: Got SIGTERM: going down... Jan 30 08:22:44 Tower emhttp[964]: Scanning user shares... Jan 30 08:22:44 Tower emhttp[964]: shcmd (18): rm -r /mnt/user/* 2>/dev/null Jan 30 08:22:44 Tower emhttp[964]: shcmd (19): /usr/sbin/nmbd -D Jan 30 08:22:44 Tower emhttp[964]: shcmd (20): /usr/sbin/smbd -D Jan 30 08:22:54 Tower emhttp[983]: shcmd (21): mkreiserfs -q /dev/md1 >/dev/null Jan 30 08:22:57 Tower kernel: hda: status timeout: status=0xd0 { Busy } Jan 30 08:22:57 Tower kernel: Jan 30 08:22:57 Tower kernel: hda: no DRQ after issuing WRITE Jan 30 08:22:57 Tower kernel: ide0: reset: success Jan 30 08:23:35 Tower emhttp[983]: shcmd (22): mount -t reiserfs -o noatime,nodi ratime /dev/md1 /mnt/disk1 Jan 30 08:23:35 Tower kernel: reiserfs: found format "3.6" with standard journal Jan 30 08:24:04 Tower kernel: reiserfs: checking transaction log (device md(9,1) ) ... Jan 30 08:24:04 Tower kernel: for (md(9,1)) Jan 30 08:24:19 Tower kernel: md(9,1):Using r5 hash to sort names Jan 30 08:24:19 Tower emhttp[982]: shcmd (21): killall -w smbd nmbd Jan 30 08:24:19 Tower nmbd[976]: [2007/01/30 08:24:19, 0] nmbd/nmbd.c:terminate( 56) Jan 30 08:24:19 Tower nmbd[976]: Got SIGTERM: going down... Jan 30 08:24:21 Tower emhttp[982]: Scanning user shares... Jan 30 08:24:21 Tower emhttp[982]: shcmd (22): rm -r /mnt/user/* 2>/dev/null Jan 30 08:24:21 Tower emhttp[982]: shcmd (23): /usr/sbin/nmbd -D Jan 30 08:24:21 Tower emhttp[982]: shcmd (24): /usr/sbin/smbd -D Jan 30 08:26:01 Tower smbd[1003]: [2007/01/30 08:26:01, 0] lib/util_sock.c:get_p eer_addr(1000) Jan 30 08:26:01 Tower smbd[1003]: getpeername failed. Error was Transport endp oint is not connected Jan 30 08:26:01 Tower smbd[1003]: [2007/01/30 08:26:01, 0] lib/util_sock.c:get_p eer_addr(1000) Jan 30 08:26:01 Tower smbd[1003]: getpeername failed. Error was Transport endp oint is not connected Jan 30 08:26:01 Tower smbd[1003]: [2007/01/30 08:26:01, 0] lib/util_sock.c:write _socket_data(430) Jan 30 08:26:01 Tower smbd[1003]: write_socket_data: write failure. Error = Co nnection reset by peer Jan 30 08:26:01 Tower smbd[1003]: [2007/01/30 08:26:01, 0] lib/util_sock.c:write _socket(455) Jan 30 08:26:01 Tower smbd[1003]: write_socket: Error writing 4 bytes to socke t 22: ERRNO = Connection reset by peer Jan 30 08:26:01 Tower smbd[1003]: [2007/01/30 08:26:01, 0] lib/util_sock.c:send_ smb(647) Jan 30 08:26:01 Tower smbd[1003]: Error writing 4 bytes to client. -1. (Connec tion reset by peer) root@Tower:~#
January 31, 200719 yr That board uses Intel ICH7 southbridge chip, which doesn't have proper IDE (aka, PATA) support in the linux kernel that unRAID 3.0 is using (supports ICH6 and below). The result is that the IDE driver will not use DMA which is why you're seeing the slow rate. However... we recently added this support & are testing it. In meantime, you can avoid the IDE controller on the MB (use a Promise card instead).
January 31, 200719 yr Author Thanks. Do you know how long it will be before you roll out the patch? I can live with the slow parity if I know that shortly there will be an update. It does seem strange though, that when I had my other ide drive in the slot and used my SATA drive as parity, I didn't have the slow speed. It was only when making the new IDE drive as the parity that the slow down occured. Would I not see slow speed regardless if the IDE drive was parity or not?
January 31, 200719 yr Author Hi Tom, my mistake I have the Asus P5Pl2 mb in my system. Does this have the same problem with the southbridge chip? I see from another site that it has Chipset Type: Intel 945PL, Intel ICH7. So It appears it has the same problem. I just want to confirm.
February 1, 200719 yr Author Well I put my new drive as parity and put the old parity drive as unassigned for now. However when I do this I am getting the following error. Not sure why the same device is showing up twice and two drives for the first device? I checked my device tab and all is in order there. Is this because I have my old parity drive installed but unassigned? Do I need to disconnect it first, rebuild parity with the new drive, then add the old parity drive?
February 1, 200719 yr Author Okay now I"m getting worried. I disconnected the old parity drive completely. Still no matter what I do the new 500IDE drive is showing up under parity and device one even though I only have it selected as parity. What am I doing wrong?
February 1, 200719 yr Author Well I got part of it back. The new disk is now parity however my last device shows as blue which means it's a new disk. However it isn't new. It does have data on it which I don't want to lose. What do I do now? CAn I simply click the checkbox then Restore or do I just click Start??? Help! Also just to confirm. The errors noted above in my syslog are definitely related to the southbridge chip and definitley not a result of a bad drive? I have 30 days for a direct replacement disk and just want to make sure.
February 1, 200719 yr Olly Olly Oxen Free...anybody there? 333 views...oops 334.....335.... From what I see it looks like you tried to move disks around AND add one at the same time. unRaid does not like that and stopped you. Next time, do one thing at a time. You probably should check the little checkbox and then press the "Restore" button. It should then re-build parity with the data on the data disks. It should see that it is already formatted and not prompt you to re-format it. It if does DO NOT re-format it or you will lose data. Although it is not clear, the reason the disk showed up twice in your prior screenshot was that unRaid tracked where the disk used to be, and showed the OLD and NEW disk-serial-numbers for the slot where the serial-number had changed. You basically just need to recalculate parity, since right now you are running unprotected. Joe L.
February 2, 200719 yr Author Well parity is running but it's running at 1.5kb/sec which apparently will take 6806min to complete. So in 3 days time parity will complete, I'll add my new disk and then run parity for another 3 days. So effectively my system is down for an entire week. Yikes! Hopefully Tom comes out with his update soon.
February 14, 200719 yr Author Even though my motherboard doesn't have proper support, P5PL2, at one point before making my ide drive the parity drive, I could copy a large 2gb file from one SATA drive to another SATA drve pretty quickly. Now that my ide drive is parity and I'm copying to the exact same SATA drive to the other, it takes like 45 min to copy the same one file. I'd really like to understand why this is? I can wait for the new re4lease but I'm really wondering if it will correct the problem or if there is some other underlying problem?
February 15, 200719 yr DD: Sorry, just saw your thread/problem. Without being critical, you mentioned the ability to have a direct drive replacement for 30 days (if not already up). Per Tom's comment even with the update to 2.6.x why not "exchange" your PATA 500 for a SATA 500 GB Disk (as you noted the SATA worked!) and pay the difference. The amount of time/effort/frustration/problem/compatability et al that you've experienced is got to be less more than the difference in price. If not, pull the 500 PATA & replace it with a "new" 500 SATA (< $140) keep the 500 PATA until new release and have more storage. Just a thought Dave PS - I'll buy your 500 PATA for Cheeep! Let me know! Seriously, I'm not using SATA's yet so really would consider it. PM me!
February 15, 200719 yr Author DD: Sorry, just saw your thread/problem. Without being critical, you mentioned the ability to have a direct drive replacement for 30 days (if not already up). Per Tom's comment even with the update to 2.6.x why not "exchange" your PATA 500 for a SATA 500 GB Disk (as you noted the SATA worked!) and pay the difference. The amount of time/effort/frustration/problem/compatability et al that you've experienced is got to be less more than the difference in price. If not, pull the 500 PATA & replace it with a "new" 500 SATA (< $140) keep the 500 PATA until new release and have more storage. Just a thought Dave PS - I'll buy your 500 PATA for Cheeep! Let me know! Seriously, I'm not using SATA's yet so really would consider it. PM me! My MB supports 4 SATA and 2 IDE. I had room for one last drive which was the IDE drive. So it just makes sense to use what I have rather than going out to buy a Promise Controller to install two more SATA drives. Plus as I mentioned it was working fine with the one IDE drive and only had a problem when I made the new drive parity.
February 15, 200719 yr DD: Gotcha - good luck! I picked up a Promise Card from Ebay several months ago for about $20 (IDE), with SATA becoming the deFacto std, that might have been a mistake, but when I built my UnRaid, the SATA ports were not active (version 2.6x not 3.x). Since Tom is indicating that the new version with Linux 2.6.x kernel is about to be released, if you are not in a hurry, your might just wait another couple of weeks. That might solve the problem with the Intel ICH7 chipset. Dave
Archived
This topic is now archived and is closed to further replies.