Hi All

 

Sorry to create a new thread about this, but I'm also having this "Kernel Panic Out of memory" issue (different cause) and I think I've solved mine, so I figured I'd share. I am resyncing parity, where *every* single parity bit is wrong.

 

Why this is: I'm building an array; I format a disk, connect it to my linux box, copy old stuff, disconnect and reconnect to unRAID server. Rinse, repeat. As a result I now have a completely useless parity disk (nothing's in sync anymore because I'm not using the unRAID box to fill up the disks).

 

During parity check, it generates an error for every single sector, which is somehow making syslog huge, filling up ram, and causing this kernel panic.

 

EDIT *snip*

 

To fix:

 

- Boot unRAID

- Before you do a sync in the web interface, logon as root on your unraid box.

- cd /var/log

- mv syslog syslog.old ; ln -s /dev/null syslog

 

This redirects the syslog to the null device and will prevent it from filling up. To get syslog back (which you want to do when this is all over):

 

- As root on your unraid box.

- cd /var/log

- rm syslog ; mv syslog.old syslog

 

EDIT: I'm being an idiot, ignore that. Go to the unRAID Web Interface, unassign the parity disk, start the array, stop it, and reassign the parity disk. This will then allow you to bring up the array and start a parity rebuild without the errors. (thanks Joe L.)

 

Hope this helps someone!

 

- xerxesv5

Are you aware you can un-assign the parity drive and run that way while you load your disks.  True, you will not have any parity protection while you transfer your data, but you will not fill your error log (and exhaust memory) either.

 

When you get all your data drives in place, assign the parity drive, start the array, and it will calculate it all at once for you.

 

Joe L.

I actually didn't know this. When I first built the array I tried to add one data disk, then another. When I added the second data disk (without adding a parity drive) it grumbled something about "Invalid Expansion" and refused to start the array, so I figured it wants a parity disk before we go any further, and I gave it one.

 

I have since discovered that this is a bug, solved in the new betas, which are unfortunately not working on my unRAID box.

 

Figured I missed something somewhere. =)

 

Thanks Joe L.!

I actually didn't know this. When I first built the array I tried to add one data disk, then another. When I added the second data disk (without adding a parity drive) it grumbled something about "Invalid Expansion" and refused to start the array, so I figured it wants a parity disk before we go any further, and I gave it one.

 

I have since discovered that this is a bug, solved in the new betas, which are unfortunately not working on my unRAID box.

 

Figured I missed something somewhere. =)

 

Thanks Joe L.!

Please upgrade to unRAID 4.3beta6.  As you discovered, it was a bug in the 4.2 release (and prior) that prevented expansion without a parity drive present.  It has since been fixed.

 

You only need to download the most current release of unRAID, unzip it on your PC, and replace the bzroot and bzimage files on your flash drive with those from the current release to upgrade. 

 

Everything else can stay exactly as it is now.  You don't need to reformat the flash drive, or reload syslinux, or anything... just use the newer bzroot and bzimage from the most current release and you will have upgraded.  (Oh yeah, you need to reboot your server too)  Just copy those two files to you flash drive.  You can even re-name the existing two to bzroot42 and bzimage42, In case you want to revert to the older release, just name them back to their original names.

 

It will save you a lot of time since you will not constantly be re-calculating parity while you migrate your data.

 

Joe L.

I actually didn't know this. When I first built the array I tried to add one data disk, then another. When I added the second data disk (without adding a parity drive) it grumbled something about "Invalid Expansion" and refused to start the array, so I figured it wants a parity disk before we go any further, and I gave it one.

 

I have since discovered that this is a bug, solved in the new betas, which are unfortunately not working on my unRAID box.

 

Figured I missed something somewhere. =)

 

Thanks Joe L.!

Please upgrade to unRAID 4.3beta6.  As you discovered, it was a bug in the 4.2 release (and prior) that prevented expansion without a parity drive present.  It has since been fixed.

 

You only need to download the most current release of unRAID, unzip it on your PC, and replace the bzroot and bzimage files on your flash drive with those from the current release to upgrade. 

 

Everything else can stay exactly as it is now.  You don't need to reformat the flash drive, or reload syslinux, or anything... just use the newer bzroot and bzimage from the most current release and you will have upgraded.  (Oh yeah, you need to reboot your server too)  Just copy those two files to you flash drive.  You can even re-name the existing two to bzroot42 and bzimage42, In case you want to revert to the older release, just name them back to their original names.

 

It will save you a lot of time since you will not constantly be re-calculating parity while you migrate your data.

 

Joe L.

 

I did try the upgrade, and I have since rolled back to 4.2.4. I have the same issue as 'cohiba' in page 1 of beta6's announcement thread here: http://lime-technology.com/forum/index.php?topic=1757.0

 

EDIT: I switched boards from a D865GBF to a D865GLC and it now works. I *cannot* get the new unRAID beta to be happy with the D865GBF, I'll try a BIOS flash later.