limetech

Thank you for the report! Now get some more memory in there or there will be some strange errors eventually. What happens is unRAID is running without any swap space. When linux needs memory, and there's no swap space, it's just starts "randomly" killing processes leading to very strange behavior.

Good points Koolkiwi, Version 4.1 was produced specifically for the MD-1500 product, where we needed to have 16-drive support. While it is a pretty significant change going from linux kernel 2.6.20 to 2.6.22.1, we extensively tested on the MD-1500 platform. Probably, version 2.6.20 would have been fine as well, but looking through kernel change logs, we felt it was worth it to pick up all the bug fixes related to SATA. Probably any problems we see in 4.1 will be related to h/w not in the MD-1500. As for your earlier question about AHCI, yes we set all the motherboard SATA controllers to operate in AHCI mode.

Download. Ok, sorry to disappoint, this is not the big "security + writable user share" release, those major features will get into 4.2 This is the release we're shipping with the MD-1500 product. The main features in this release are an upgrade of the linux kernel to the latest stable version (2.6.22.1), and support for 16 hard drives. The reason we upgraded the linux kernel was to get all the latest changes in SATA subsystem. This release has been well tested on the ASUS P5B-VM DO motherboard. For those with Realtek LAN chips: the latest Realtek manufacturer driver does not compile without error for some reason under 2.6.22.1, so we built in the "stock" linux driver. There are a series of patches for this driver which should get incorporated in the next major linux release (2.6.23). So if you have a Realtek LAN chip, try this release and let me know if there are problems and we will attempt to address them. unRAID Server 4.1 Release Notes Upgrade Instructions -------------------- If you are currently running unRAID Server 4.0-beta1 or higher, it is only necessary to copy the files: bzimage bzroot from the new release to the root of your Flash device. This can be done either by plugging the Flash into your PC or, but copying the files to the 'flash' share on your running server. The server must then be rebooted. If you are currently running unRAID Server 3.0-beta1 or higher, please follow these steps to upgrade: 1. Referring to the System Management Utility 'Main' page, make a note of each disks's model/serial number; you will need this information later. 2. Shut down your server, remove the Flash and plug it into your PC. 3. Right-click your Flash device listed under My Computer and select Properties. Make sure the volume label is set to "UNRAID" (without the quotes) and click OK. You do NOT need to format the Flash. 4. Copy the files: bzimage bzroot syslinux.cfg from the new release to the root of your Flash device. 5. Right-click your Flash device listed under My Computer and select Eject. Remove the Flash, install in your server and power-up. 6. After your server has booted up, the System Management Utility 'Main' page will probably show no devices; this is OK, navigate to the 'Devices' page. Using the model/serial number information gathered in step 1, assign each of your hard drives to the correct disk slot. 7. Go back to the 'Main' page and your devices should appear correctly. You may now Start the array. If you are installing this release to a new Flash, please refer to instructions on our website at: http://www.lime-technology.com/wordpress/?page_id=19 Changes from 4.0 to 4.1 ----------------------- Improvement: support up to 16 hard drives Improvement: upgrade to linux kernel 2.6.22.1 Improvement: upgrade Intel Pro/1000 driver to version 7.6.5 Improvement: use stock r8169 driver instead of Realtek r1000/r8168 driver Improvement: add JMicron PATA support

Use of the 'cp' command is documented in the wiki, but we never intended this to be the primary means of moving files. This is mainly because one of our design goals is to hide the underlying linux OS as much as possible. Also, as you have observed, there is not much of a speed improvement over moving files with Explorer anyway. Nevertheless, as unRAID OS evolves, we plan to make it easier to cusstomize the platform and fix these annoying problems, such as... This is just an artifact of the default file create permissions for 'root'. What's happening is that Samba (which implements Windows Networking protocol) is "overloading" some of the unix file permission bits to implement the DOS 'Hidden' and 'System' attributes (which are meaningless in the unix world). This is a known "issue" for which you can search to find more info on. In a nutshell, since unRAID is meant to be used in a Windows Networking environment, we enable the Samba feature that implements 'Hidden' and 'System'. We plan to make this configurable in an upcoming release. Don't blame Linus!! We take full responsibility for not including all the necessary code pages in the unRAID build. This was done to conserve space, but again, we plan to correct this in a future release. I guess those would be the mail systems created by US developers Thank you!

Main reason is our supplier only carries the 1.6 GHz version with 800 Mhz FSB. When faster version becomes available, probably will start using it.

tftpd is already included - it's called in.tftpd and is normally invoked via inetd; however, it is currently commented out in inetd.conf configuration file. Probably easiest way to start it would be via command line in the 'go' startup script on the flash. Here's a man-page to get you started.

Yes, that Lian-Li case is very very nice. The picture doesn't do it justice - I'll be adding a "gallery" soon with more pix and close-ups.

What's happening is the PCI bus at approx. 133MB/sec becomes the bottleneck. The parity sync rate is showing the rate at which the parity drive is being written. To generate/check parity you have read all the data drives, and write (or read) the parity drive. So 133MB/sec PCI bandwidth divided by 4 (because all 4 drives share the PCI bus) is about what you should see.

We are pleased to announce availability of a new server product called the MD-1500. For a limited time, enter "unraidforum" in the Customer Code box on the order form to receive $100 off any MD-1500 order.

I'll check into this, but I believe the "extended attributes" have to also be built into the file system.

What you describe is exactly what we were looking for in a chassis. If you have ever seen/used the Antec Sonata chassis, there's a good example of what we wanted to do: Notice how these drive trays work. You attach the tray, slide into chassis, then hook up individual power and data cable. We tried to get Antec to quote us a custom chassis with this style drive cage the entire height of the chassis, but they weren't interested unless we wanted 10,000 of them

Yes. However many multi-port controller cards want to operate in "RAID" mode. You need a card that will just export each port individually.

If you have the card it's a simple process to determine. You don't have to put together a full system. Get just about any motherboard you might have laying around (that will support USB Boot). Plug the card into it, hook up a power supply and boot unRAID basic. You can do this on a table-top. Then copy the system log to the Flash and post & I can see if the ports are recognized.

Agreed, though throughput overhead is truly negligible. The big advantage of course is being able to install/remove drives without opening the case and dealing with cables and fasteners!

Yes, that board has a Pro/100 LAN chip which is supported.

Actually, we've been evaluating the 5-in-3 version and it's not too bad.

Very clever, thanks!

That Sunix card is SATA vs SATAII. You probably won't notice any difference though, at least not due to SATA vs. SATAII.

Have you ever encountered one of those fan controllers which also has a system power & reset switch?

We're using the PC Power & Cooling Silencer 610 EPS12V.

The h/w will work, but you should run unRAID 4.0.

Yes it should work. If you an on-board LAN chip, turn it off in the bios.

Thanks for the report! I've never seen this happen, where did you hear this from?

Thanks for the report! Does the Flash appear to the bios as a 'hard drive' or as a 'removeable drive' or something else?

Please post your system log. Instructions