limetech

I'm very happy for you... but not *that* happy...

cohiba- I don't think the problem you're seeing is due to the driver not getting loaded. Seeing the syslog will be a big help. I'm not completely sure about the state of Realtec support. This is because we don't have any Realtec-based NIC's to test with, but looking at the linux change log, there have been updates to the built-in driver. BTW, the "built-in" driver is different than the driver supplied on the Realtec site. We tried downloading and building the latest Realtec driver, but it does not compile with our kernel (2.6.24.4) - gets numerous compile errors. Realtec is very slow to update their drivers and typically lag pretty far behind linux kernel development. This is probably why everyone uses the 'built-in' driver, which is maintained independently from Realtec (probably kernel developers get tired of dealing with Realtec lag time to update their drivers - just a guess). Here is latest compile error message: make[2]: Entering directory `/usr/src/linux-2.6.24.4' CC [M] /usr/src/r8169/src/r8169_n.o /usr/src/r8169/src/r8169_n.c: In function 'rtl8169_init_one': /usr/src/r8169/src/r8169_n.c:2431: error: implicit declaration of function 'SET_MODULE_OWNER' /usr/src/r8169/src/r8169_n.c:2594: error: 'struct net_device' has no member named 'poll' /usr/src/r8169/src/r8169_n.c:2595: error: 'struct net_device' has no member named 'weight' /usr/src/r8169/src/r8169_n.c: In function 'rtl8169_rx_interrupt': /usr/src/r8169/src/r8169_n.c:3526: error: 'struct net_device' has no member named 'quota' /usr/src/r8169/src/r8169_n.c:3526: warning: type defaults to 'int' in declaration of '_y' /usr/src/r8169/src/r8169_n.c:3526: error: 'struct net_device' has no member named 'quota' /usr/src/r8169/src/r8169_n.c:3526: warning: comparison of distinct pointer types lacks a cast /usr/src/r8169/src/r8169_n.c: In function 'rtl8169_interrupt': /usr/src/r8169/src/r8169_n.c:3697: error: too few arguments to function 'netif_rx_schedule_prep' /usr/src/r8169/src/r8169_n.c:3698: error: too few arguments to function '__netif_rx_schedule' /usr/src/r8169/src/r8169_n.c: In function 'rtl8169_poll': /usr/src/r8169/src/r8169_n.c:3741: error: 'struct net_device' has no member named 'quota' /usr/src/r8169/src/r8169_n.c:3741: warning: type defaults to 'int' in declaration of '_y' /usr/src/r8169/src/r8169_n.c:3741: error: 'struct net_device' has no member named 'quota' /usr/src/r8169/src/r8169_n.c:3749: error: 'struct net_device' has no member named 'quota' /usr/src/r8169/src/r8169_n.c:3752: error: too few arguments to function 'netif_rx_complete' make[3]: *** [/usr/src/r8169/src/r8169_n.o] Error 1 make[2]: *** [_module_/usr/src/r8169/src] Error 2 make[2]: Leaving directory `/usr/src/linux-2.6.24.4' make[1]: *** [modules] Error 2 make[1]: Leaving directory `/usr/src/r8169-6.005.00/src' make: *** [modules] Error 2

Or, you can send me an email: [email protected] asking, "Hey man, can you build the 3ware driver for me?". To which I would respond, "which model 3ware card is it?".

This topic has been moved to Good Deals!. [iurl]http://lime-technology.com/forum/index.php?topic=1778.0[/iurl]

cohiba- Since you have a monitor/keyboard, after system boots, log in via console and please copy the system log to the the Flash: cp /var/log/syslog /boot/syslog.txt Then power down, plug Flash into PC and post the syslog. While you're at it, also upgrade to 2.4-beta6.

Intel D865GLCLK. We still have a couple of these, send me an email at [email protected].

eltigro- Please send me p/m with the email address you used to order. I don't see any email from the address you specified on your forum profile. The keys are sent as email binary attachments. From time-to-time someone emails us saying they didn't receive their key, but later found out their email provider or spam filter blocked it.

Heh - you're getting close One suggestion - use grub instead of lilo.

4.3-beta6 should fix these problems reading drive temps.

Download. More changes to fix user-reported problems. unRAID Server 4.3-beta6 Release Notes ===================================== Changes from 4.3-beta5 to 4.3-beta6 ----------------------------------- Improvement: update to latest Intel network driver (7.6.15.4). Bug Fix: Correct problem enabling SMART before reading disk temperatures. Bug Fix: Fix crash that may occur if there is a large number of user shares. Changes from 4.3-beta4 to 4.3-beta5 ----------------------------------- Bug Fix: Fix 'hang' that may occur starting syslogd. Improvement: Add 'sync' as last step in 'mover' script Changes from 4.3-beta3 to 4.3-beta4 ----------------------------------- New feature: cache disk support. Improvement: enable SMART before reading disk temperature. Improvement: upgrade from linux kernel 2.6.24.3 to 2.6.24.4 (refer to http://lwn.net/Articles/274741). Improvement: upgrade from Samba 3.0.28 to Samba 3.0.28a (addresses some Vista issues, refer to http://us1.samba.org/samba/history/samba-3.0.28a.html). Improvement: added back a few more missing libraries needed for certain user customizations. Bug Fix: Support normal expansion of array when Parity is not installed. Changes from 4.3-beta2 to 4.3-beta3 ----------------------------------- Bug fix: Turn off user share filesystem debugging output accidentally left on - doh! Changes from 4.3-beta1 to 4.3-beta2 ----------------------------------- Bug fix: Restore missing 'installpkg' script. Bug fix: Fixed possible user share crash if top-level disk directories contain ordinary files. Bug fix: Fixed warning message generated by 'find' when searching user shares. Bug fix: Fixed problem reporting correct hostname to DHCP server. Changes from 4.2.3 to 4.3-beta1 ------------------------------- Improvement: With user shares enabled, directories/files created directly in a disk share will show up immediately in the correct user share. Improvement: Included 'vsftpd' server. Improvement: Upgrade to linux kernel 2.6.24.3. Improvement: Enable kernel support of up to 4GB of memory. Upgrade Instructions (Please Read Carefully) ============================================ If you are currently running unRAID Server 4.2-beta1 or higher (including 4.2.x 'final'), please copy the following files from the new release to the root of your Flash device: bzimage bzroot If you are currently running unRAID server 4.0 or 4.1, please copy the following files from the new release to the root of your Flash device: bzimage bzroot syslinux.cfg menu.c32 memtest This can be done either by plugging the Flash into your PC or, by 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 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

Yes and yes.

BLKMGK- For the segfault problem, you might need to manually edit the 'config/share.cfg' file on the Flash (/boot/config/share.cfg via telnet), and disable user shares. Change the line that reads: shareUser=e to shareUser=- Next, reboot and system should come up again without user shares enabled. Now, I need to see the top level directories of your disks. From a telnet session, type this: ls /mnt There will be an entry in there for each of your data disks. You need to do this for each disk: ls -a /mnt/disk1 ls -a /mnt/disk2 etc. Do this for each disk. Capture the screen output and send to me: [email protected] For your parity disk temperature problem, please try the 'bzroot' test file in the post above to ReneV & let me know if that solves it for you. DPO and FUA are bits in a SCSI write command that give "hints" to the disk drive about the nature of the data being written. These are just informational messages of no consequence.

Found your email & replied...

Along these lines... been experimenting with a feature that lets you see shares from one unRAID server in the name space of another unRAID server. For example, suppose you have this: //tower1/Videos/a bunch of files //tower2/Vidoes/another bunch of files Set up a special config in Tower3 to see: //tower3/Videos/aggregate of files from tower1, tower2, and tower3 Kinda slow... but maybe useful.

Do you have any more info about this? There have been a handful of customers who have reported a similar problem & I'm wondering if it's perhaps due to our recent move to a new host provider.

Yes. No.

Correct.

Let's say you have a user share named "Videos", which you allow to span disk1,disk2,disk3, and the cache disk is enabled for it. On the Shares page you might have this: Share name: Videos Comments: Home movies Allocation method: High-water Split level: 1 Included disk(s): disk1-3 Excluded disks(s): Use cache disk: Yes Export mode: Export read/write Scenario 1 Let's say I navigate to the Videos share under My Network Places and create a folder called "Spring 2008", and then copy the file "Aspen.avi" to that directory. Since the cache disk is enabled for this share, system will: a) create "Videos" directory on cache disk (if not already there) b) create "Spring 2008" directory on cache disk (if not already there) c) create "Aspen.avi" on cache disk Later, whenever the mover is schedule to run, "Aspen.avi" will be copied to either disk1,disk2, or disk3, and then removed from cache disk. The directory structure on the cache disk will remain however. This is all transparent to accessing this folder structure via "Video" share under My Network Places - at all times the folder structure will be visible no matter which disk the folders/files actually reside on. Exception: if the cache disk is already full (meaning remaining free space is less than "Min free space" setting), then we don't use the cache disk & the folders/files will get created on the share normally - that is, according to it's allocation method. Scenario 2 Same config, except that under "Export settings" on the Shares page, I also have "Disk shares" set to "Export read/write". In this case, in addition to seeing all my user shares under My Network Places, I will also see all the disk shares (i.e., "disk1", "disk2", etc.), as well as the cache disk as "cache". I then navigate to the cache disk share "Videos/Spring 2008" folder, and directly copy "Vale.avi" to this folder. Now if I go back and click on the "Videos" share, I will immediately see that "Vale.avi" is in the "Spring 2008" folder there. Note that I can directly write to any of the disk shares in this manner and the folders/files will immediate show up in the appropriate user share [but see *note below]. Scenario 3 Same config, except the Video user share export setting is set to "read-only". In this case, I can not directly write to the user share, but I can still write to disk that is part of the user share (including the cache disk). In other words, the user share export setting only applies when accessing files through that share. If you wanted to totally disable writes, in addition to setting the user share write-only, you would also have to set the global "Disk export" setting to "write-only" or "don't export". *note: here's how 'duplicates' are treated: A 'duplicate' is when the same file exists in identical folder structures on two or more disks. For example, suppose you already have this: /disk2/Videos/Spring 2008/Breckenridge.avi and then you create the same named file on the cache disk: /cache/Videos/Spring 2008/Breckenridge.avi When you navigate to the Videos share via My Network Places, you will only see a single file named "Breckenridge.avi" under the "Spring 2008" directory. The version you see (and would be accessed) is the one on the lowest numbered disk, where the cache disk is lower than any data disk (ie, as if it were "disk0"). So you would be accessing the version of Breckenridge.avi which is on the cache disk in this case. Later when the mover decides to move Breckenridge.avi, there are three possibilities: 1. If, according to share allocation method, disk1 is the one picked to be the target, then Breckenridge.avi will get moved to disk1 and you will still have a duplicate. But since disk1 is lower than disk2, you would see the version on disk1. 2. If, according to share allocation method, disk2 is the one picked to be the target, then Breckenridge.avi will replace the one on disk2 (note it's possible to configure the 'mv' command in the mover to not replace existing files - if set up like this then the file will remain on the cache disk). 3. If, according to share allocation method, disk3 is the one picked to be the target, then Breckenridge.avi will get moved to disk3 and you will still have a duplicate. But since disk2 is lower than disk3, you would see the old version of Breckenridge.avi instead of the new one. Because of the problems with duplicates, we strongly encourage you to not have duplicates!

