unRAID Server Release 5.0-beta13 Available

[Johnm]

False alarm on the M1015...

EDIT: there is an issue with the m1015 driver../edit.

Ok, I am not sure what went wrong there.
i downgraded back to 12 and still had no card. (I saw it go past in the system post though)
cut the power for a bit and I tore open the server reseated all the cards.
rebooted to b12 natively. It worked fine (minus the fact i forgot my datastore drives are  SSD's that report temps at 128c and shutdown the box),

I upgraded back to B13. it booted fine natively.

Booted back into ESXi and booted B13 as a guest... no issues this time.. ~shrug~ gremlins..
i think that is the first time in months that box has been powered off or rebooted.

updated syslog, not that it is needed...

[One2go]

Also included in here is network bonding support.  Actually I only enabled it in the kernel and included the 'ifenslave' command.  Still working on GUI support, but some users have been able to get it working.  Here's an overview:
http://www.sgvulcan.com/network-interface-bonding-in-slackware-version-13-1/

Does this allow me to combine server 1 that has the Share "Movies" with a second server that also has the share "Movies" to appear as a combined share \\SomeServer\Movies\?

[bubbaQ]

Does this allow me to combine server 1 that has the Share "Movies" with a second server that also has the share "Movies" to appear as a combined share \\SomeServer\Movies\?

No, it lets you use 2 network cards in the server so you have (theoretically) twice as much bandwidth in/out of the server.

[limetech]

Also included in here is network bonding support.  Actually I only enabled it in the kernel and included the 'ifenslave' command.  Still working on GUI support, but some users have been able to get it working.  Here's an overview:
http://www.sgvulcan.com/network-interface-bonding-in-slackware-version-13-1/

Does this allow me to combine server 1 that has the Share "Movies" with a second server that also has the share "Movies" to appear as a combined share \\SomeServer\Movies\?

No, but what do you think about that feature (of combining shares from separate servers like that)?

[limetech]

Does this allow me to combine server 1 that has the Share "Movies" with a second server that also has the share "Movies" to appear as a combined share \\SomeServer\Movies\?

No, it lets you use 2 network cards in the server so you have (theoretically) twice as much bandwidth in/out of the server.

Or redundant links.

[Johnm]

No, but what do you think about that feature (of combining shares from separate servers like that)?

Interesting.. an unRAID Server array...
I can see how it would be handy if you have for example 3 HP microservers.
I don't think I would use it personally. at least not at this point. However, once i fill my array, that might be pretty cool.

You could sell an "expansion license" for maybe half price (with an option to upgrade to a full) that wont work as a stand alone server.

[Auggie]

Samba throughput (large file copy) is improved 15 to 20%.

Graph is 2.5GB file copy to unprotected disk (no parity).... solid 480 mbps.

Is this under SMB2 or SMB1?

[Johnm]

Possible issue or Possible coincidence..

A drive redballed on me within 30 min of running beta13. it came up doing a parity check on first boot, so I let it run.

the drive itself has a clean SMART report. I think this drive is on my LSI card not my MV8.
This drive just got precleared a few days ago.

SMART report

Code: [Select]

=== START OF INFORMATION SECTION ===
Device Model:     Hitachi HDS5C3030ALA630
Serial Number:    MJ1321YNG14A6A
Firmware Version: MEAOA580
User Capacity:    3,000,592,982,016 bytes
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Fri Oct 28 21:57:49 2011 CDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x84) Offline data collection activity
was suspended by an interrupting command from host.
Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: (38769) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: (   1) minutes.
Extended self-test routine
recommended polling time: ( 255) minutes.
SCT capabilities:       (0x003d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   100   100   016    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   135   135   054    Pre-fail  Offline      -       107
  3 Spin_Up_Time            0x0007   129   129   024    Pre-fail  Always       -       543 (Average 542)
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       149
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   132   132   020    Pre-fail  Offline      -       32
  9 Power_On_Hours          0x0012   100   100   000    Old_age   Always       -       2520
 10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       99
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       189
193 Load_Cycle_Count        0x0012   100   100   000    Old_age   Always       -       189
194 Temperature_Celsius     0x0002   200   200   000    Old_age   Always       -       30 (Min/Max 23/39)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       0

General Purpose Logging (GPL) feature set supported
General Purpose Log Directory Version 1
SMART           Log Directory Version 1 [multi-sector log support]
GP/S  Log at address 0x00 has    1 sectors [Log Directory]
SMART Log at address 0x01 has    1 sectors [Summary SMART error log]
GP    Log at address 0x03 has    1 sectors [Ext. Comprehensive SMART error log]
GP    Log at address 0x04 has    7 sectors [Device Statistics]
SMART Log at address 0x06 has    1 sectors [SMART self-test log]
GP    Log at address 0x07 has    1 sectors [Extended self-test log]
GP    Log at address 0x08 has    1 sectors [Reserved]
SMART Log at address 0x09 has    1 sectors [Selective self-test log]
GP    Log at address 0x10 has    1 sectors [NCQ Command Error]
GP    Log at address 0x11 has    1 sectors [SATA Phy Event Counters]
GP    Log at address 0x20 has    1 sectors [Streaming performance log]
GP    Log at address 0x21 has    1 sectors [Write stream error log]
GP    Log at address 0x22 has    1 sectors [Read stream error log]
GP/S  Log at address 0x80 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x81 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x82 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x83 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x84 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x85 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x86 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x87 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x88 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x89 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x8a has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x8b has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x8c has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x8d has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x8e has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x8f has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x90 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x91 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x92 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x93 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x94 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x95 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x96 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x97 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x98 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x99 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x9a has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x9b has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x9c has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x9d has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x9e has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x9f has   16 sectors [Host vendor specific log]
GP/S  Log at address 0xe0 has    1 sectors [SCT Command/Status]
GP/S  Log at address 0xe1 has    1 sectors [SCT Data Transfer]

SMART Extended Comprehensive Error Log Version: 1 (1 sectors)
No Errors Logged

SMART Extended Self-test Log Version: 1 (1 sectors)
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

SCT Status Version:                  3
SCT Version (vendor specific):       256 (0x0100)
SCT Support Level:                   1
Device State:                        SMART Off-line Data Collection executing in background (4)
Current Temperature:                    30 Celsius
Power Cycle Min/Max Temperature:     28/34 Celsius
Lifetime    Min/Max Temperature:     23/39 Celsius
Under/Over Temperature Limit Count:   0/0
SCT Temperature History Version:     2
Temperature Sampling Period:         1 minute
Temperature Logging Interval:        1 minute
Min/Max recommended Temperature:      0/60 Celsius
Min/Max Temperature Limit:           -40/70 Celsius
Temperature History Size (Index):    128 (34)

Index    Estimated Time   Temperature Celsius
  35    2011-10-28 19:50    28  *********
 ...    ..(120 skipped).    ..  *********
  28    2011-10-28 21:51    28  *********
  29    2011-10-28 21:52    29  **********
 ...    ..(  2 skipped).    ..  **********
  32    2011-10-28 21:55    29  **********
  33    2011-10-28 21:56    30  ***********
  34    2011-10-28 21:57    30  ***********

SCT Error Recovery Control:
           Read: Disabled
          Write: Disabled

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x0001  2            0  Command failed due to ICRC error
0x0002  2            0  R_ERR response for data FIS
0x0003  2            0  R_ERR response for device-to-host data FIS
0x0004  2            0  R_ERR response for host-to-device data FIS
0x0005  2            0  R_ERR response for non-data FIS
0x0006  2            0  R_ERR response for device-to-host non-data FIS
0x0007  2            0  R_ERR response for host-to-device non-data FIS
0x0009  2            3  Transition from drive PhyRdy to drive PhyNRdy
0x000a  2            3  Device-to-host register FISes sent due to a COMRESET
0x000b  2            0  CRC errors within host-to-device FIS
0x000d  2            0  Non-CRC errors within host-to-device FIS
the Power-Off_Retract_Count bothers me, but it is not fatal. it just points out a possible backplane connection issue.



syslog attached.

I am going to rip the server open, swap out the LSI card for another one, swap that drive for a brand new out of the box  (precleared) 3TB and let it rebuild. it is on a sas backplane so there is not to much cable monkeying i can do. i will pull the backplane and inspect it.
I'll post any findings.

[One2go]

I would love to see something that allows separate servers to present a unified share. Same reason for what was already mentioned, as I toyed with the idea of turning a HP microserver into a server running a Beta version, but then it needs to be able to get integrated into the overall network.

[JustinAiken]

No, but what do you think about that feature (of combining shares from separate servers like that)?

I would love to see this... 3TB drives are still too much more expensive than 2TB's for me, and once my server hits full this is exactly the type of solution I'd like to see...

Plus it would be cool to have a "mini-server" that was small enough to take out of house, but joined the server at home, to keep the most vital data on...

Anyways, happy to see movement on 5.0, thanks limetech!

[purko]

The `/root/mkmbr` that's included in 5.0-beta13 doesn't work with 3TB drives, right?
Will it be updated for 3TB?  Or maybe a similar tool that does the same job for 3TB drives?

[limetech]

The `/root/mkmbr` that's included in 5.0-beta13 doesn't work with 3TB drives, right?
Will it be updated for 3TB?  Or maybe a similar tool that does the same job for 3TB drives?

Right, I forgot about the utility.  It was created to help deal with "4K-aligned" hard drives during that code transition period, why do you still want to use it?

[flambot]

Also included in here is network bonding support.  Actually I only enabled it in the kernel and included the 'ifenslave' command.  Still working on GUI support, but some users have been able to get it working.  Here's an overview:
http://www.sgvulcan.com/network-interface-bonding-in-slackware-version-13-1/

Does this allow me to combine server 1 that has the Share "Movies" with a second server that also has the share "Movies" to appear as a combined share \\SomeServer\Movies\?

No, but what do you think about that feature (of combining shares from separate servers like that)?

I'd also like to see this. While I don't have two servers currently, I see myself with a 2nd build in the future.

[prostuff1]

No, but what do you think about that feature (of combining shares from separate servers like that)?

I would love to see this... 3TB drives are still too much more expensive than 2TB's for me, and once my server hits full this is exactly the type of solution I'd like to see...

Plus it would be cool to have a "mini-server" that was small enough to take out of house, but joined the server at home, to keep the most vital data on...

Anyways, happy to see movement on 5.0, thanks limetech!

Joining them on the local network would be cool and feasible... doing it over an Internet connection from outside the local network... that would be asking for a support nightmare.

[peter_sm]

Is this something to taking some action for?

Code: [Select]

Oct 29 08:50:16 Tower mountd[22017]: Kernel does not have pseudo root support.
Oct 29 08:50:16 Tower mountd[22017]: NFS v4 mounts will be disabled unless fsid=0
Oct 29 08:50:16 Tower mountd[22017]: is specfied in /etc/exports file.