OpenMediaVault Hangs on Boot

I am having a problem with my OpenMediaVault server failing to boot up. The particularly aggravating thing is that this is happening intermittently. Sometimes it works, and sometimes it doesn't.

Basically, what will happen is if I try to reboot the computer, the server will not come back up on its own. Instead, it will hang at some point during the reboot. To get the server working again, I tried cutting the power to it by pulling the plug, then plugging it back in (the server automatically powers on when power is restored). This did not work either, as the server was still hanging. I tried to figure out what was causing the hanging by connecting a monitor and trying the boot process again, but the server came up just fine! I shut down the server unplugged the monitor, and powered it on without any issues.

Since then, I've discovered that if I reboot the server shortly after it comes up, the reboot works fine, but if I wait a while (I don't have a precise measurement of this unfortunately), the reboot will fail. If I try to resolve the issue by cutting the power and restoring it, the computer will only boot after sitting for a few minutes. What's going on. Why is this happening? Is there a way that I could get information about why this annoying issue keeps coming up?

Zitat von Dropkick Murphy

You may attach a log, so that someone can help you...

I would, but I am not sure what log I should attach.

Zitat von cabrio_leo

At least the syslog.

Okay. I have attached the syslog to this post and have also posted it on PasteBin to make it easier to review without downloading it.

https://pastebin.com/NwB9E3Ng

Zitat von cabrio_leo

That syslog is very short. There must be a log file about the complete boot process also.

Is your system drive a SD card or something like this? Are you sure that it is not defective?

Here's my boot log: https://pastebin.com/LgKA5Yn7

As for my system drive, I use a regular hard drive, and I am fairly confident that it is not defective.

Zitat von cabrio_leo

I can see several disk timeouts in the log:

Spoiler anzeigen

[*]2017-11-05T21:24:28-0500 OpenMediaVault systemd[1]: Job dev-disk-by\x2did-ata\x2dST4000DM000\x2d2AE166_WDH141CG\x2dpart1.device/start timed out.
[*]2017-11-05T21:24:28-0500 OpenMediaVault systemd[1]: Timed out waiting for device dev-disk-by\x2did-ata\x2dST4000DM000\x2d2AE166_WDH141CG\x2dpart1.device.

and a lot of this kind of messages:

Spoiler anzeigen

2017-11-06T08:00:03-0500 OpenMediaVault CRON[19230]: pam_unix(cron:session): session closed for user root

2017-11-06T08:09:01-0500 OpenMediaVault CRON[19427]: pam_unix(cron:session): session opened for user root by (uid=0)

Alles anzeigen

I recently had one of my hard drives fail and I had to remove it. I'll have to look to see if it's having a hard time with one of my other drives. Hopefully that's it though.

Could this message also be caused by waiting for drives to spin up? My drives spin down after a certain amount of time and I'm wondering if that is perhaps the problem.

Zitat von cabrio_leo

I can see several disk timeouts in the log:

Spoiler anzeigen

[*]2017-11-05T21:24:28-0500 OpenMediaVault systemd[1]: Job dev-disk-by\x2did-ata\x2dST4000DM000\x2d2AE166_WDH141CG\x2dpart1.device/start timed out.
[*]2017-11-05T21:24:28-0500 OpenMediaVault systemd[1]: Timed out waiting for device dev-disk-by\x2did-ata\x2dST4000DM000\x2d2AE166_WDH141CG\x2dpart1.device.

and a lot of this kind of messages:

Spoiler anzeigen

2017-11-06T08:00:03-0500 OpenMediaVault CRON[19230]: pam_unix(cron:session): session closed for user root

2017-11-06T08:09:01-0500 OpenMediaVault CRON[19427]: pam_unix(cron:session): session opened for user root by (uid=0)

Alles anzeigen

I recently had one of my hard drives fail and I had to remove it. I'll have to look to see if it's having a hard time with one of my other drives. Hopefully that's it though.

Could this message also be caused by waiting for drives to spin up? My drives spin down after a certain amount of time and I'm wondering if that is perhaps the problem.

Zitat von cabrio_leo

Normally the disk should spin up in a period of time shorter than the time out. I would interpret this message that the drive doesn´t spin up at all or takes to much time.

From what I can tell, the drive that it's trying to connect to is the one that died that I pulled from the computer. I am inferring this based on the "WDH141CG" part of the entry. That looks a lot like the serial numbers for my other drives, but it is not identical to any of the ones that I have. Unfortunately, I cannot check the serial number on the dead drive, as I do not have it in my possession at this time.

I've just had this happen to me again. Any ideas @ryecoaaron or @votdev?

Zitat von ryecoaaron

Was it fixed at some point?

No. I just haven't rebooted the machine recently.

Zitat von ryecoaaron

What is the output of mount -a

Here is the output of mount -a. I believe the "Failed to access volume" entry is related to the hard drive that I removed.

ntfs-3g: Failed to access volume '/dev/disk/by-id/ata-ST4000DM000-2AE166_WDH141CG-part1': No such file or directory


ntfs-3g 2014.2.15AR.2 integrated FUSE 28 - Third Generation NTFS Driver
                Configuration type 7, XATTRS are on, POSIX ACLS are on


Copyright (C) 2005-2007 Yura Pakhuchiy
Copyright (C) 2006-2009 Szabolcs Szakacsits
Copyright (C) 2007-2014 Jean-Pierre Andre
Copyright (C) 2009 Erik Larsson


Usage:    ntfs-3g [-o option[,...]] <device|image_file> <mount_point>


Options:  ro (read-only mount), windows_names, uid=, gid=,
          umask=, fmask=, dmask=, streams_interface=.
          Please see the details in the manual (type: man ntfs-3g).


Example: ntfs-3g /dev/sda1 /mnt/windows


News, support and information:  http://tuxera.com

Zitat von ryecoaaron

How about:

omv-mkconf fstab

Then:

mount -a

Alles anzeigen

The output that I get is identical to what I posted before.