ReneV- If you don't mind, please download this bzroot zip file, unzip and replace your current bzroot file on the Flash & let me know if this fixes the problem.

Download. Fixes 'hang' that can happen during start-up if no WINS server on network. Please refer to the 4.3-beta4 announcement regarding description of new features. unRAID Server 4.3-beta5 Release Notes Upgrade Instructions (Please Read Carefully) -------------------------------------------- If you are currently running unRAID Server 4.2-beta1 or higher (including 4.2.x 'final'), please copy the following files from the new release to the root of your Flash device: bzimage bzroot If you are currently running unRAID server 4.0 or 4.1, please copy the following files from the new release to the root of your Flash device: bzimage bzroot syslinux.cfg menu.c32 memtest This can be done either by plugging the Flash into your PC or, by 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 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.3-beta4 to 4.3-beta5 ----------------------------------- Bug Fix: Fix 'hang' that may occur starting syslogd. Improvement: Add 'sync' as last step in 'mover' script Changes from 4.3-beta3 to 4.3-beta4 ----------------------------------- New feature: cache disk support. Improvement: enable SMART before reading disk temperature. Improvement: upgrade from linux kernel 2.6.24.3 to 2.6.24.4 (refer to http://lwn.net/Articles/274741). Improvement: upgrade from Samba 3.0.28 to Samba 3.0.28a (addresses some Vista issues, refer to http://us1.samba.org/samba/history/samba-3.0.28a.html). Improvement: added back a few more missing libraries needed for certain user customizations. Bug Fix: Support normal expansion of array when Parity is not installed.

Then each 'mv' command executed by the mover will fail and the file(s) will stay put on the cache disk.

If your user shares are read-only, then no objects will get created via that share on any disk. If disk shares are write-enabled, then you could write to a user share directory on the cache disk, or any other disk. Put another way, the access controls on a user share only apply to access via Samba (ie, Windows Networking). If you have set the 'excluded disks' string for a share to name all the disks, then the mover will get an error on every file it tries to move.

Right, except that you don't add the Cache disk to the "Included disks". Instead there's a drop down box for each share that enables or disables the cache disk for that share. At first we did implement it exactly as you describe, using the name "disk0" instead of "cache", but there are other reasons why this wasn't the best way to do it.

Correct. Correct. Actually you don't have to explicitly copy anything to the cache disk. If the cache disk is enabled for a share, then when you create any new file or directory on that share, the system will try to create it on the cache disk first. The only reason it wouldn't create it on the cache disk is if there is not enough free space left on the cache disk. There are 3 main reasons why we implemented this feature: 1. To widen the bottleneck when writing several media streams to the server simultaneously, e.g., multiple HiDef video feeds. 2. To speed up initial loading of the array. Assuming a 1TB cache disk, and average network throughput of 50MB/sec, it would take a little over 5 hours to fill up the cache disk (and then probably 15 to drain it to the array). 3. To provide a place to put a swap file.

Good idea.