14 Jan
2012
14 Jan
'12
7:48 p.m.
Hi Mathew,
On Sat, Jan 14, 2012 at 04:34:41PM -0000, Mathew Newton wrote:
Following a recent IPv4 numbering update I removed my
old IPv4 address
today and shutdown/boot(ed) my VPS from the console. I noticed a few
warnings/errors in the boot log which I don't recall having seen before:
Setting the system clock.
Unable to set System Clock to: Sat Jan 14 16:11:03 UTC 2012 (warning).
I believe this is the init scripts trying to set system time from
the hardware clock, which it can't do because a VM doesn't have a
hardware clock. Therefore I think it's harmless.
[... non-related output removed ...]
Not activating swap on swapfile. (warning).
I believe this is a deliberate choice of the init scripts to not
activate swap that is on swap*files* until after a fsck of the
filesystem that it's on has been done. So again I think this is
harmless/normal.
Further down in the output you would expect to see the swapfile
enabled.
[... non-related output removed ...]
Will now check root file system:fsck 1.41.3 (12-Oct-2008)
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a -C0 /dev/xvda
/ primary superblock features different from backup, check forced.
You would expect this after a resize because certain data structures
change...
/: ***** REBOOT LINUX *****
/: 138212/1310720 files (10.2% non-contiguous), 3340623/5242880 blocks
fsck died with exit status 3
failed!
The file system check corrected errors on the root partition but requested
...however I would not have expected fsck to find any
inconsistencies. But I guess that happens from time to time.
I recently increased the size of my VPS disk storage
(successfully) and so
I'm wondering if the fsck check was as a result of that? The subsequent
boot completed successfully so I'm not overly concerned... or should I be?
The only thing out of the ordinary in my opinion is fsck wanting to
restart, and as it went without incident after that, I personally
would not worry.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting