Incorrect rebooting of marvin 19.09.2017 - Revision history

Rf at 16:57, 20 September 2017

2017-09-20T16:57:32Z

Rf at 13:38, 20 September 2017

2017-09-20T13:38:52Z

Rf: Created page with "= Introduction = Following a much delayed maintenance period for marvin, the latest published update from RedHat on the 10 Sept 2017 (i.e. kernel 2.6.32-696.10.2.el6.x86_64)..."

2017-09-20T13:35:40Z

Created page with "= Introduction = Following a much delayed maintenance period for marvin, the latest published update from RedHat on the 10 Sept 2017 (i.e. kernel 2.6.32-696.10.2.el6.x86_64)..."

New page

= Introduction =

Following a much delayed maintenance period for marvin, the latest published update from RedHat on the 10 Sept 2017 (i.e. kernel 2.6.32-696.10.2.el6.x86_64) was implemented on the nodes and marvin itself.

= Progress =

There are usually some small problems, such as irregularities with RedHat's subscription manager software or with the repositories. Marvin had one such referring to an opensuse URL having something to do with Ocaml. This was disabled and the update went fine.

== Problem ==

The nodes were fine, but marvin itself did not boot properly

== Forgotten ==

The precaution of disabling automatic mounting of the INTERNAL, SHELF and STORAGE was not followed. This was because an attempt was made to manually unmount the systems before the closedown, which is not a necessary operation. The manual umount's were not successful. There has been no problem in the past just rebooting while these were mounted. So they were uncommented in the '''fstab''' file.

Truth is, it was thought that these filesystems were set to '''noauto''', but this was not true, they are set up with normal '''defaults'''.

So, after the manual unmounting attempt, these lines were not commented out again. The problem here is that - and the reason is not understood - automatic mounting (especially of STORAGE) cuases a hiccup in the RedHat boot process. All indications point to a hanging at the fsck stage.

← Older revision		Revision as of 16:57, 20 September 2017
Line 18:		Line 18:

	The problem here is that - and the reason is not understood - automatic mounting (especially of STORAGE) causes a hiccup in the RedHat boot process. All indications point to a hanging at the fsck stage. SO this is why marvin did not boot up properly, and also they reason why this was unexpected, because uncommenting was not meant to allow automatic mounting becaus eit was though the '''noauto''' would then come into force. That was a mistake.		The problem here is that - and the reason is not understood - automatic mounting (especially of STORAGE) causes a hiccup in the RedHat boot process. All indications point to a hanging at the fsck stage. SO this is why marvin did not boot up properly, and also they reason why this was unexpected, because uncommenting was not meant to allow automatic mounting becaus eit was though the '''noauto''' would then come into force. That was a mistake.
		+
		+	Needless, to say, much heartbreak can be avoid if these things are not forgotten.
		+
		+	To remedy this, a live Linux distribution on a USB stick is required. The CIBOX branded stick has the "SystemRescueCD" distribution on it. It recognises LVM, so you can simply go into the /dev/mapper foler and mount

@@ Line 15: / Line 15: @@
 The precaution of disabling automatic mounting of the INTERNAL, SHELF and STORAGE was not followed. This was because an attempt was made to manually unmount the systems before the closedown, which is not a necessary operation. The manual umount's were not successful. There has been no problem in the past just rebooting while these were mounted. So they were uncommented in the '''fstab''' file.
-Truth is, it was thought that these filesystems were set to '''noauto''', but this was not true, they are set up with normal '''defaults'''.
+Truth is, it was thought that these filesystems were set to '''noauto''', but this was not true, they are set up with normal '''defaults'''. So, after the manual unmounting attempt, these lines were not commented out again, so their automatic mounting was set again.
-So, after the manual unmounting attempt, these lines were not commented out again. The problem here is that - and the reason is not understood - automatic mounting (especially of STORAGE) cuases a hiccup in the RedHat boot process. All indications point to a hanging at the fsck stage.
+The problem here is that - and the reason is not understood - automatic mounting (especially of STORAGE) causes a hiccup in the RedHat boot process. All indications point to a hanging at the fsck stage. SO this is why marvin did not boot up properly, and also they reason why this was unexpected, because uncommenting was not meant to allow automatic mounting becaus eit was though the '''noauto'''  would then come into force. That was a mistake.