unRAID Server Release 5.0-beta13 Available

[limetech]

Linux Kernel 3.1.1 is out and contains a lot of fixes. One in particular is of vital importance for LSI hardware users. I dont know if this is causing the massive headaches in Beta 13 or not, but it can't make things any worse than they are now (completely unusable).

 

http://www.kernel.org/pub/linux/kernel/v3.0/ChangeLog-3.1.1

commit 218782d30177214893625e8d6523191caa5e023b

Author: [email protected] <[email protected]>

Date:   Fri Oct 21 10:06:33 2011 +0530

 

    mpt2sas: Fix for system hang when discovery in progress

   

    commit 0167ac67ff6f35bf2364f7672c8012b0cd40277f upstream.

   

    Fix for issue : While discovery is in progress, hot unplug and hot plug of

    enclosure connected to the controller card is causing system to hang.

   

    When a device is in the process of being detected at driver load time then

    if it is removed, the device that is no longer present will not be added

    to the list. So the code in _scsih_probe_sas() is rearranged as such so

    the devices that failed to be detected are not added to the list.

 

You're right, BRiT, this fix appear to handle those terrible mptsas detection errors. I'm hopping that Tom will update v5 soon.

Working on it.  Also working on updating forum to SMF 2.

[peter_sm]

Linux Kernel 3.1.1 is out and contains a lot of fixes. One in particular is of vital importance for LSI hardware users. I dont know if this is causing the massive headaches in Beta 13 or not, but it can't make things any worse than they are now (completely unusable).

 

http://www.kernel.org/pub/linux/kernel/v3.0/ChangeLog-3.1.1

commit 218782d30177214893625e8d6523191caa5e023b

Author: [email protected] <[email protected]>

Date:   Fri Oct 21 10:06:33 2011 +0530

 

    mpt2sas: Fix for system hang when discovery in progress

   

    commit 0167ac67ff6f35bf2364f7672c8012b0cd40277f upstream.

   

    Fix for issue : While discovery is in progress, hot unplug and hot plug of

    enclosure connected to the controller card is causing system to hang.

   

    When a device is in the process of being detected at driver load time then

    if it is removed, the device that is no longer present will not be added

    to the list. So the code in _scsih_probe_sas() is rearranged as such so

    the devices that failed to be detected are not added to the list.

 

You're right, BRiT, this fix appear to handle those terrible mptsas detection errors. I'm hopping that Tom will update v5 soon.

Working on it.  Also working on updating forum to SMF 2.

 

Tom,

 

Did you see any issue about NFS? or perhaps is on our side (medi player)

 

//Peter

[PeterB]

...this fix appear to handle those terrible mptsas detection errors.

 

The Change Log also lists several fixes to nfs - perhaps it will cure the nfs hangs too!

[comfox]

Anyone here able to take a look at the following thread and help out with the problem? 

 

http://lime-technology.com/forum/index.php?topic=16521.0

 

My buddy has been using unRAID on my advice for a few months now and can't seem to get it to work.  Joe L or any other Guru please help 

[stomp]

Personnaly I experienced no change regarding NFS when upgrading from 12a to 13. However I don't know about previous version performances.

[PeterB]

So you are saying that nfs is usable for you?  For some of us, nfs transfers simply hang after a few seconds.  I have reverted to b11 for a working nfs.

[peter_sm]

I will do the same and test with B11, hope we have a new beta today.

 

//Peter

[peter_sm]

I will do the same and test with B11, hope we have a new beta today.

 

//Peter

 

Confirmed, B11 works flawless over NFS, none of the issue I have on B13 exist.

EDIT

 

 

Verified with my Media Player, (For me, NFS is only used for streaming high bit-rate BD and MKV)

 

//Peter

 

 

[stomp]

So you are saying that nfs is usable for you?  For some of us, nfs transfers simply hang after a few seconds.  I have reverted to b11 for a working nfs.

 

I'm only using NFS for streaming with my media player though...

[WizADSL]

Based on my research you need multy lane breakout cables becouse the reverse variaty is for backplain use.

 

This is the cable I am using http://www.newegg.com/Product/Product.aspx?Item=N82E16816116098

 

As far as I can tell it is the right one for use with an AOC-SASLP-MV8 and bare drives.

[Johnm]

Based on my research you need multy lane breakout cables becouse the reverse variaty is for backplain use.

 

This is the cable I am using http://www.newegg.com/Product/Product.aspx?Item=N82E16816116098

 

As far as I can tell it is the right one for use with an AOC-SASLP-MV8 and bare drives.

 

Yes, that is the correct one.

[vl1969]

Hi, this is my first build so here it goes...

 

I have build out my server (stats are below including links in case some one needs more info or would like to get the parts)

 

I am using the latest 5.13 build as the MD is Realteck 8111E  chipset for LAN and I do not have plig-in card.

 

my issue is that I can not get to my server from the web.

 

this is the basic build, and nothing extra have been installed.

the only files on the flash  drive are from the limetech posted zip for the build.

 

it boots, it runs the unraid, I can ping it, I get the IP address (changed it to static IP)

I can Tellnet with PUTTY

 

can run the " ifconfig eth0"  get the screen full of info including my IP etc.

 

BUT no web.

 

I will post the log file tonight (it was very late last night when I booted up and I just was too tired to mess with logs and stuff)  but if anyone have any additional things that they might think I need to run for tests and troubleshooting please let me know.

 

PS>> I am only booting with one (1) unformatted  uncleared HDD as I am not finish with my case modes so not all HDD are installed. but I do not think this could cause issues with booting unRaid(can it?)

 

I am running all windows 7 64bit PC (2+)

my main PC is win 7 Ultimate 64bit fresh build as I had an HD crash

my 2nd is HTPC  windows 7 home 64bit (this is where all my RIPS are now)

 

my stats are :

 

NO CASE STATS :-),  I am using an old full tower case that I am trying to mode to make it nice

some paint here, some tweaks there, nothing serious but to make all my things fit and make sure I have room for future modes.

 

