unRAID Server Release 5.0-beta14 Available

had a kernel: BUG: unable to handle kernel NULL pointer dereference at  (null)

when I tried to stop the array

I have a Supermicro X8SIL-V board, 6 sata drives attached to the on-board sata controller

I also have a LSI 3081-er (1068e based) but it didn't have any drives attached to it

all of the 6 drives were sleeping. they woke up, but the web interface couldn't stop the array. it apparently froze in the sync command

syslog attached

any help about that ?

syslog.zip

had a kernel: BUG: unable to handle kernel NULL pointer dereference at  (null)

when I tried to stop the array

 

I have a Supermicro X8SIL-V board, 6 sata drives attached to the on-board sata controller

 

I also have a LSI 3081-er (1068e based) but it didn't have any drives attached to it

 

all of the 6 drives were sleeping. they woke up, but the web interface couldn't stop the array. it apparently froze in the sync command

 

syslog attached

 

any help about that ?

Please do not use LSI based cards with beta13 or beta14 versions. The beta12a is the most recent reliable version for use with LSI cards.

OK

Removed the LSI card

Thanks

Something's amiss....

Yesterday the web GUI was inaccessible (but unMENU was); had to force a reboot via command line but server would not boot for what seemed like hours.  Leaving it in that state, I came home to find the server was finally fully booted, but now the web GUI is still showing as loading in my web browser for the past 5 minutes (again, unMENU is still works just fine, my savior).

Syslog (via unMENU) shows some sort of port error on all drive ports:

UnRAID kernel: ata#: sas eh calling libata port error handler (Errors)

And none of the drives appear to be accessible via command line and mnt directory is empty.

Rebooted, checked BIOS and all drives are shown available.  SASLP card POSTs as well, lists all connected drives and indicates all OK.

After reboot, everything now seems just fine.  Weird.

UPDATE: 2012-02-03:  I just looked at my current syslog and noticed the same libata error again, but this time just applying to what appears to be the AOC-SASLP card, but unRAID seems to still be functioning, no other errors or system failures appear to be present, and I can access read/write to all drives attached to the SASLP.  Pulling up some old syslog's from the past shows these errors have always been showing up on the SASLP card since December of last year, right after upgrading to B14.  Syslogs prior to B14 don't show this error...

syslog-2012-02-01.txt

Here's two requests for the developers. 

1.  Support for 3Ware Controllers - Here's the syslog error.

Feb  3 13:19:32 Tower last message repeated 66 times

Feb  3 13:19:33 Tower kernel: 3w-9xxx: scsi0: ERROR: (0x03:0x0101): Invalid command opcode:opcode=0x85.

Feb  3 13:19:34 Tower last message repeated 5 times

Feb  3 13:19:38 Tower unmenu[6604]: bad method -  2052243 63630231 525458441  2437090      49      25      592      10        0  2375820  24365202052243-^M

Feb  3 13:19:38 Tower last message repeated 33 times

Feb  3 13:19:44 Tower kernel: 3w-9xxx: scsi0: ERROR: (0x03:0x0101): Invalid command opcode:opcode=0x85.

Feb  3 13:19:45 Tower last message repeated 4 times

Feb  3 13:19:45 Tower unmenu[6604]: bad method -  2052243 63630231 525458441  2437090      49      25      592      10        0  2375820  24365202052243-^M

Feb  3 13:19:45 Tower last message repeated 32 times

Feb  3 13:19:45 Tower kernel: 3w-9xxx: scsi0: ERROR: (0x03:0x0101): Invalid command opcode:opcode=0x85.

2.  Please release some new code soon.

Thanks

Did a try with the new kernal 3.2.2 in B14, but it's same issu for me regarding NFS/Fuse.

 

//Peter

Peter,

Do you a link to the 3.2 kernel you built I would like to test and see if it gets rid of my acpi errors which if it was patched then it should fix the libata errors as well.

thx,

Dave

You can try this version

http://www.filefactory.com/file/c23d2f2/n/Archive.zip

• Linux Tower 3.2.4-unRAID
  
• Samba version 3.6.3
  
• afpd 2.2.2 - Apple Filing Protocol (AFP) daemon of Netatalk
  

There is a issue using Timemachine, need to looking into what more I need to add to the compiling.

root@Tower:~# afpd -v
afpd 2.2.2 - Apple Filing Protocol (AFP) daemon of Netatalk

This program is free software; you can redistribute it and/or modify it under
the terms of the GNU General Public License as published by the Free Software
Foundation; either version 2 of the License, or (at your option) any later
version. Please see the file COPYING for further information and details.

afpd has been compiled with support for these features:

          AFP versions: 1.1 2.0 2.1 2.2 3.0 3.1 3.2 3.3
DDP(AppleTalk) Support: Yes
         CNID backends: dbd last tdb

             afpd.conf: /etc/netatalk/afpd.conf
   AppleVolumes.system: /etc/netatalk/AppleVolumes.system
  AppleVolumes.default: /etc/netatalk/AppleVolumes.default
    afp_signature.conf: /etc/netatalk/afp_signature.conf
      afp_voluuid.conf: /etc/netatalk/afp_voluuid.conf
         afp_ldap.conf: /etc/netatalk/afp_ldap.conf
       UAM search path: /etc/netatalk/uams/
  Server messages path: /etc/netatalk/msg/
              lockfile: /var/lock/afpd

root@Tower:~# smbstatus

Samba version 3.6.3

 uname -rs
Linux 3.2.4-unRAID
root@Tower:~# Linux 3.2.4-unRAID

Thanks peter, I am copying a bunch of files over I will test it when I get done and report.

Thanks,

Dave

Removed link, the issue with compiled netatalk was that I couldn't use password to my get access to the shared folder for AFP

Need to see what I need to change to get it right. but 2.2.1 it god enough.

//Peter

That fine, I am pretty sure the s3 acpi fixes are in the 3.3 kernels anyhow. I am testing on another machine with Sandy Bridge setup and I could not get S3 working until I installed 3.3rc2 (ubuntu) on mythbuntu 11.10 and mythbuntu 10.04.

It does fix the acpi namespace issue and from what I read that is directly related to getting a acpid for video and libata. come on TOM  . Give me something at least to test with please.

I am not taking down my old server until i know this is fixed -WAF is not too happy, I have three servers and a mythbuntu back/end running in the rack downs stairs.  Hydro has to think I have a 4 factory here. LOL.  but seriously I am not taking the chance on losing any data until that acpi namespace issue is fixed which it is on my Sandy Bridge OS/XBMC/MYTH test system.

Dave

No joy.  It wasn't running and when I restarted it I got this:

 

Jan 10 19:51:59 freenas emhttp: unRAID System Management Utility version 5.0-beta14
Jan 10 19:51:59 freenas emhttp: Copyright (C) 2005-2011, Lime Technology, LLC
Jan 10 19:51:59 freenas emhttp: Pro key detected, GUID: 0781-556B-3109-3213ECBXXXX
Jan 10 19:51:59 freenas kernel: mdcmd (35): spindown 2
Jan 10 19:52:00 freenas kernel: mdcmd (36): spindown 3
Jan 10 19:52:01 freenas emhttp: rdevName.22 not found
Jan 10 19:52:01 freenas emhttp: diskFsStatus.1 not found
Jan 10 19:52:01 freenas kernel: emhttp[17085]: segfault at 0 ip b754a760 sp bf9442b0 error 4 in libc-2.11.1.so[b74d1000+15c000]

 

This seems to be some great mystery of the universe.  Seems like a dozen of us suddenly started having this problem, but no answers exist.  rdevName.22 not found, but I don't know what that means and why it didn't happen for months and suddenly it starts happening.  I've disabled everything extra and still have the problem.  No one has ideas on how to fix this?

 

Test with a clean install.

 

Short of purchasing a new license to put on a new USB flash drive, what files can I delete (after making a copy of course) to bring me back to a stock install?  I disabled all plugins, auto installs, scripts, etc. already.

I just solved the same error on my system. Are you using ESET antivirus suite? The web scanner crashes emhttp on unraid. see http://lime-technology.com/forum/index.php?topic=18333.0

Does anyone have any ETA on Beta15? I haven't done a parity sync in 5 months because parity sync has been slow since beta12. Rolling back fixes this, but I'd like to stay on the latest beta.

I reported this a few times but it seems like im the only person that is experiencing slow parity speeds on the newest betas. I don't see how it could possibly be hardware related, because it doesnt happen on older version. It seems driver related to me, and I heard the next beta is going to have a much newer linux kernal. Hoping it fixes it...

Based on this:

http://lime-technology.com/forum/index.php?topic=17705.msg163222#msg163222

I'm not expecting it anytime really soon.

Does anyone have any ETA on Beta15? I haven't done a parity sync in 5 months because parity sync has been slow since beta12. Rolling back fixes this, but I'd like to stay on the latest beta.

let it run over night, it should not be a huge problem then.  Not running a parity check for 5 months could be far worse than letting the check run for +/- 10 hours.

I reported this a few times but it seems like im the only person that is experiencing slow parity speeds on the newest betas. I don't see how it could possibly be hardware related, because it doesnt happen on older version. It seems driver related to me, and I heard the next beta is going to have a much newer linux kernal. Hoping it fixes it...

I think parity checks may have slowed down for a number of people; it might have for me...  It is not a huge deal because the check runs while everyone in my house is asleep.

Does anyone have any ETA on Beta15? I haven't done a parity sync in 5 months because parity sync has been slow since beta12. Rolling back fixes this, but I'd like to stay on the latest beta.

let it run over night, it should not be a huge problem then.  Not running a parity check for 5 months could be far worse than letting the check run for +/- 10 hours.

It will take 78 hours at the speed it goes.. 3TB parity with 20 data drives, many of the data drives are also 3TB.

Beta12 it takes around 7 hours if I remember right, definitely less than 12 hours.

How do figure out which devices are open? I am new to unRAID and have a AOC-SASLP-MV8 arriving tomorrow. I would like to use this beta with it so I could have 3TB support.

 

I use the command 'lsof', grepping for /mnt: lsof | grep /mnt

 

It will list shares, drives that are open. Good luck and welcome aboard!

Will using {UNMENU -System Info - Open Files} do the same thing? I mean that should show me all open files correct?

How do figure out which devices are open? I am new to unRAID and have a AOC-SASLP-MV8 arriving tomorrow. I would like to use this beta with it so I could have 3TB support.

 

I use the command 'lsof', grepping for /mnt: lsof | grep /mnt

 

It will list shares, drives that are open. Good luck and welcome aboard!

 

Will using {UNMENU -System Info - Open Files} do the same thing? I mean that should show me all open files correct?

It is the output of

/usr/bin/lsof /dev/md*

which will not show you the cache drive or the user shares.

I just solved the same error on my system. Are you using ESET antivirus suite? The web scanner crashes emhttp on unraid. see http://lime-technology.com/forum/index.php?topic=18333.0

No ESET here.  Only Macs running Safari.

I've actually been running b14 for a while now, having some crashing issues.  I assumed it was because of all the plugins that it was running out of memory, so I cut back on them and upgraded the memory.  Then it seemed to do it during heavy networking, torrents, HD streaming, ftp, etc so I decided to pipe the syslog to a local file and noticed what I'm guessing is the NIC crapping out, but I'm not sure, any ideas?

Feb  7 22:16:01 BobTower kernel: ------------[ cut here ]------------
Feb  7 22:16:01 BobTower kernel: WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0xf8/0x17b()
Feb  7 22:16:01 BobTower kernel: Hardware name: MS-7592
Feb  7 22:16:01 BobTower kernel: NETDEV WATCHDOG: eth0 (atl1c): transmit queue 0 timed out
Feb  7 22:16:01 BobTower kernel: Modules linked in: md_mod xor i2c_i801 i2c_core ata_piix piix atl1c [last unloaded: md_mod]
Feb  7 22:16:01 BobTower kernel: Pid: 0, comm: kworker/0:0 Not tainted 3.1.1-unRAID #1
Feb  7 22:16:01 BobTower kernel: Call Trace:
Feb  7 22:16:01 BobTower kernel:  [<c1028550>] warn_slowpath_common+0x65/0x7a
Feb  7 22:16:01 BobTower kernel:  [<c12a379e>] ? dev_watchdog+0xf8/0x17b
Feb  7 22:16:01 BobTower kernel:  [<c10285c9>] warn_slowpath_fmt+0x26/0x2a
Feb  7 22:16:01 BobTower kernel:  [<c12a379e>] dev_watchdog+0xf8/0x17b
Feb  7 22:16:01 BobTower kernel:  [<c103117e>] run_timer_softirq+0x10a/0x182
Feb  7 22:16:01 BobTower kernel:  [<c12a36a6>] ? __netdev_watchdog_up+0x52/0x52
Feb  7 22:16:01 BobTower kernel:  [<c102c9ee>] __do_softirq+0x6b/0xe5
Feb  7 22:16:01 BobTower kernel:  [<c102c983>] ? irq_enter+0x3c/0x3c
Feb  7 22:16:01 BobTower kernel:  <IRQ>  [<c102c841>] ? irq_exit+0x32/0x53
Feb  7 22:16:01 BobTower kernel:  [<c101590d>] ? smp_apic_timer_interrupt+0x6c/0x7a
Feb  7 22:16:01 BobTower kernel:  [<c130bd0a>] ? apic_timer_interrupt+0x2a/0x30
Feb  7 22:16:01 BobTower kernel:  [<c1007c7e>] ? mwait_idle+0x4a/0x50
Feb  7 22:16:01 BobTower kernel:  [<c1001a69>] ? cpu_idle+0x43/0x5a
Feb  7 22:16:01 BobTower kernel:  [<c1307570>] ? start_secondary+0xad/0xaf
Feb  7 22:16:01 BobTower kernel: ---[ end trace 2733570d23560efd ]---
Feb  7 22:16:01 BobTower kernel: atl1c 0000:02:00.0: irq 43 for MSI/MSI-X
Feb  7 22:16:01 BobTower kernel: atl1c 0000:02:00.0: atl1c: eth0 NIC Link is Up<100 Mbps Full Duplex>

Well I finally did a parity sync after 5 months because of the newest betas having slow parity speeds.. and got 1 error with 3TB of parity.

Feb  8 00:58:57 UNRAID kernel: md: parity incorrect: 2994297112

It was auto corrected, and if my knowledge on the SATA interface is correct, 5 months of writing has a rather good chance of at least 1 SATA error that would cause a parity sync error. So, should I ignore it? I've probably wrote a good 5TB of data since the last parity sync.

I've actually been running b14 for a while now, having some crashing issues.  I assumed it was because of all the plugins that it was running out of memory, so I cut back on them and upgraded the memory.  Then it seemed to do it during heavy networking, torrents, HD streaming, ftp, etc so I decided to pipe the syslog to a local file and noticed what I'm guessing is the NIC crapping out, but I'm not sure, any ideas?

Its generally best to attach your whole system log to your post as there can be events/errors/messages before and/or after that error that is related and can help others tell you what the problem may be.

With my limited knowledge, i would say the same thing, NIC/Network problems.

Do you know what NIC you are using?

At the end of the log snippet it says "eth0 NIC Link is Up<100 Mbps Full Duplex>", is your network only 10/100 Mbps or do you run gigabit?

The NIC is the onboard one from this mobo: http://www.newegg.com/Product/Product.aspx?Item=N82E16813130555R and yes my network is only 10/100.  I'll get a full syslog and attach next time it happens, I've been keeping torrenting off just to see if it helps, and it seems to not shut down after little HTPC.  Would there be any other logs that are useful that I should capture?

Hey guys,

I've just added a 4TB "ST4000DX000-1C5160_Z1Z00P0M" from a Seagate GoFlex external to my box, how ever, it's appearing as a 3TB drive.

26°C 3 TB 3 TB 609 22457 0

I only have a 500GB, 320GB and this drive in there, all as data, no parity or cache as I'm just playing around for now.

Any ideas? I was hoping to get it to appear as 4TB before I start writing to it.

Hey guys,

I've just added a 4TB "ST4000DX000-1C5160_Z1Z00P0M" from a Seagate GoFlex external to my box, how ever, it's appearing as a 3TB drive.

26°C 3 TB 3 TB 609 22457 0

 

I only have a 500GB, 320GB and this drive in there, all as data, no parity or cache as I'm just playing around for now.

 

Any ideas? I was hoping to get it to appear as 4TB before I start writing to it.

what does

fdisk -lu /dev/sdX

and

hdparm -I /dev/sdX

and

cat /sys/block/sdX/size

give to you?

what does

fdisk -lu /dev/sdX

WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.

Disk /dev/sda: 3000.6 GB, 3000615492608 bytes

255 heads, 63 sectors/track, 364804 cylinders, total 5860577134 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x00000000

  Device Boot      Start        End      Blocks  Id  System

/dev/sda1              1  4294967295  2147483647+  ee  GPT

hdparm -I /dev/sdX

/dev/sda:

ATA device, with non-removable media

        Model Number:      ST4000DX000-1C5160

        Serial Number:      Z1Z00P0M

        Firmware Revision:  CC42

        Transport:          Serial, SATA Rev 3.0

Standards:

        Used: unknown (minor revision code 0x0029)

        Supported: 8 7 6 5

        Likely used: 8

Configuration:

        Logical        max    current

        cylinders      16383  16383

        heads          16      16

        sectors/track  63      63

        --

        CHS current addressable sectors:  16514064

        LBA    user addressable sectors:  268435455

        LBA48  user addressable sectors: 5860577134

        Logical/Physical Sector size:          512 bytes

        device size with M = 1024*1024:    2861609 MBytes

        device size with M = 1000*1000:    3000615 MBytes (3000 GB)

        cache/buffer size  = unknown

        Nominal Media Rotation Rate: 7200

Capabilities:

        LBA, IORDY(can be disabled)

        Queue depth: 32

        Standby timer values: spec'd by Standard, no device specific minimum

        R/W multiple sector transfer: Max = 16  Current = 16

        Advanced power management level: 128

        Recommended acoustic management value: 208, current value: 0

        DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6

            Cycle time: min=120ns recommended=120ns

        PIO: pio0 pio1 pio2 pio3 pio4

            Cycle time: no flow control=120ns  IORDY flow control=120ns

Commands/features:

        Enabled Supported:

          *    SMART feature set

                Security Mode feature set

          *    Power Management feature set

          *    Write cache

          *    Look-ahead

          *    Host Protected Area feature set

          *    WRITE_BUFFER command

          *    READ_BUFFER command

          *    DOWNLOAD_MICROCODE

          *    Advanced Power Management feature set

                SET_MAX security extension

          *    48-bit Address feature set

          *    Device Configuration Overlay feature set

          *    Mandatory FLUSH_CACHE

          *    FLUSH_CACHE_EXT

          *    SMART error logging

          *    SMART self-test

          *    General Purpose Logging feature set

          *    WRITE_{DMA|MULTIPLE}_FUA_EXT

          *    64-bit World wide name

                Write-Read-Verify feature set

          *    WRITE_UNCORRECTABLE_EXT command

          *    {READ,WRITE}_DMA_EXT_GPL commands

          *    Segmented DOWNLOAD_MICROCODE

          *    Gen1 signaling speed (1.5Gb/s)

          *    Gen2 signaling speed (3.0Gb/s)

          *    unknown 76[3]

          *    Native Command Queueing (NCQ)

          *    Phy event counters

          *    unknown 76[15]

                DMA Setup Auto-Activate optimization

                Device-initiated interface power management

          *    Software settings preservation

          *    SMART Command Transport (SCT) feature set

          *    SCT LBA Segment Access (AC2)

                unknown 206[7]

                unknown 206[12] (vendor specific)

Security:

        Master password revision code = 65534

                supported

        not    enabled

        not    locked

        not    frozen

        not    expired: security count

                supported: enhanced erase

        506min for SECURITY ERASE UNIT. 506min for ENHANCED SECURITY ERASE UNIT.

Logical Unit WWN Device Identifier: 5000c50035e53be2

        NAA            : 5

        IEEE OUI        : 000c50

        Unique ID      : 035e53be2

Checksum: correct

cat /sys/block/sdX/size

5860577134