2

Working on Ubuntu Desktop 17.04 (Host) with VirtualBox.
Using Ubuntu Server 16.04 on each VM (Guest) as WebServer.

Trying to cp -r /var/www content to a specific shared folder wwwfiles to Host.

Working on Guest after a random period of time the host stops to responding (freezes processes, terminal, Mouse and Keyboard interaction) and reboots by itself. This happens as well without working on both of them (host/guest).

Can't get into error logs cd /var/log/syslog (because of sporadically reboots/interruption) on host as on guest.

Looking and reading around is that What I did until now (in command line):

sudo rm /var/lib/apt/lists/*

sudo rm /var/cache/apt/archives/lock/*

sudo apt-get update

none of these has worked.

My Intent is to:

  • Get all data (related mysql of-and running WebBased Applications as Website Data) into a USB Stick to install on a fresh system (supposed corrupted maybe because of a conflict with VirtualBox).

UPDATE: 07.09.2017

couldn't leave the problem there so started to work on.
It seems it's more a fileSystem issue.
Executing fsck -nf /dev/sda1as root I got following error list:

Inode [number] was part of orphaned inode list. IGNORED
made all passes
structure
connectivity
counts
summary information
It's in fact a FileSystem Error... due I get the message after the check:
/dev/sda1 ******** WARNING: Filesystem still has error ********
Not a Hardware as thought.

Gianni
  • 111
  • 3
  • 16

1 Answers1

0

I would begin by insuring that the foundation is sound by booting from verified good live media . Check the SMART status of the host drive and run a memtest.

The reason we do the above first is that if the hardware is malfunctioning any repairs we attempt on the filesystem using the same hardware are likely to fail and can't be trusted.

If no errors are found proceed to actually repair the filesystem in question. The fsck command you ran reports the errors but doesn;t actually make any attempt to repair the filesystem. The orphaned inode mentioned is explained well here.

I would then manually run fsck repairs on the filesystem with the command sudo fsck -y /dev/sda1 as based on your question /dev/sda1 is the partition that you are having difficulty with (if it's a different block device, adjust that accordingly.

If you are able to accomplish all this without the system rebooting when booted from live media, but still have the same issue when booted from /dev/sda1 [edit] the results into your post, drop me a comment and I'll expand and revise this answer as necessary.

Sources:

Experience.

Elder Geek
  • 36,752