MB:  M5A87 Socket AM3+ 870 ATX AMD Motherboard ($94.99) (http://www.microcenter.com/single_product_results.phtml?product_id=0365861)

CPU:  PHENOM II X4 840 Boxed Processor HDX840WFGMBOX ($59.99)(http://www.microcenter.com/single_product_results.phtml?product_id=0371961)

PSU:  Silencer 760 Watt ATX Power Supply (89.99)(http://www.microcenter.com/single_product_results.phtml?product_id=0358411)

RAM:  HyperX blu 8GB DDR3-1600 (PC3-12800) CL9 Dual Channel Desktop Memory Kit ($39.99)(Two 4GB Memory Modules)(http://www.microcenter.com/single_product_results.phtml?product_id=0360527)

 

HDD:  Barracuda LP 2TB 5,900 RPM SATA 3Gb/s 3.5" Internal Hard Drive ST320005N4A1AS-RK (4)x($74.99 bought it before the price hike :-P )(http://www.microcenter.com/single_product_results.phtml?product_id=0334239)

 

 

 

[Frank1940]

Hi, this is my first build so here it goes...

 

I have build out my server (stats are below including links in case some one needs more info or would like to get the parts)

 

I am using the latest 5.13 build as the MD is Realteck 8111E  chipset for LAN and I do not have plig-in card.

 

my issue is that I can not get to my server from the web.

 

this is the basic build, and nothing extra have been installed.

the only files on the flash  drive are from the limetech posted zip for the build.

 

it boots, it runs the unraid, I can ping it, I get the IP address (changed it to static IP)

I can Tellnet with PUTTY

....

BUT no web.

 

 

 

You didn't give much information about how you attempted to access your unRAID box.  Since you changed to a static IP address, it may be difficult for you to get to the box using \\TOWER.  I would suggest that you try using the IP address in your bowser URL window.  (Many routers do not list any device to which the router has not assigned the IP address.  This can also be the case even when you have reserved the address in the router table.) 

 

Hope this hopes a bit....

[vl1969]

Hi, this is my first build so here it goes...

 

I have build out my server (stats are below including links in case some one needs more info or would like to get the parts)

 

I am using the latest 5.13 build as the MD is Realteck 8111E  chipset for LAN and I do not have plig-in card.

 

my issue is that I can not get to my server from the web.

 

this is the basic build, and nothing extra have been installed.

the only files on the flash  drive are from the limetech posted zip for the build.

 

it boots, it runs the unraid, I can ping it, I get the IP address (changed it to static IP)

I can Tellnet with PUTTY

....

BUT no web.

 

 

 

You didn't give much information about how you attempted to access your unRAID box.  Since you changed to a static IP address, it may be difficult for you to get to the box using \\TOWER.  I would suggest that you try using the IP address in your bowser URL window.  (Many routers do not list any device to which the router has not assigned the IP address.  This can also be the case even when you have reserved the address in the router table.)  

 

Hope this hopes a bit....

 

thanks Frank, sorry I was not clear in my post, but I did try it all the possible ways I could think of.

 

I booted first as DHCP client and try  "\\Tower" / "//Tower"  // "\\tower" and any permutations I

could think of,  I then tried "\\IP_ADDRESS"

 

I then set it to static IP and repeat the process.  nothing worked.

 

[MOVED] here [http://lime-technology.com/forum/index.php?topic=16632.0]

 

 

[prostuff1]

Hi, this is my first build so here it goes...

 

I have build out my server (stats are below including links in case some one needs more info or would like to get the parts)

 

I am using the latest 5.13 build as the MD is Realteck 8111E  chipset for LAN and I do not have plig-in card.

 

my issue is that I can not get to my server from the web.

 

this is the basic build, and nothing extra have been installed.

the only files on the flash  drive are from the limetech posted zip for the build.

 

it boots, it runs the unraid, I can ping it, I get the IP address (changed it to static IP)

I can Tellnet with PUTTY

....

BUT no web.

 

 

 

You didn't give much information about how you attempted to access your unRAID box.  Since you changed to a static IP address, it may be difficult for you to get to the box using \\TOWER.  I would suggest that you try using the IP address in your bowser URL window.  (Many routers do not list any device to which the router has not assigned the IP address.  This can also be the case even when you have reserved the address in the router table.) 

 

Hope this hopes a bit....

 

thanks Frank, sorry I was not clear in my post, but I did try it all the possible ways I could think of.

 

I booted first as DHCP client and try  "\\Tower" / "//Tower"  // "\\tower" and any permutations I

could think of,  I then tried "\\IP_ADDRESS"

 

I then set it to static IP and repeat the process.  nothing worked.

 

 

 

please take this to the general support forum

[vl1969]

Hi, this is my first build so here it goes...

 

I have build out my server (stats are below including links in case some one needs more info or would like to get the parts)

 

I am using the latest 5.13 build as the MD is Realteck 8111E  chipset for LAN and I do not have plig-in card.

 

my issue is that I can not get to my server from the web.

 

this is the basic build, and nothing extra have been installed.

the only files on the flash  drive are from the limetech posted zip for the build.

 

it boots, it runs the unraid, I can ping it, I get the IP address (changed it to static IP)

I can Tellnet with PUTTY

....

BUT no web.

 

 

 

You didn't give much information about how you attempted to access your unRAID box.  Since you changed to a static IP address, it may be difficult for you to get to the box using \\TOWER.  I would suggest that you try using the IP address in your bowser URL window.  (Many routers do not list any device to which the router has not assigned the IP address.  This can also be the case even when you have reserved the address in the router table.) 

 

Hope this hopes a bit....

 

thanks Frank, sorry I was not clear in my post, but I did try it all the possible ways I could think of.

 

I booted first as DHCP client and try  "\\Tower" / "//Tower"  // "\\tower" and any permutations I

could think of,  I then tried "\\IP_ADDRESS"

 

I then set it to static IP and repeat the process.  nothing worked.

 

 

 

please take this to the general support forum

 

OK, so do I just repost it in General topics or is there a way for me to move this post there?

 

I thought  that since I was running a 5.13 beta and the initial post from limetech said to report any issues I post it here first...

 

if I was wrong, my bad...

[prostuff1]

not so much wrong or bad on your part.

 

since you can telnet into the machine it appears to be running.  I don't think this is related to 5.0b13 so don't want the thread cluttered.

 

Just start a new post there and we can pick up the discussion again.

[WizADSL]

Based on my research you need multy lane breakout cables becouse the reverse variaty is for backplain use.

 

This is the cable I am using http://www.newegg.com/Product/Product.aspx?Item=N82E16816116098

 

As far as I can tell it is the right one for use with an AOC-SASLP-MV8 and bare drives.

 

Yes, that is the correct one.

 

Ok, good.  Here is my previous post about errors that I am receiving if using the AOC-SASLP-MV8:

 

I just added an AOC-SASLP-MV8 to my system in order to consolidate several 2-port sata controllers, I was able to boot and start the array, but the syslog was being FILLED by lines like the ones below.  I'm talking on the order of 1 gig of syslog in the space of 10 minutes.  6 of my drives are on the MB controller and the other 5 where put on the AOC-SASLP-MV8, bios version is 3.1.0.22.  Initially I had a drive red-balled because I didn't have one of the cables seated properly but the syslog messages were always present.  I am using 2 reverse breakout cables to hook up drives.

 

Nov 5 02:04:39 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2108:phy 3 ctrl sts=0x00199800.

Nov 5 02:04:39 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2110:phy 3 irq sts = 0x01000000

Nov 5 02:04:39 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2108:phy 3 ctrl sts=0x00199800.

Nov 5 02:04:39 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2110:phy 3 irq sts = 0x01000000

Nov 5 02:04:39 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2108:phy 3 ctrl sts=0x00199800.

Nov 5 02:04:39 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2110:phy 3 irq sts = 0x01000000

[mejutty]

Not to sure what sort of issue this is but I completed a parity check, shutdown replaced a 1.5tb drive with a new 3tb drive powered on the array allocated the new drive (it was already precleared) let it rebuild,  once it finished rebuilding it now states that that last parity check took place 15296 days ago with no errors.

 

Last 2 syslogs attached one taken after parity check before drive replacement the other as of now after drive rebuild.

syslog.zip

[Interstellar]

Still getting network errors :

 

Nov 17 13:09:50 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network)
Nov 17 13:10:38 Tower logger: Thu Nov 17 12:54:36 GMT 2011 - Hard Drives active, resetting counter
Nov 17 13:11:38 Tower logger: Thu Nov 17 12:54:36 GMT 2011 - Hard Drives active, resetting counter
Nov 17 13:13:38 Tower last message repeated 2 times
Nov 17 13:15:38 Tower last message repeated 2 times
Nov 17 13:16:38 Tower logger: Thu Nov 17 12:54:36 GMT 2011 - Hard Drives active, resetting counter
Nov 17 13:17:06 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network)
Nov 17 13:17:24 Tower last message repeated 2 times
Nov 17 13:17:38 Tower logger: Thu Nov 17 12:54:36 GMT 2011 - Hard Drives active, resetting counter
Nov 17 13:18:38 Tower logger: Thu Nov 17 12:54:36 GMT 2011 - Hard Drives active, resetting counter
Nov 17 13:20:39 Tower last message repeated 2 times
Nov 17 13:20:54 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network)
Nov 17 13:21:39 Tower logger: Thu Nov 17 12:54:36 GMT 2011 - Hard Drives active, resetting counter
Nov 17 13:22:22 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network)
Nov 17 13:22:39 Tower logger: Thu Nov 17 12:54:36 GMT 2011 - Hard Drives active, resetting counter
Nov 17 13:23:39 Tower logger: Thu Nov 17 12:54:36 GMT 2011 - Hard Drives active, resetting counter
Nov 17 13:24:38 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network)
Nov 17 13:24:39 Tower logger: Thu Nov 17 12:54:36 GMT 2011 - Hard Drives active, resetting counter
Nov 17 13:25:39 Tower logger: Thu Nov 17 12:54:36 GMT 2011 - Hard Drives active, resetting counter
Nov 17 13:26:39 Tower logger: Thu Nov 17 12:54:36 GMT 2011 - Hard Drives active, resetting counter
Nov 17 13:27:14 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network)
Nov 17 13:27:17 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network)
Nov 17 13:27:39 Tower logger: Thu Nov 17 12:54:36 GMT 2011 - Hard Drives active, resetting counter
Nov 17 13:28:39 Tower logger: Thu Nov 17 12:54:36 GMT 2011 - Hard Drives active, resetting counter
Nov 17 13:30:39 Tower last message repeated 2 times
Nov 17 13:31:40 Tower logger: Thu Nov 17 12:54:36 GMT 2011 - Hard Drives active, resetting counter
Nov 17 13:33:40 Tower last message repeated 2 times
Nov 17 13:34:27 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network)

 

