xamindar

I was just going to say $70-$120 is a lot to pay for just a control web interface on top of a free operating system. But with free upgrades when they come about it doesn't seem that steep a price anymore. You are right though, we do not know what goes on behind the scenes. But the positive appearance to potential customers still needs to be there.

If that's true then judging by the start of this thread it is now two or three weeks that Lime-Technology has been "closed"

Also, was the site down for a time yesterday? Are there other problems Lime-tech is having?

Pretty sure it is NOT enabled in the kernel on unraid. Someone correct me if I am wrong. Don't know why, but there are a quite a few options set in the unraid kernel that baffle me.

You can't select them from the devices tab? Stop the array first and then look at the devices tab.

Just look at the unraid kernel config and see if it has a module for that chipset enabled. Or just get the card and find out when you insert it and boot up.

What do those errors pertain to? Are they any errors with writing or reading?

Why in the world would you tell them you were returning it because of unraid issues? It has nothing to do with unraid. The pending sectors are reported from the firmware built into the drive its self. Is this the first time you have ever returned something to the store. When returning something it is best to only state the actual cause for the return as simple and as clear as possible. Saying anything about issues that have nothing to do with it will just confuse them and they may just end up giving you store credit only. Though, you probably just want an exchange, which should be no problem if you simply tell them this drive is defective and you would like a new one.

Since it already has pending sectors I would return it for a replacement if this is a new drive. There should not be any at all on a new drive.

Why do that when you can write a script that will do that for free?

First of all thanks for all the hard work you put into your scripts Joe. This one is just what I need so I can stop using the very clumsy cron jobs. I tried out this script and put a few rc scripts in the /etc/rc.d/unraid.d directories for it to run (crashplan, mediatomb, cache_dirs, rsyncd). Now is it correct that this script will always think the array is stopping if there is a stop event in the last 50 lines of the log file? The first time I ran this script to test (unraid_addon_control.sh -u -F) it was starting then stopping all the rc scripts every 30 seconds or so. Got really confusing with crashplan trying to check its files and cache_dirs didn't close properly when it was stopped right after being started. I know this script is new and still being worked on. Is it mainly there to just stop things properly before a shutdown (ie. not when the array is manually stopped then started again)? Again, thanks for this script. I'm not complaining or anything, just trying to understand how it works and how I am supposed to use it.

To "force" an unmount you use the "-l" (lazy) option. It will force an unmount whether there are open files on that mount or not.

If you type "mount" it will show "type fuseblk" for any mounted as ntfs-3g and any other filesystems under fuse.

Just a note, I'm running unraid 4.5.1 on a Slackware 13 installation. I just matched the kernel to the one unraid uses. All works fine.

Don't confuse PWM in lm-sensors with PWM in the bios. I was reading about the 4-pin and 3-pin stuff when I was writing my script and don't know why lm-sensors calls everything pwm. The way I understand it real pwm (4 pin fans) are controlled by pulsing the power at different intervals while always staying at 12 volts. Apparently they are less likely to stall at lower rpms that way. But then there are 3 pin (non pwm) fans. The speed of them is changed by lowering the voltage. This way of changing speed does stall the fan at low rpms and depending on the fan depends on when it stalls. Also, you have to raise the power pretty high to get the fan to start again. Obviously 4 pin is better but 3 pin works just fine in most cases. I am pretty sure if you are using only 3 pin fans you need to select 3 pin in the bios. Don't worry about it not calling it pwm. Lm-sensors should still be able to control them. I have no idea why there is a server and a workstation setting though. If I were you I would try the three settings of disabled, 3 pin server, and 3 pin workstation and see if any of those change what you see under your hwmon0/devices area. Specifically look for pwm2_enable or see if fan2_input is reporting rpms.

Thats one of the problems. He doesn't have pwm_enable. The script wasn't able to change it and the directory listing he posted doesn't include it. His fans are spinning but fan2_input is not showing any rpm values. I don't really have much experience with this to know what the problem is. Looks like your board deffinately supports fan speeds. starcat, do the IPMI fan speeds ever change? They should constantly fluctuate a little as the fans don't go the exact same speed at all times. From one of your earlier posts they were all even numbers (800, 1500...). That doesn't make sense to me unless your monitors are rounding them to the closest 100 or something. In any case, sorry, I'm out of ideas. Sense you have the fan divisors (I don't on mine for some reason) you can read up on it here: http://www.lm-sensors.org/browser/lm-sensors/trunk/doc/fan-divisors

Well, updating the bios fixed the issue with the waiting forever when no array is defined. That was the biggest issue and I'm glad it works now. So now it will sit there for like 5 seconds with the no array defined message and then continue on to boot. I also updated my motherboard bios while I was at it. Was hoping it would be the cause of not being able to boot from any drives on the tx4 card but I guess not. Still can not boot from a disk plugged into the promise card. I guess it is just not possible to do this with a promise card? Just seems odd.

Yes I can, but wont that erase everything on it? I don't think this will work though, because I can not creat an array without a disk and all ports are not full yet.

No, it only gives options for Stripe or Mirror. Mirror will not let me save with only one disk set. I have been googling for a bios to flash but so far no luck Even after passing ESC it fails to find a boot device. Same thing was happening on my other pci sata card (that one was a 2 port tx2 but didn't need to press ESC to pass it). EDIT: Found the bios for this here. http://www.promise.com/support/download/download2_eng.asp?productID=108&category=all&os=100 The card currently has the older one installed. I guess I'll try flashing the newer one to see if it helps.

I have an issue with the promise sata150 tx4 I just got. It will sit at the "no array defined" screen indefinately unless I press ESC. How do these things work? Do I need to define 4 arrays(one for each of the four drives connected)? Will defining an array erase the disk? I don't get why it doesn't just continue as if they are all seperate disks if there is no array defined. Also, I have unraid on a full slackware distro on one hdd, is there a way to boot off this promise card instead of the mainboard sata ports? I set it to boot add in cards first in the bios but apparently this card doesn't allow booting from it. Thanks for any help!

Dang, I had a whole long reply typed out then my computer froze (laptop doesn't like to compile programs for a long time, the ram overheats). What do you see under /sys/class/hwmon/hwmon0/device ?? "ls /sys/class/hwmon/hwmon0/device" Are you running on a full slackware setup? Looks like you are if you are using lm-sensors. Looks like you either don't have 3-wire fans connected or your sensors do not have the correct circuitry connected on the mainboard to control them. Try the following while physically watching the fan: "echo 0 > /sys/class/hwmon/hwmon0/device/pwm2" - that is a zero. It should completely stop that fan. If it does stop spinning then you will be able to control them. "echo 255 > /sys/class/hwmon/hwmon0/device/pwm2" - will bring it back to full speed. If that does nothing at all then either linux is not allowed to change the speed or the board doesn't support it. The error the script gave means it was unable to set the file that tells whether linux controls the fan or the bios controls the fan. I haven't done much testing with different sensor drivers so don't know if there is a different spot for that in your case. Post a directory listing of /sys/class/hwmon/hwmon0/device so we can see if there is anything else that might help. Also "cat /sys/class/hwmon/hwmon0/device/fan2_input" should give you the rpm of the fan on pwm2.

Looks like a nice case. I wonder if it has the same trays as the ss-500 does. Would definitely be a plus for people who have those 5 in 3s as they would be interchangeable.

I decided to just get the Promise sata150 tx4 as it seems the best supported. Got it on ebay for $20. I can tell you with my current card (tx2 2 port sata150 pci card) my parity checks start out around 40,000 KB/sec. This is with two data drives on the sata card and the parity on the motherboard slot. Pretty sure my card is only running at 33mhz though so it might be faster if it was 66mhz.

I just tried but that sata driver from jetway would not build OR patch against the unraid kernel. Things in the kernel have probably changed too much for that driver to work as is. Surprisingly wikipedia has a lot about getting your sata ports working: http://en.wikipedia.org/wiki/List_of_Marvell_Technology_Group_chipsets#88SE61xx_Chipsets_Linux_support So the drivers that should be able to drive your ports are either pata_marvel or ahci. Probably want to use ahci unless you really need to use your ide ports. You need to add a module perimeter to enable the marvel apparently. Try this while telnetted into your unraid: "rmmod ahci" - that will unload the ahci driver "modprobe ahci marvell_enable=1" - that should reload it with marvel support. Then hopefully your sata ports will work. If they do (dmesg should help) then just edit your syslinux.cfg on your flash and add "ahci.marvell_enable=1" to the append line of your unraid selection. For example: default menu.c32 menu title Lime Technology LLC prompt 0 timeout 50 label unRAID OS menu default kernel bzimage append initrd=bzroot ahci.marvell_enable=1 label Memtest86+ kernel memtest Good luck. Oh, and make sure the sata ports are enabled in the bios and in "ahci" mode, not ide emulation.

As well, I have two 1tb EARS jumpered in my unraid and they have performed perfectly.