I'm running into two problems:

 

1.  I can not take my server off-line - one disk is always "active"

 

2.  I shut down unRaid, add a drive and

   

    (a) can not format it because of 1 above;

    (b) one the drive is added and I restart, every third disk shows as "unformatted"

 

Suggestions?

 

syslog-2013-04-05.txt.zip

I'm running into two problems:

 

1.  I can not take my server off-line - one disk is always "active"

 

2.  I shut down unRaid, add a drive and

   

    (a) can not format it because of 1 above;

    (b) one the drive is added and I restart, every third disk shows as "unformatted"

 

Suggestions?

One or more of your add-ons is preventing you from stopping the array.  Disable them before attempting to go further. 

 

To unRAID, any disk not mounted (not able to be mounted) is considered "unformatted".  In the event of an un-clean shut-down is is very normal for it to take 30 minutes or more for the disk file-system journals to be replayed before the disks can be mounted.  DO NOT FORMAT THEM, DO NOT RE_START AGAIN WHILE THEY ARE REPLAYING THEIR JOURNALS OR YOU MIGHT CAUSE CORRUPTION.  Wait 30 minutes or more and refresh the maintenance screen, they just might be mounted.

 

If you do have corruption, you'll have to fix it before they will mount again.  See

reiserfsck

in the wiki for guidance.

 

Biggest issue is this:

: emhttp[3696]: segfault at 0 ip b7483760 sp bfb85fb0 error 4 in libc-2.11.1.so[b740a000+15c000]

 

No idea why it crashed, but you are unlikely to get any help from lime-technology unless on the latest beta release.  Good luck,  I do know some plugins have caused issues even when starting the array by accessing disks (or disk mount points) before the array is fully online, but file-system-corruption or bad memory could easily do the same.

Can you explain what this means?

 

: emhttp[3696]: segfault at 0 ip b7483760 sp bfb85fb0 error 4 in libc-2.11.1.so[b740a000+15c000]

 

I've had no issues to date and completed a parity last night with no problems.

Can you explain what this means?

 

: emhttp[3696]: segfault at 0 ip b7483760 sp bfb85fb0 error 4 in libc-2.11.1.so[b740a000+15c000]

 

I've had no issues to date and completed a parity last night with no problems.

It indicates your unRAID web-management process crashed.  You cannot use it to stop your array or perform any other management of the array until you reboot.  (It cannot be re-started without a reboot)  You'll get no response when you navigate to //tower with your browser.

 

You'll need to attempt to stop the array cleanly via either command line commands, (or basically the same commands in the add-on clean powerdown script)

I've successfully restarted and all seems to work fine, but my syslog still shows the error.

I've successfully restarted and all seems to work fine, but my syslog still shows the error.

Can you stop and re-start the array from the stock web-management screen?  If yes, cool.

If not, very bad.

 

Joe L

Yes I can start and stop.  Do I ignore this error going forward?

Yes I can start and stop.  Do I ignore this error going forward?

It is probably best if you attach a zipped copy of your syslog to your next post so a more experienced user can look for any other clues about the error you are describing.

Zip file attached.

syslog-2013-04-07.txt.zip

Yes I can start and stop.  Do I ignore this error going forward?

No.  you cannot ignore it.  It is very bad, and very unusual.

 

I see from your syslog that emhttp is being started twice.  One of them is crashing.  It should only be started once. 

 

I suspect your config/go file is poorly edited or damaged.

 

Please post it (or its contents)  Normally this is only a few lines of text.

 

Joe L.

#!/bin/bash

# Start the Management Utility

/usr/local/sbin/emhttp &

boot/unmenu/uu

 

cd /boot/packages && find . -name '*.auto_install' -type f -print | sort | xargs -n1 sh -c

/boot/config/snap/snap.sh -b

 

unraid_notify start

#!/bin/bash

# Start the Management Utility

/usr/local/sbin/emhttp &

boot/unmenu/uu

 

cd /boot/packages && find . -name '*.auto_install' -type f -print | sort | xargs -n1 sh -c

/boot/config/snap/snap.sh -b

 

unraid_notify start

It looks fairly normal.

Now what?