Ideas?

 

Will attached syslog in bait.

 

syslog-2011-11-17.txt

[Joe L.]

Not to sure what sort of issue this is but I completed a parity check, shutdown replaced a 1.5tb drive with a new 3tb drive powered on the array allocated the new drive (it was already precleared) let it rebuild,  once it finished rebuilding it now states that that last parity check took place 15296 days ago with no errors.

 

Last 2 syslogs attached one taken after parity check before drive replacement the other as of now after drive rebuild.

The process of initially calculating parity and riting to the parity drive is 99% identical to re-constructing a replaced disk, the only difference is the drive being written to.

 

Apparently there is only one "time-stamp" variable involved, and its shared use results in the erroneous duration since the last parity check. 

(unless the time you last did a parity check was in 1970 ?)

 

Yes, it is a bug.  Not one that affects much, but it makes your array sound so much older than it actually is.

 

Joe L.

[SlowNIC]

Another user chiming in on the LSI mptsas spinup issue.

Thanks.

 

[Interstellar]

Still getting network errors :

 

Nov 17 13:09:50 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network)
Nov 17 13:10:38 Tower logger: Thu Nov 17 12:54:36 GMT 2011 - Hard Drives active, resetting counter
Nov 17 13:11:38 Tower logger: Thu Nov 17 12:54:36 GMT 2011 - Hard Drives active, resetting counter
Nov 17 13:13:38 Tower last message repeated 2 times
Nov 17 13:15:38 Tower last message repeated 2 times
Nov 17 13:16:38 Tower logger: Thu Nov 17 12:54:36 GMT 2011 - Hard Drives active, resetting counter
Nov 17 13:17:06 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network)
Nov 17 13:17:24 Tower last message repeated 2 times
Nov 17 13:17:38 Tower logger: Thu Nov 17 12:54:36 GMT 2011 - Hard Drives active, resetting counter
Nov 17 13:18:38 Tower logger: Thu Nov 17 12:54:36 GMT 2011 - Hard Drives active, resetting counter
Nov 17 13:20:39 Tower last message repeated 2 times
Nov 17 13:20:54 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network)
Nov 17 13:21:39 Tower logger: Thu Nov 17 12:54:36 GMT 2011 - Hard Drives active, resetting counter
Nov 17 13:22:22 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network)
Nov 17 13:22:39 Tower logger: Thu Nov 17 12:54:36 GMT 2011 - Hard Drives active, resetting counter
Nov 17 13:23:39 Tower logger: Thu Nov 17 12:54:36 GMT 2011 - Hard Drives active, resetting counter
Nov 17 13:24:38 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network)
Nov 17 13:24:39 Tower logger: Thu Nov 17 12:54:36 GMT 2011 - Hard Drives active, resetting counter
Nov 17 13:25:39 Tower logger: Thu Nov 17 12:54:36 GMT 2011 - Hard Drives active, resetting counter
Nov 17 13:26:39 Tower logger: Thu Nov 17 12:54:36 GMT 2011 - Hard Drives active, resetting counter
Nov 17 13:27:14 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network)
Nov 17 13:27:17 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network)
Nov 17 13:27:39 Tower logger: Thu Nov 17 12:54:36 GMT 2011 - Hard Drives active, resetting counter
Nov 17 13:28:39 Tower logger: Thu Nov 17 12:54:36 GMT 2011 - Hard Drives active, resetting counter
Nov 17 13:30:39 Tower last message repeated 2 times
Nov 17 13:31:40 Tower logger: Thu Nov 17 12:54:36 GMT 2011 - Hard Drives active, resetting counter
Nov 17 13:33:40 Tower last message repeated 2 times
Nov 17 13:34:27 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network)

 

Ideas?

 

Will attached syslog in bait.

 

 

 

Went back to 12a, all is good now!

[Thornwood]

I installed the day it came out and I have not had a single problem. Great Job!

[WallaceTech]

NFS is really bad.

 

I have just hooked my VMware server up to use it as a datastore. after about an hour the VMware box loses connection to unRaid. I have to reboot unRaid as just rebooting the VMware box does nothing.

 

The disk that VMware is on is told not to spin down so i know its not that.