LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 02-12-2016, 05:56 AM   #1
chris_crunch
Member
 
Registered: Jan 2016
Location: Braintree, Essex
Distribution: Ubuntu 14.04
Posts: 107

Rep: Reputation: Disabled
Linux Crashed?


When I started the computer up this morning, it said something along the lines of...

Code:
There's an error in the /home directory...
File system check or mount failed. A maintenance shell will now be started...
I'm paraphrasing, but I did something like tell it to check and fix errors, and it's working again.

Umm... what do I do? Is it possible to run hardware diagnostics to try and fix some stuff?
 
Old 02-12-2016, 06:34 AM   #2
wpeckham
Senior Member
 
Registered: Apr 2010
Location: Continental USA
Distribution: Debian, Ubuntu, Fedora, RedHat, DSL, Puppy, CentOS, Knoppix, Mint-DE, Sparky, Vsido, tinycore, Q4OS
Posts: 2,379

Rep: Reputation: 961Reputation: 961Reputation: 961Reputation: 961Reputation: 961Reputation: 961Reputation: 961Reputation: 961
Need More Data.

That does not sound like a hardware failure, hardware is not fixed by running software.
It sounds like you might have had a slight partition or file system corruption that fsck was able to repair. If that is the case, there may be nothing more to do now. I am more worried about preventing the problem going forward.

Have you seen this before?
What was your shutdown procedure during the preceding session?
How is this machine normally used?

And perhaps most important:
Can you tell us anything about that partition or file system?
 
Old 02-12-2016, 08:48 AM   #3
jpollard
Senior Member
 
Registered: Dec 2012
Location: Washington DC area
Distribution: Fedora, CentOS, Slackware
Posts: 4,713

Rep: Reputation: 1279Reputation: 1279Reputation: 1279Reputation: 1279Reputation: 1279Reputation: 1279Reputation: 1279Reputation: 1279Reputation: 1279
Did you complete a shutdown the previous night?

The errors are typical of what you would see with an incomplete shutdown before powering off.
 
Old 02-12-2016, 05:42 PM   #4
jefro
Moderator
 
Registered: Mar 2008
Posts: 17,101

Rep: Reputation: 2552Reputation: 2552Reputation: 2552Reputation: 2552Reputation: 2552Reputation: 2552Reputation: 2552Reputation: 2552Reputation: 2552Reputation: 2552Reputation: 2552
Usually it's an issue with power down agreed.

Can check smart status on drive.
 
Old 02-12-2016, 07:51 PM   #5
Ztcoracat
LQ Guru
 
Registered: Dec 2011
Distribution: Slackware
Posts: 7,873
Blog Entries: 10

Rep: Reputation: Disabled
https://wiki.archlinux.org/index.php/S.M.A.R.T.
 
Old 02-12-2016, 08:51 PM   #6
frankbell
LQ Guru
 
Registered: Jan 2006
Location: Virginia, USA
Distribution: Slackware, Debian, Mageia, and whatever VMs I happen to be playing with
Posts: 12,784
Blog Entries: 17

Rep: Reputation: 3315Reputation: 3315Reputation: 3315Reputation: 3315Reputation: 3315Reputation: 3315Reputation: 3315Reputation: 3315Reputation: 3315Reputation: 3315Reputation: 3315
Sounds as if the computer at boot noted that one or more partitions need to have an fsck (file system check, sort of similar to DOS/Windows checkdisk) run on it. Whatever you did gave permission for the fsck, and not everything is hunky-dory.

See man fsck for more.
 
Old 02-17-2016, 08:21 AM   #7
chris_crunch
Member
 
Registered: Jan 2016
Location: Braintree, Essex
Distribution: Ubuntu 14.04
Posts: 107

Original Poster
Rep: Reputation: Disabled
Hey guys, was out for a while- busy with personal related issues and what not. Sorry for the late reply.
Okay, back to this issue. Hmmm. Well I tried this and shat my pants a litle. I really am a linux newbie.

