Visit Open-E website
Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 27

Thread: Kernel error kernel:[360783.353677]

  1. #11
    Join Date
    Aug 2010
    Posts
    404

    Default

    One of the links show a solution by replacing disk(s) with errors, after that the system start to work fine.
    So we recommend you to check your controller health and to check the storage disks, then to run file system repair tool to fix your FS if it contain any issue.
    Please check this KB: http://kb.open-e.com/File-system-repair_138.html

    Also please be sure that your controller Firmware is updated to the latest firmware available at your controller website.

  2. #12
    Join Date
    Oct 2009
    Posts
    53

    Default

    Thanks for the hints: I've checked the controller's and disks' health and no issue was found. All are running the latest firmware builds.
    However, I found that the ACPI features were still turned on in the boot options - I guess I turned them off before upgrading to v7 and forgot to check afterwards.
    I turned it off and rebooted.

    The machine is up and running again and I keep my fingers crossed...
    Thanks for your help and I'll keep this thread up to date so it might be helpful for other users (although maybe just the inexperienced users like me).

  3. #13
    Join Date
    Oct 2010
    Location
    GA
    Posts
    935

    Default

    FYI: driver settings, and boot settings and a few more, are not saved when going from DSS V6-->DSS V7. I thought this was in the release notes someplace. Guess I will have to check on that!

  4. #14
    Join Date
    Oct 2009
    Posts
    53

    Default

    I'm sure it's in there: I probably just did not pay enough attention when upgrading

    Unfortunately, keeping the fingers crossed did not help: even with having ran a full memtest (no errors), completely disabled the onboard SATA controller and the ACPI features turned off, the system hang again last night.
    I rebooted and checked the error logs, but I could not find a clue what happened.

    It feels like I'm slowly running out of ideas...
    Anyone willing to take a look at my logs and see if I overlooked something?
    Last edited by Arcesilaus; 10-26-2012 at 09:11 AM.

  5. #15

    Default

    yeah, for sure.

    How do you see that it is a system freeze? Is it a actual freeze? Or is it something like: WebGUI not available, Console behaving slow and strange?

  6. #16
    Join Date
    Oct 2009
    Posts
    53

    Default

    Thanks for the offer: I have to find a way to post the latest Logs here (if that is permitted).

    Well, the freeze is quite comprehensive: no response on NICs (not able to ping), no response on console (no keystroke wakes the screen) at all.
    All that is left, is a hard reset.

  7. #17

    Default

    hm okay this is definitely a kernel panic.
    just upload the logs anywhere and post a link to it? should be permitted

  8. #18
    Join Date
    Oct 2009
    Posts
    53

    Default

    Hi Daniel

    It looks indeed like a kernel panic, mostly happening under some load. I've checked the logs for the latest connection logs before (manual) reset, and here are the results:

    26-10, 02:00: Freeze when scanning folders for music files, logs taken at 07:13:
    [2012/10/26 02:00:49.934090, 1] smbd/vfs.c:932(check_reduced_name)
    check_reduced_name: couldn't get realpath for
    24-10, 16:10: Freeze when re-applying security rights, logs taken at 16:50:
    [2012/10/24 04:00:39.437702, 1] smbd/vfs.c:932(check_reduced_name)
    check_reduced_name: couldn't get realpath for
    [2012/10/24 16:10:18.187779, 0] modules/vfs_posixacl.c:349(smb_acl_to_posix):
    smb_acl_to_posix: ACL is invalid for set (Invalid argument)
    23-10, 00:21: Freeze, not clear what triggered the panic, logs taken at 07:40:
    [2012/10/23 00:01:35.570535, 1] smbd/vfs.c:932(check_reduced_name)
    check_reduced_name: couldn't get realpath
    [2012/10/23 08:05:50.234214, 1] smbd/vfs.c:932(check_reduced_name)
    check_reduced_name: couldn't get realpath
    22-10, 15:06, Freeze, not clear what triggered the panic, logs taken at 21:54
    [2012/10/22 14:29:51.344227, 1] smbd/vfs.c:932(check_reduced_name)
    check_reduced_name: couldn't get realpath for
    Admittedly, when bringing the machine back up, I did not always run the filesystem check: there was simply not enough time for that.
    Could any FS errors cause a kernel panic?

  9. #19

    Default

    Hi,

    normally not.

    Please send us the following logs completely(!):

    critical_error, dmesg2, test, Samba

    Greets

  10. #20
    Join Date
    Oct 2009
    Posts
    53

    Default

    I just posted you a message on your profile page that contains the details of where the log can be found.
    Please let me know if you are successful in picking them up...

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •