unRAID Server Release 4.5.6 Available

limetech · July 3, 2010

This is a maintenance release to fix problems in the previous maintenance release. Sorry, the problem happened because the "final build" script that creates the zip image used the wrong 'root' directory to build 'bzroot'.

unRAID Server 4.5.6 Release Notes
=================================

Sorry, the 4.5.5 release package got built wrong which resulted in bugs listed below.


Changes from 4.5.4 to 4.5.5
---------------------------

Bug fixes:
- Fixed problem with restoring timezone setting upon reboot.
- Fixed missing reiserfsprogs.


Changes from 4.5.4 to 4.5.5
---------------------------

Bug fixes:
- Fixed 'Mover logging' control in webGui.

Other:
- Added better timezone support.
- Increase supported array width from 20 to 21 drives.
- Add 'Are you sure?' prompt to the 'initconfig' command.
- Added IPMI support, I2C support, and Intel 82801 support.
- During parity-check, the first 20 sync errors are output to the system log.
- If directory named 'extra' exists in root of Flash, invoke 'installpkg' on all files found there before invoking the 'go' script.
- Add 'removepkg' and 'explodepkg'.
- Added 'bzip2'.
- Upgrade reiserfsprogs to version 3.6.21


Changes from 4.5.3 to 4.5.4
---------------------------

Bug fixes:
- Fix (another) problem where formatted data disks could appear 'unformatted' immediately following array start.  This one was due to race condition where md devices could possibly not exist before management utility issues 'mount'.

Other:
- Generate additional logging information during 'mount'.
- Added additional "safeguards" in the code handling 'format' operations.
- Removed 'Restore' button from webGui, replacing with new shell command called 'initconfig'.
- Updated mc (midnight-commander) utility to slackware's 2010-02-06 version.


Changes from 4.5.2 to 4.5.3
---------------------------

Other:
- Update linux kernel to 2.6.32.9
- Enable SMT (Hyperthreading) scheduler support in kernel.
- Update linux udev subsystem to 1.41.
- Fix problem reading USB Flash device model & serial number with some motherboads.
- Added USB FTDI Single Port Serial Driver per user request.


Changes from 4.5.1 to 4.5.2
---------------------------

Bug fixes:
- Fix problem where device assignment via webGui could fail if device identifier is too long.

Other:
- Added SCST subsystem (see http://scst.sourceforge.net) in order to support Marvell 88SE63xx/64xx/68xx/94xx SAS controller-based cards.
- Added 'COPYING' file in release that includes text of the GPL version 2.


Changes from 4.5 to 4.5.1
-------------------------

Bug fixes:
- Fix javascript bug checking valid settings on the Settings page.
- Fix bug where a disk can appear 'Unformatted' immediately after array Start.
- Change unmount polling rate from 1 second to 5 seconds when Stopping the array when external extensions still have a disk or use share mounted.

Other:
- Updated linux kernel to version 2.6.31.12
- Updated Samba to version 3.4.5
- Added Areca driver.
- Added Marvell legacy PATA support.
- Added USB printer support.


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.

justinkas · July 8, 2010

Hi,

I just went into my //tower through my browser and found that ALL of my 20 hard drives were showing up as unformatted. I had to restart my system at which time the parity check has begun but also looks like the drives are showing back up.

Any ideas why this may have happened or if I should perhaps expect it to happen again? I thought that a similar bug was addressed in an earlier 4.5.4 or similar prior version?

If there's anything I can do to provide more information please let me know exactly what to do (newbie here) and I'll post the answers.

PS: Prior to this I was running 4.5.4 and I NEVER have had this issue come up before.

Thanks...

limetech · July 8, 2010

No idea without seeing a system log, and yes this bug should be stamped out.

When you brought up //tower through the browser, what was the other state? For example was the array 'Started' or 'Stopped'? Was the server running ok (i.e., on your network) and you just decided to look in on status & saw all the drives 'unformatted'?

How did you restart the system?

If you ever see this happen again, before changing any state, please capture the system log first.

justinkas · July 8, 2010

Hi,

I have been running this system without any troubles for a long while now and until the 4.5.6 upgrade a few days ago everything has been running perfectly.

Can you please provide instructions for capturing a system log? Also, is there a log saved right now somewhere that might help you?

I just decided to look at the //tower in the browser because I had not been in there in a few days since the upgrade actually; and then I saw that all the drives were showing unformatted. I tried to stop the array but it would not powerdown. So I was forced to essentially hit the power switch to power it down. I then restarted the system and everything looks fine - except that it began a new parity check which is working still right now and has about an hour left.

Sincerely, Justin

SuperPerry · July 8, 2010

I am running this version but I have problem copying 4.37GB from my disk5 to disk6 using MC but then I got error my server crapping out. I tried to do it few times but no luck I have to "hard-power off" my server (pressing the power button for few secs). After that my server will check for parity everytime.

I've done it with fresh "go script" or with modified that I created, no luck. Attached is my syslog.

I am not sure why my server always crashes when I am copying files. Any help please.

Thanks.

syslog-20100708-023806.zip

kizer · July 8, 2010

Hi,

I have been running this system without any troubles for a long while now and until the 4.5.6 upgrade a few days ago everything has been running perfectly.

Can you please provide instructions for capturing a system log? Also, is there a log saved right now somewhere that might help you?

I just decided to look at the //tower in the browser because I had not been in there in a few days since the upgrade actually; and then I saw that all the drives were showing unformatted. I tried to stop the array but it would not powerdown. So I was forced to essentially hit the power switch to power it down. I then restarted the system and everything looks fine - except that it began a new parity check which is working still right now and has about an hour left.

Sincerely, Justin

cp /var/log/syslog /boot/syslog.txt

Your syslog lives in the /var/log/ directory and if you run the command up above it would copy it to your /boot directory or the root of your USB. I just tagged the end of it with .txt so you could read it easier in windows or whatever your running.

Chris Pollard · July 8, 2010

- If directory named 'extra' exists in root of Flash, invoke 'installpkg' on all files found there before invoking the 'go' script.

If you do this with the SABnzbd package provided by the community it breaks user shares. Probably something to do with SABnzbd creating its configured directories on the cache drive when it starts up. ( Nothing useful logged to syslog but a console message about being unable to create /mnt/cache appeared ).

Joe L. · July 8, 2010

- If directory named 'extra' exists in root of Flash, invoke 'installpkg' on all files found there before invoking the 'go' script.

If you do this with the SABnzbd package provided by the community it breaks user shares. Probably something to do with SABnzbd creating its configured directories on the cache drive when it starts up. ( Nothing useful logged to syslog but a console message about being unable to create /mnt/cache appeared ).

You are correct, it does not work if your package puts anything under /mnt as those directories are not yet there.

It only works for some packages, not all.

Joe L.

WeeboTech · July 9, 2010

- If directory named 'extra' exists in root of Flash, invoke 'installpkg' on all files found there before invoking the 'go' script.

If you do this with the SABnzbd package provided by the community it breaks user shares. Probably something to do with SABnzbd creating its configured directories on the cache drive when it starts up. ( Nothing useful logged to syslog but a console message about being unable to create /mnt/cache appeared ).

You are correct, it does not work if your package puts anything under /mnt as those directories are not yet there.

It only works for some packages, not all.

Joe L.

It's not the right place to put packages that depend on the array to be active.

best to use the older community methodology of testing the array's status in the go script by polling /proc/mdcmd and the /dev/md? device you want to access.

SuperPerry · July 11, 2010

I am running this version but I have problem copying 4.37GB from my disk5 to disk6 using MC but then I got error my server crapping out. I tried to do it few times but no luck I have to "hard-power off" my server (pressing the power button for few secs). After that my server will check for parity everytime.

I've done it with fresh "go script" or with modified that I created, no luck. Attached is my syslog.

I am not sure why my server always crashes when I am copying files. Any help please.

Thanks.

Can anyone please have a look at my syslog my server keeps crashing when I'm copying files. When my server crashes unraid-GUI is still active but samba share is lost and I cannot restart samba even thru unmenu. If I stop the server one of the disk my case is usually disk 6 that cannot be unmounted. I had to force shutdown my server and the server will do parity check when I turn it back on.

Help please... Thanks.

GK20 · July 11, 2010

Can anyone please have a look at my syslog my server keeps crashing when I'm copying files. When my server crashes unraid-GUI is still active but samba share is lost and I cannot restart samba even thru unmenu. If I stop the server one of the disk my case is usually disk 6 that cannot be unmounted. I had to force shutdown my server and the server will do parity check when I turn it back on.

Help please... Thanks.

you might want to stop using USB disk in your unRAID and see how it goes. the disk5/6 in your unRAID looks normal.

Jul 7 12:03:38 tower kernel: scsi4 : SCSI emulation for USB Mass Storage devices

Jul 7 12:03:38 tower kernel: usb-storage: device found at 4

Jul 7 12:03:38 tower kernel: usb-storage: waiting for device to settle before scanning

Jul 7 12:03:38 tower kernel: usb 3-3: new low speed USB device using ohci_hcd and address 2

Jul 7 12:03:38 tower kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Jul 7 12:03:38 tower kernel: ata3.00: ATA-8: WDC WD10EADS-00L5B1, 01.01A01, max UDMA/133

Jul 7 12:03:38 tower kernel: ata3.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)

Jul 7 12:03:38 tower kernel: ata3.00: configured for UDMA/133

Jul 7 12:03:38 tower kernel: scsi 2:0:0:0: Direct-Access ATA WDC WD10EADS-00L 01.0 PQ: 0 ANSI: 5

Jul 7 12:03:38 tower kernel: sd 2:0:0:0: [sdc] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)

Jul 7 12:03:38 tower kernel: sd 2:0:0:0: [sdc] Write Protect is off

Jul 7 12:03:38 tower kernel: sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00

Jul 7 12:03:38 tower kernel: sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Jul 7 12:03:38 tower kernel: sdc: sdc1

Jul 7 12:03:38 tower kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Jul 7 12:03:38 tower kernel: ata4.00: ATA-8: WDC WD10EADS-00M2B0, 01.00A01, max UDMA/133

Jul 7 12:03:38 tower kernel: ata4.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)

Jul 7 12:03:38 tower kernel: ata4.00: configured for UDMA/133

Jul 7 12:03:38 tower kernel: scsi 3:0:0:0: Direct-Access ATA WDC WD10EADS-00M 01.0 PQ: 0 ANSI: 5

Jul 7 12:03:38 tower kernel: sd 3:0:0:0: [sdd] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)

Jul 7 12:03:38 tower kernel: sd 3:0:0:0: [sdd] Write Protect is off

Jul 7 12:03:38 tower kernel: sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00

Jul 7 12:03:38 tower kernel: sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Jul 7 12:03:38 tower kernel: sdd:

Jul 7 12:03:38 tower kernel: sdd1

Jul 7 12:03:38 tower kernel: md: unRAID driver 0.95.4 installed

Jul 7 12:03:38 tower kernel: md: import disk0: [8,80] (sdf) ST31000340AS 9QJ2051W offset: 63 size: 976762552

Jul 7 12:03:38 tower kernel: md: import disk1: [8,0] (sda) MAXTOR STM375033 9QK04MPD offset: 63 size: 732574552

Jul 7 12:03:38 tower kernel: md: import disk2: [8,96] (sdg) WDC WD10EACS-22D WD-WCAU42540107 offset: 63 size: 976762552

Jul 7 12:03:38 tower kernel: md: import disk3: [8,16] (sdb) WDC WD10EADS-00L WD-WCAU46796306 offset: 63 size: 976762552

Jul 7 12:03:38 tower kernel: md: import disk4: [8,112] (sdh) SAMSUNG HD103UJ S13PJ1CS301780 offset: 63 size: 976762552

Jul 7 12:03:38 tower kernel: md: import disk5: [8,32] (sdc) WDC WD10EADS-00L WD-WCAU49177150 offset: 63 size: 976762552

Jul 7 12:03:38 tower kernel: md: import disk6: [8,48] (sdd) WDC WD10EADS-00M WD-WCAV50967676 offset: 63 size: 976762552

Jul 7 12:47:02 tower kernel: usb 1-6: reset high speed USB device using ehci_hcd and address 4

Jul 7 12:47:03 tower kernel: usb 1-6: reset high speed USB device using ehci_hcd and address 4

Jul 7 13:47:02 tower kernel: usb 1-6: reset high speed USB device using ehci_hcd and address 4

Jul 7 13:47:03 tower kernel: usb 1-6: reset high speed USB device using ehci_hcd and address 4

Jul 7 14:47:02 tower kernel: usb 1-6: reset high speed USB device using ehci_hcd and address 4

Jul 7 14:47:03 tower kernel: usb 1-6: reset high speed USB device using ehci_hcd and address 4

Jul 7 15:47:02 tower kernel: usb 1-6: reset high speed USB device using ehci_hcd and address 4

Jul 7 16:47:01 tower kernel: usb 1-6: reset high speed USB device using ehci_hcd and address 4

Jul 7 17:47:01 tower kernel: usb 1-6: reset high speed USB device using ehci_hcd and address 4

Jul 7 18:47:01 tower last message repeated 2 times

Jul 7 19:47:01 tower last message repeated 2 times

Jul 7 20:47:01 tower last message repeated 2 times

Jul 7 21:47:01 tower last message repeated 2 times

Jul 7 22:47:01 tower last message repeated 2 times

Jul 7 23:47:01 tower last message repeated 2 times

Jul 8 00:47:01 tower last message repeated 2 times

Jul 8 01:47:01 tower last message repeated 2 times

Jul 8 01:47:01 tower kernel: usb 1-6: reset high speed USB device using ehci_hcd and address 4

Jul 8 02:36:50 tower mountd[1709]: Caught signal 15, un-registering and exiting.

luke duke · July 11, 2010

I have been running 4.3.3 for a while now, with no issues. Today I tried upgrading to 4.5.6 and one of my data drives shows up as "Unformatted". I then tried to upgrade to 4.5.4 and had the same issue. I have now reverted back to 4.3.3 and everything is fine. Anyone have any ideas? I've got the syslog file, but I have no clue how to decipher it. Plus it's 28 pages long, so I'm not going to post it unless someone asks for a specific part of it.

BRiT · July 11, 2010

The full syslog is needed. Zip it up and attach it.

luke duke · July 11, 2010

Disk4 is the problem.

WDC_WD10EACS-00ZJB0_WD-WCASJ0361661

Motherboard: ABIT AB9 Pro LGA 775 Intel P965 Express ATX Intel Motherboard

All of my drives are WD Caviar Green drives.

syslog_2010-07-11_1430.zip

GK20 · July 11, 2010

Disk4 is the problem.

WDC_WD10EACS-00ZJB0_WD-WCASJ0361661

Motherboard: ABIT AB9 Pro LGA 775 Intel P965 Express ATX Intel Motherboard

All of my drives are WD Caviar Green drives.

This is why,

Jul 11 19:21:21 Tower kernel: md: import disk4: [8,80] (sdf) WDC WD10EACS-00Z WD-WCASJ0361661 offset: 63 size: 976761496

Jul 11 19:21:22 Tower kernel: REISERFS warning (device md4): jdm-20006 create_privroot: xattrs/ACLs enabled and couldn't find/create .reiserfs_priv. Failing mount.

Jul 11 19:21:22 Tower kernel: REISERFS (device md2): Using r5 hash to sort names

Jul 11 19:21:22 Tower logger: mount: Operation not supported

Jul 11 19:21:22 Tower emhttp: _shcmd: shcmd (25): exit status: 32

Jul 11 19:21:22 Tower emhttp: disk4 mount error: 32

Jul 11 19:21:22 Tower emhttp: shcmd (26): rmdir /mnt/disk4

Joe L. · July 11, 2010

Disk4 is the problem.

WDC_WD10EACS-00ZJB0_WD-WCASJ0361661

Motherboard: ABIT AB9 Pro LGA 775 Intel P965 Express ATX Intel Motherboard

All of my drives are WD Caviar Green drives.

This is why,

Jul 11 19:21:21 Tower kernel: md: import disk4: [8,80] (sdf) WDC WD10EACS-00Z WD-WCASJ0361661 offset: 63 size: 976761496

Jul 11 19:21:22 Tower kernel: REISERFS warning (device md4): jdm-20006 create_privroot: xattrs/ACLs enabled and couldn't find/create .reiserfs_priv. Failing mount.

Jul 11 19:21:22 Tower kernel: REISERFS (device md2): Using r5 hash to sort names

Jul 11 19:21:22 Tower logger: mount: Operation not supported

Jul 11 19:21:22 Tower emhttp: _shcmd: shcmd (25): exit status: 32

Jul 11 19:21:22 Tower emhttp: disk4 mount error: 32

Jul 11 19:21:22 Tower emhttp: shcmd (26): rmdir /mnt/disk4

I think that once previously that was determined to be a drive that was too full to have the attributes file created.

See this old post: http://lime-technology.com/forum/index.php?topic=4969.msg45787#msg45787

Joe L.

luke duke · July 12, 2010

I think that once previously that was determined to be a drive that was too full to have the attributes file created.

That could definitely be the cause. That disk is 100% full. I'm transferring some files now. Hopefully I'll have some time tomorrow to see if it works.

luke duke · July 12, 2010

It appears to have worked. I'm doing a parity check right now to be 100% sure. If you don't hear back from me then everything's fine.

Thanks for the help.

meerkat154 · July 18, 2010

Have to do some investigation. 4.5.6 crashes under usage. I "rolled" back to 4.5.4 and it's rock solid.

Anyone else having lockups?

Katman

speeding_ant · July 18, 2010

Not here - running solid.

pussnbootlp · September 25, 2010

4.5.6 cache won't spindown on timer setting, even you push spindown button still won't spindown.

Also, fill-up still have bug. one of my 1st disk only have 300kb left and the files is 4Gb. It will write the first 4G with the same name on 1st disk and stop, leaving the org 4Gb on cache disk. Do anyone know whey the fill-up won't check the remain size before moving files?

SSD · September 25, 2010

4.5.6 cache won't spindown on timer setting, even you push spindown button still won't spindown.

Also, fill-up still have bug. one of my 1st disk only have 300kb left and the files is 4Gb. It will write the first 4G with the same name on 1st disk and stop, leaving the org 4Gb on cache disk. Do anyone know whey the fill-up won't check the remain size before moving files?

Might try rebooting your server to get spindown working. Seem to remember issues with a new array getting spindown working. Post machine specs and syslog if that does not resolve the problem.

Can't help you with user shares.

Koolkiwi · October 10, 2010

Hi,

I've just come back after a long period running 4.2.4 without any issues. I decided to upgrade to stable 4.5.6 so I'm a little more current.

However I seem to have a problem. To conserve power, I intentionally built my unRAID Server without a VGA card. This has been working fine in the past. I do have a spare VGA card that I can install if I ever have an issue that requires me to access the server from the console. However for normal use, I have no VGA card installed (reducing power consumption and heat), and I have no keyboard connected. ie. Just a bare minimum network connected black box.

However, after upgrading to 4.5.6, my server will no longer boot-up if I do not have my VGA card installed. Basically, without the VGA card installed I see no disk activity, and I cannot network connect as the ethernet interface has presumably not been initialized at the point the boot appears to fail / freeze. With the VGA card installed all works fine, except I have a toasty hot display card unnecessarily using up power.

I'm not sure how to diagnose this, as when the system refuses to start up without a VGA card, I have now way to connect to capture a log to see how w2here the boot process has stopped.

Any ideas on what to do next, or what may have changed since 4.2.4 that now requires a VGA card to be present for successful boot?

Thanks

Greg

Kewjoe · October 11, 2010

May want to also post this in the 4.5 support forums which may get more views. Good luck, I personally don't know.

flixxx · October 12, 2010

Hi,

I already posted my syslog on another thread requesting help but it seems like it's a "known issue". I wanted to post my latest syslog error of a kernel bug here in case it helps and sheds some light in fixing this problem;

Oct 11 17:36:25 kenny kernel: BUG: unable to handle kernel paging request at f83ce000
Oct 11 17:36:25 kenny kernel: IP: [<f83c48e4>] md_cmd_proc_read+0x41/0x54 [md_mod]
Oct 11 17:36:25 kenny kernel: *pdpt = 0000000001447001 *pde = 0000000037410067 *pte = 0000000000000000
Oct 11 17:36:26 kenny kernel: Oops: 0000 [#1] SMP
Oct 11 17:36:26 kenny kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:1f.1/ide0/0.1/block/hdb/stat
Oct 11 17:36:27 kenny kernel: Modules linked in: md_mod xor ide_gd_mod i2c_i801 i2c_core ata_piix piix sata_mv r8169
Oct 11 17:36:27 kenny kernel:
Oct 11 17:36:27 kenny kernel: Pid: 19938, comm: grep Not tainted (2.6.32.9-unRAID #5)
Oct 11 17:36:27 kenny kernel: EIP: 0060:[<f83c48e4>] EFLAGS: 00010202 CPU: 2
Oct 11 17:36:27 kenny kernel: EIP is at md_cmd_proc_read+0x41/0x54 [md_mod]
Oct 11 17:36:27 kenny kernel: EAX: c44fff38 EBX: fffff615 ECX: 3fffeff0 EDX: fffff615
Oct 11 17:36:27 kenny kernel: ESI: f83ce000 EDI: ec674654 EBP: c44fff04 ESP: c44ffef4
Oct 11 17:36:27 kenny kernel:  DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
Oct 11 17:36:28 kenny kernel: Process grep (pid: 19938, ti=c44fe000 task=f7497a70 task.ti=c44fe000)
Oct 11 17:36:28 kenny kernel: Stack:
Oct 11 17:36:28 kenny kernel:  c44fff38 f83c48a3 00001000 ec671000 c44fff4c c109d5f5 00000c00 c44fff3c
Oct 11 17:36:28 kenny kernel: <0> 00000000 00008000 00000000 00007400 0806bc00 f74c4cc0 00000c00 f74c4cc0
Oct 11 17:36:28 kenny kernel: <0> 00000c00 ec671000 00000001 f74c4cc0 c109d4ea fffffffb c44fff70 c1099f72
Oct 11 17:36:28 kenny kernel: Call Trace:
Oct 11 17:36:28 kenny kernel:  [<f83c48a3>] ? md_cmd_proc_read+0x0/0x54 [md_mod]
Oct 11 17:36:28 kenny kernel:  [<c109d5f5>] ? proc_file_read+0x10b/0x22d
Oct 11 17:36:28 kenny kernel:  [<c109d4ea>] ? proc_file_read+0x0/0x22d
Oct 11 17:36:28 kenny kernel:  [<c1099f72>] ? proc_reg_read+0x56/0x6a
Oct 11 17:36:28 kenny kernel:  [<c1099f1c>] ? proc_reg_read+0x0/0x6a
Oct 11 17:36:28 kenny kernel:  [<c106cbd8>] ? vfs_read+0x8a/0x114
Oct 11 17:36:28 kenny kernel:  [<c106cf6f>] ? sys_read+0x3b/0x60
Oct 11 17:36:28 kenny kernel:  [<c1002935>] ? syscall_call+0x7/0xb
Oct 11 17:36:28 kenny kernel: Code: 55 f0 e8 6a 22 d7 c8 8d 50 01 29 f2 39 d3 7c 0b 8b 45 0c 89 d3 c7 00 01 00 00 00 8b 45 f0 89 d9 81
c6 ac 9d 3c f8 c1 e9 02 89 38 <f3> a5 89 d9 83 e1 03 74 02 f3 a4 5a 89 d8 5b 5e 5f 5d c3 55 89
Oct 11 17:36:28 kenny kernel: EIP: [<f83c48e4>] md_cmd_proc_read+0x41/0x54 [md_mod] SS:ESP 0068:c44ffef4
Oct 11 17:36:28 kenny kernel: CR2: 00000000f83ce000
Oct 11 17:36:28 kenny kernel: ---[ end trace eccec5a5c6279b90 ]---

unRAID Server Release 4.5.6 Available

Recommended Posts

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Join the conversation