Code:
 chris@chris-crunch:~/apps/caffe-master$ fsck
fsck from util-linux 2.20.1
e2fsck 1.42.9 (4-Feb-2014)
/dev/sda1 is mounted.



WARNING!!!  The filesystem is mounted.   If you continue you ***WILL***
cause ***SEVERE*** filesystem damage.


Do you really want to continue<n>? no
check aborted.
e2fsck 1.42.9 (4-Feb-2014)
/dev/sdb6 is mounted.



WARNING!!!  The filesystem is mounted.   If you continue you ***WILL***
cause ***SEVERE*** filesystem damage.


Do you really want to continue<n>? no
check aborted.
e2fsck 1.42.9 (4-Feb-2014)
/dev/sdb7 is mounted.



WARNING!!!  The filesystem is mounted.   If you continue you ***WILL***
cause ***SEVERE*** filesystem damage.


Do you really want to continue<n>? no
check aborted.
e2fsck 1.42.9 (4-Feb-2014)
/dev/sdb1 is mounted.



WARNING!!!  The filesystem is mounted.   If you continue you ***WILL***
cause ***SEVERE*** filesystem damage.


Do you really want to continue<n>? no
check aborted.
So I rapidly clicked no, no, ...

At the minute the computer is working fine for the most part. Although it does crash from time to time (not when I'm doing anything specific).

Then when I turn it on I get SIX messages on the desktop saying

Quote:
"A problem with your system was detected. Do you wish to file a report?"
or something like that. At which point I close the boxes and carry on doing what I'm doing...
Currently I'm sitting here googling this stuff to get a better idea of what the heck is going on.
If you need more specific information from me I will provide it.


So... by that message, it looks like the computer is partitioned into 4 drives? That are mounted? Hmmm...so do I need to unmount before performing an fsck...

Yes, it was an incomplete shutdown. I have this bloody 'dell' monitor that sometimes goes into powersave mode for no reason, and the only way to get it working again is to manually shutdown the computer and reboot it. I've no idea how to fix this issue, I've googled it and it seems a lot of people are having it. But I hope the force shutting down (which I regularly have to do, like once a day) won't cause permanent damage to the computer...

Last edited by chris_crunch; 02-17-2016 at 08:26 AM.
 
Old 02-17-2016, 08:27 AM   #8
chris_crunch
Member
 
Registered: Jan 2016
Location: Braintree, Essex
Distribution: Ubuntu 14.04
Posts: 107

Original Poster
Rep: Reputation: Disabled
This may be useful?
Code:
chris@chris-crunch:~/apps/caffe-master$ mount
/dev/sda1 on / type ext4 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/cgroup type tmpfs (rw)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755)
none on /sys/fs/pstore type pstore (rw)
/dev/sdb6 on /data1 type ext4 (rw)
/dev/sdb7 on /data2 type ext4 (rw)
/dev/sdb1 on /home type ext4 (rw)
systemd on /sys/fs/cgroup/systemd type cgroup (rw,noexec,nosuid,nodev,none,name=systemd)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,user=chris)
(What on earth does this mean... )
 
Old 02-17-2016, 09:39 AM   #9
jpollard
Senior Member
 
Registered: Dec 2012
Location: Washington DC area
Distribution: Fedora, CentOS, Slackware
Posts: 4,713

Rep: Reputation: 1279Reputation: 1279Reputation: 1279Reputation: 1279Reputation: 1279Reputation: 1279Reputation: 1279Reputation: 1279Reputation: 1279
Quote:
Originally Posted by chris_crunch View Post
This may be useful?
Code:
chris@chris-crunch:~/apps/caffe-master$ mount
/dev/sda1 on / type ext4 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/cgroup type tmpfs (rw)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755)
none on /sys/fs/pstore type pstore (rw)
/dev/sdb6 on /data1 type ext4 (rw)
/dev/sdb7 on /data2 type ext4 (rw)
/dev/sdb1 on /home type ext4 (rw)
systemd on /sys/fs/cgroup/systemd type cgroup (rw,noexec,nosuid,nodev,none,name=systemd)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,user=chris)
(What on earth does this mean... )
This is a list of all filesystems that have been mounted.

The first column is the device the data resides on. Entries:
"proc","sysfs", "none","devpts","tmpfs","systemd", and "gvfsd-fuse" are not disk based filesystems.

proc - mapps a filesystem view into the kernel proc table, and various other kernel data structures.
sysfs - kernel data structures (monitoring and tuning)
"none" - no device is associated. These frequently are identified as "type tmpfs" because tmpfs is memory allocated for use to hold arbitrary data.
devpts - pseudo terminal device tables
tmpfs - used for various things (it is just named tmpfs, it isn't a real device) systemd uses tmpfs for scratch data that is discarded at each shutdown.
systemd - named for systemd usage for CPU scheduling control.

The "on" list is where in the filesystem hierarchy the particular mount is put for access.

The "type" is the filesystem structure being mounted, hence ext4 for some disks. Each different filesystem has a designated name (the list of what is recognized by the kernel is in /proc/filesystems; note not all filesystems are kernel based - thus the "system" and gvfsd-fuse" are not kernel, but provided by a daemon for information/control).

The parts in parenthesis are options passed to the filesystem.
 
1 members found this post helpful.
Old 02-17-2016, 09:46 AM   #10
jpollard
Senior Member
 
Registered: Dec 2012
Location: Washington DC area
Distribution: Fedora, CentOS, Slackware
Posts: 4,713

Rep: Reputation: 1279Reputation: 1279Reputation: 1279Reputation: 1279Reputation: 1279Reputation: 1279Reputation: 1279Reputation: 1279Reputation: 1279
Now, back to the fsck...

Normally, you would NOT use fsck to repair a mounted filesystem. The problem is that fsck bypasses the kernel filesystem to rebuild things - and a mounted filesystem will have data copied into the kernel. Having two paths that write to the same filesystem WILL cause corruption of that filesystem.

It WORKS if the filesystem is mounted read-only because then, anything copied into the kernel will NOT be modified by the kernel. Thus only one write path would exist. It is also strongly recommended that immediately after fixing such a filesystem that the system be rebooted (using the data the kernel has copied might not work... as the disk resident data may have been modified, and things won't match what the kernel expects).

Normally fsck runs are done at single user mode - where only ONE disk based filesystems is mounted (root), and that one is usually mounted read only (thus can be fixed, with an immediate reboot afterward). If root is mounted read/write, then don't run fsck on it. Fsck will detect when a partition is mounted, and warn you (as you found).

One other thing: Usually a filesystem will not mount if it requires fsck to be run on the disk/partition.

Last edited by jpollard; 02-17-2016 at 09:48 AM.
 
Old 02-17-2016, 09:49 AM   #11
jpollard
Senior Member
 
Registered: Dec 2012
Location: Washington DC area
Distribution: Fedora, CentOS, Slackware
Posts: 4,713

Rep: Reputation: 1279Reputation: 1279Reputation: 1279Reputation: 1279Reputation: 1279Reputation: 1279Reputation: 1279Reputation: 1279Reputation: 1279
If a monitor goes into "power save" with no reason, you usually have a video card problem (though a bad cable can do it too).
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
i crashed linux shamimkhaliq Linux - Newbie 9 03-13-2009 10:50 PM
Linux Crashed Could not get # or $ prompt jspsandhu Linux - Software 1 06-25-2005 12:02 AM
Linux crashed and I can't get up aaronlc Linux - Newbie 3 06-15-2005 09:57 PM
my Linux crashed salmanucit Linux - Software 4 07-24-2004 08:12 AM
Linux crashed tonystaf Linux - Software 3 05-27-2004 08:05 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 03:42 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration