Torquewrench

Use EMCKDHJ35 for $10 off each, but limit appears to be 3 per customer. Cannot be combined with NEWCUSTOMER10.

Yeah, I got it. I have one SuperMicro SAT-MV8, so I want to make sure I can use it in a 4220 or 4224, which I think I can with the reverse breakout cable. My next controller will definitely be the SuperMicro AOC-SASLP-MV8 on a PCI-E motherboard, like you said, I need to be able to handle the 24 drives so 2 of those and some motherboard sata ports should do it. Thanks, Phil/TW

Ok, so now I'm leaning towards the 4224 like everyone else! Let me make sure I have this right. I can use my 8X SATA MV8 controller card and use two reverse breakout 4-into-1 SATA-SAS cables (~$15 each) to go from the controller to the backplane. If I come to my senses and want sub 72-hour parity checks and decide to get a PCI-E motherboard and PCI-E SAS MV8 controller(s) then I will just need 4-lane SAS cables from these to the backplane. Do I have that right? If I do then I think it DOES make sense to get the 4220 or 4224, especially if the 4224 includes the 3x120mm fanboard. Thanks, Phil/TW

I have a 8 sata drives plus two ATA drives (system, cache) on an 8X PCI-X sata controller now and a PCI only motherboard. I can handle the cable management, bundling is fun, but I'm not seeing any compelling benefits to overcome the expense of replacing motherboard, controller, and cabling in addition to the $50 premium of the case. Regarding the noise, the case will be in the garage so I might want to upgrade to the 120mm plate for cooling but the noise won't be a problem. Anything esle I should be aware of? Thanks, Phil/TW

In the market for a new case, was leaning towards the 4020, now I see folks using the 4220. My read is it would require new controller(s), cables, maybe a new motherboard to go with the controllers, all for the benefit of SAS vs. plain sata cables. Am I reading the situation right? Any reason I'm missing I would pay $50 more for the 4220 and all the additional cost for the items mentioned if I'm happy with my SATA setup? Thanks, Phil/TW

For those running unRAID on a full Slackware distro: How do you backup your system drive so that you can restore in the event of a crash? If this were a Windows system I'd take a Ghost image or something similar periodically, but I don't know what the best approach is in Slackware/Linux? How have others solved this problem? Thanks, Phil/TW

Checked the BIOS, all settings intact. It appears that this is a result of running rtorrent and low disk space (<5GB). When I deleted some recordings and freed up ~50GB the problem disappeared. Regarding Windows being at fault, I see the pausing even when logged into a terminal, so it's not a Windows thing.

Definitely worth a check to make sure the bios settings are still there, I'll give it a look.

All seagates, all but one 7200rpm. Beyond the smart long test, any recommendations on testing the drives?

Hi, This is a new behavior where my unraid server is pausing for 1-30sec. This pausing is a total system freeze and affects all operations including terminal sessions, file transfers, videos playing, etc. The frequency and duration of the pauses varies. This is a new behavior and I haven't recently changed any hardware or software. Here's a description of the system: ASUS A7N8X-E m/b AMD Athlon 2500+ processor 1GB memory, 1 stick 5 1.5TB, 1 1TB drives (drives are pretty full, 10-20GB left on each if this might matter) 27GB system drive running slackware 12.2 2GB Cruzer running unRAID 4.4.2 MV8 PCI-X controller card Tried running just from USB stick (not running full slackware), same behavior Drives were running 39-42C, put a big fan in front of it and got drive temps down to 34-36C, same behavior Drives are not ticking or clunking All drives pass SMART short test, running long tests but so far no failures Located files on individual disks (pausing files not located on just one disk), ran SMART Long test on these drives first, passed, now running Long test on other disks. My thought is that this is a hardware failure and not the disks so my plan is to swap in another motherboard, ram, processor, and power supply. I only have one controller so I can't swap this. Has anyone else seen this behavior? If there is a simple fix or a likely root cause I'd love to hear it. Thanks, Phil/TW

Got the message: unpacking initramfs not syncing kernel panic: bad crc Eventually traced it to a bad stick of memory using memtest86. Didn't see this anywhere on the board so I wanted to share. Check your memory! Phil/TW

I just documented my install of blockcontrol, rtorrent and rutorrent onto my full slackware install unRAID installation and I'll be posting it in the next few days. I agree, ruTorrent is the best web interface to rTorrent I've used so far. Phil/TW

You sure did, I must have understod you the first time then got it in my head backwards this time. I'm so happy it's working! Also, user shares are working. My next project is getting moblock-control working, which I did on another slack machine, so it shouldn't be too hard . Famous last words. Thanks for your help, Phil/TW

This has got to be it, I was booting into my backup kernel the whole time so no wonder I kept seeing the same thing. I booted into the other vmlinuz kernel and was able to run emhttp WITH NO SEGFAULT ;D ;D ;D I'm doing a fresh install from scratch just to wipe the slate clean, I'll report on how it goes. Thanks again, Phil/TW

Just noticed something that might be relevant. This is an ls of my /boot directory on the hard drive: total 24045 drwxr-xr-x 2 root root 920 Nov 6 08:41 ./ -rw------- 1 root root 97792 Nov 6 08:41 map -rw-r--r-- 1 root root 890272 Nov 6 08:41 System.map -rw-r--r-- 1 root root 1869936 Nov 6 08:41 vmlinuz drwxr-xr-x 23 root root 536 Nov 6 07:05 ../ -rw-r--r-- 1 root root 891468 Nov 6 06:41 System.old -rw-r--r-- 1 root root 1874096 Nov 6 06:41 vmlinuz.old -rw-r--r-- 1 root root 512 Nov 3 21:15 boot.0300 -rw-r--r-- 1 root root 168 Nov 3 21:15 boot_message.txt lrwxrwxrwx 1 root root 28 Nov 3 21:13 config -> config-huge-smp-2.6.27.7-smp lrwxrwxrwx 1 root root 37 Nov 3 20:55 README.initrd -> /usr/doc/mkinitrd-1.3.2/README.initrd -rw-r--r-- 1 root root 5040 Nov 29 2008 diag1.img -rw-r--r-- 1 root root 1393024 Nov 20 2008 System.map-huge-2.6.27.7 -rw-r--r-- 1 root root 89081 Nov 20 2008 config-huge-2.6.27.7 -rw-r--r-- 1 root root 4540208 Nov 20 2008 vmlinuz-huge-2.6.27.7 -rw-r--r-- 1 root root 927553 Nov 20 2008 System.map-generic-2.6.27.7 -rw-r--r-- 1 root root 89202 Nov 20 2008 config-generic-2.6.27.7 -rw-r--r-- 1 root root 2220880 Nov 20 2008 vmlinuz-generic-2.6.27.7 -rw-r--r-- 1 root root 1432921 Nov 20 2008 System.map-huge-smp-2.6.27.7-smp -rw-r--r-- 1 root root 89384 Nov 20 2008 config-huge-smp-2.6.27.7-smp -rw-r--r-- 1 root root 4727664 Nov 20 2008 vmlinuz-huge-smp-2.6.27.7-smp -rw-r--r-- 1 root root 965704 Nov 20 2008 System.map-generic-smp-2.6.27.7-smp -rw-r--r-- 1 root root 89505 Nov 20 2008 config-generic-smp-2.6.27.7-smp -rw-r--r-- 1 root root 2347888 Nov 20 2008 vmlinuz-generic-smp-2.6.27.7-smp -rw-r--r-- 1 root root 15754 Feb 21 2008 slack.bmp In my lilo.conf I'm pointing at vmlinux-huge-smp-2.6.27.7-smp but it still has the Nov 20, 2008 date which is the date it was minted, while vmlinuz has dates reflecting it's been messed with lately. Is it possible when I run the final make install it's updating vmlinuz when it should be updating vmlinux-huge-smp-2.6.27.7-smp, or perhaps I should be pointing lilo.conf to vmlinuz? Thanks, Phil/TW