A weird startup on the HD

prpr

prpr

Well-Known Member
This happened overnight (at 3am BST, contrary to what the log initially says, but that's probably TZ related as discussed elsewhere):
Code: 
--------- Info for Modinit PID 666 ---------
666: Date:       Fri Jun 24 03:09:09 UTC 2022
666: MDEV:       sda1
666: ACTION:     add
666: Model:      HD
666: Device:     /dev/sda1
666: Disk:       sda

666:24/06/2022 03:09:09 +0000: sda1 is candidate for mod [/media/drive1]
666:24/06/2022 03:09:09 +0000: Waiting for disk to become ready...
666:24/06/2022 03:09:10 +0000:   disk ready after 0 seconds
666:24/06/2022 03:09:10 +0000: /dev/sda1 is formatted as ext2/3
666:24/06/2022 03:09:10 +0000: /dev/sda1 is NOT removable.
666:24/06/2022 03:09:10 +0000: /dev/sda1 is connected via USB.
666:24/06/2022 03:09:10 +0000: /dev/sda1 partition type dos
666:24/06/2022 03:09:10 +0000: Waiting for the disk to mount...
666:24/06/2022 03:09:11 +0000:   still waiting...
666:24/06/2022 03:09:12 +0000:   still waiting...
666:24/06/2022 03:09:13 +0000:   still waiting...
666:24/06/2022 03:09:14 +0000:   still waiting...
666:23/06/2022 23:09:15 +0000:   still waiting...
666:23/06/2022 23:09:16 +0000:   still waiting...
666:23/06/2022 23:09:17 +0000:   still waiting...
666:24/06/2022 02:00:48 +0000:   still waiting...
666:24/06/2022 02:00:50 +0000:   still waiting...
666:24/06/2022 02:00:51 +0000:   still waiting...
666:24/06/2022 02:00:52 +0000:   still waiting...
666:24/06/2022 02:00:53 +0000:   still waiting...
666:24/06/2022 02:00:54 +0000:   still waiting...
666:24/06/2022 02:00:55 +0000:   still waiting...
666:24/06/2022 02:00:57 +0000:   still waiting...
666:24/06/2022 02:00:58 +0000:   still waiting...
666:24/06/2022 02:00:59 +0000:   still waiting...
666:24/06/2022 02:01:00 +0000:   still waiting...
666:24/06/2022 02:01:01 +0000:   still waiting...
666:24/06/2022 02:01:02 +0000:   still waiting...
666:24/06/2022 02:01:03 +0000:   still waiting...
666:24/06/2022 02:01:04 +0000:   still waiting...
666:24/06/2022 02:01:06 +0000:   still waiting...
666:24/06/2022 02:01:07 +0000:   still waiting...
666:24/06/2022 02:01:08 +0000:   still waiting...
666:24/06/2022 02:01:09 +0000:   still waiting...
666:24/06/2022 02:01:10 +0000:   still waiting...
666:24/06/2022 02:01:11 +0000:   still waiting...
666:24/06/2022 02:01:12 +0000:   still waiting...
666:24/06/2022 02:01:13 +0000:   still waiting...
666:24/06/2022 02:01:14 +0000:   still waiting...
666:24/06/2022 02:01:16 +0000:   still waiting...
666:24/06/2022 02:01:17 +0000:   still waiting...
666:24/06/2022 02:01:18 +0000:   still waiting...
666:24/06/2022 02:01:19 +0000:   still waiting...
666:24/06/2022 02:01:20 +0000:   still waiting...
666:24/06/2022 02:01:21 +0000:   still waiting...
666:24/06/2022 02:01:22 +0000:   still waiting...
666:24/06/2022 02:01:23 +0000:   still waiting...
666:24/06/2022 02:01:25 +0000:   still waiting...
666:24/06/2022 02:01:26 +0000:   still waiting...
666:24/06/2022 02:01:27 +0000:   still waiting...
666:24/06/2022 02:01:28 +0000:   still waiting...
666:24/06/2022 02:01:29 +0000:   still waiting...
666:24/06/2022 02:01:30 +0000:   still waiting...
666:24/06/2022 02:01:31 +0000:   still waiting...
666:24/06/2022 02:01:32 +0000:   still waiting...
666:24/06/2022 02:01:33 +0000:   still waiting...
666:24/06/2022 02:01:35 +0000:   still waiting...
666:24/06/2022 02:01:36 +0000:   still waiting...
666:24/06/2022 02:01:37 +0000:   still waiting...
666:24/06/2022 02:01:38 +0000:   still waiting...
666:24/06/2022 02:01:39 +0000:   still waiting...
666:24/06/2022 02:01:40 +0000:   still waiting...
666:24/06/2022 02:01:41 +0000:   still waiting...
666:24/06/2022 02:01:42 +0000:   still waiting...
666:24/06/2022 02:01:44 +0000:   still waiting...
666:24/06/2022 02:01:45 +0000:   still waiting...
666:24/06/2022 02:01:46 +0000:   still waiting...
666:24/06/2022 02:01:47 +0000:   still waiting...
666:24/06/2022 02:01:48 +0000:   timeout, aborting.
and none of the standard CF services are running. Where did the weird 23:09 time come from?
Rebooted it (at 11:44 BST - the front panel clock is fast) and all OK.
Code: 
--------- Info for Modinit PID 594 ---------
594: Date:       Fri Jun 24 11:52:29 UTC 2022
594: MDEV:       sda1
594: ACTION:     add
594: Model:      HD
594: Device:     /dev/sda1
594: Disk:       sda

594:24/06/2022 11:52:29 +0000: sda1 is candidate for mod [/media/drive1]
594:24/06/2022 11:52:29 +0000: Waiting for disk to become ready...
594:24/06/2022 11:52:30 +0000:   disk ready after 0 seconds
594:24/06/2022 11:52:30 +0000: /dev/sda1 is formatted as ext2/3
594:24/06/2022 11:52:30 +0000: /dev/sda1 is NOT removable.
594:24/06/2022 11:52:30 +0000: /dev/sda1 is connected via USB.
594:24/06/2022 11:52:30 +0000: /dev/sda1 partition type dos
594:24/06/2022 11:52:30 +0000: Waiting for the disk to mount...
594:24/06/2022 11:52:31 +0000:   still waiting...
594:24/06/2022 11:52:32 +0000:   /dev/sda1 mounted on /media/drive1
594:24/06/2022 11:52:32 +0000:   mounted after 1 second.
594:24/06/2022 11:52:32 +0000: +++ Running modinit +++
594:24/06/2022 10:44:18 +0000: +++ Modinit complete +++
594:24/06/2022 10:44:18 +0000: >>> /mod/etc/mdev/z9samba add /dev/sda1
594:24/06/2022 10:44:18 +0000:     /media/drive1 /tmp/tmp.r2Q3Ku
594:24/06/2022 10:44:19 +0000: <<< /mod/etc/mdev/z9samba
594:24/06/2022 10:44:19 +0000: Considering package scan on /media/drive1
594:24/06/2022 10:44:19 +0000: sda: Non-removable disk, skipping package scan.
 
In the first log the code in /etc/mdev/run-and-gun is waiting for the Humax settop program to mount the disk so that it can check for /mod and launch CF stuff (via /sbin/modinit) if found. Possibly the settop program crashed (what was on the screen?) or the disk had some transient issue; if it was found to have a filesystem issue the settop program could have run something like fsck which might have taken longer than the timeout to complete. These command templates are in the settop binary, of which the second is particularly relevant:
Code: 
e2fsck -F -j ext3 -p %s
e2fsck -F -j ext3 -f -y %s
For some reason they use -F which according to man e2fsck is:
... Only really useful for doing e2fsck time trials.
Click to expand...
 
/df said:
Possibly the settop program crashed (what was on the screen?)
Click to expand...
Nope. Picture and sound working normally.
/df said:
or the disk had some transient issue; if it was found to have a filesystem issue the settop program could have run something like fsck which might have taken longer than the timeout to complete.
Click to expand...
Doesn't seem to be that either. dumpe2fs says filesystem last checked on 10 Feb, which is when the filesystem was created.
MikeSh said:
(The picture ... )
Click to expand...
I expect that surfaces every time there's a story about dormice. There must've been one around the time I joined here and was looking for something as an avatar and that just happened to appeal. I quite like the second picture too...
 
prpr said:
and none of the standard CF services are running.
Click to expand...
It strikes me your USB storage was off-line. Mine goes off-line sometimes too, sometimes a reboot sorts it or other times I have to jiggle the connections. But if that were the case I don't know where your log came from...
 
You must log in or register to reply here.
Back
Top