openSUSE 13.1 KDE crashed!

snowsun · October 5, 2014, 1:47pm

Hi,
today, the system crashed twice: mouse and keyboard are not responded at all.
I tried Ctrl+Alt+F1-6, It does not worked…
I have to push the computer’s switch to force shut down…
I look at the /var/log/message: (However, I can not understand it)
ps: when the computer crashed, I am just surfing on the Internet and use vim at the same time.
Who can tell me what is the problem? I do no want to try other Linux Distributions now…
Thank you.


2014-10-05T17:37:33.087607+08:00 jamir kernel:   408.631900] fuse init (API version 7.22)
2014-10-05T17:37:33.088846+08:00 jamir systemd[1]: Mounting FUSE Control File System...
2014-10-05T17:37:33.103692+08:00 jamir systemd[1]: Mounted FUSE Control File System.
2014-10-05T17:37:34.091942+08:00 jamir ntfs-3g[1538]: Version 2013.1.13 external FUSE 29
2014-10-05T17:37:34.092467+08:00 jamir ntfs-3g[1538]: Mounted /dev/sdb1 (Read-Write, label "NTFS", NTFS 3.1)
2014-10-05T17:37:34.092770+08:00 jamir ntfs-3g[1538]: Cmdline options: rw,nodev,nosuid,uid=1000,gid=100,dmask=0077,fmask=0177,uhelper=udisks2
2014-10-05T17:37:34.093063+08:00 jamir ntfs-3g[1538]: Mount options: rw,nodev,nosuid,uhelper=udisks2,allow_other,nonempty,relatime,default_permissions,fsname=/dev/sdb1,blkdev,blksize=4096
2014-10-05T17:37:34.093431+08:00 jamir ntfs-3g[1538]: Global ownership and permissions enforced, configuration type 1
2014-10-05T17:37:34.100674+08:00 jamir udisksd[1252]: Mounted /dev/sdb1 at /run/media/aries/NTFS on behalf of uid 1000
2014-10-05T17:37:36.579146+08:00 jamir kernel:   412.123950] FAT-fs (sdb2): error, invalid access to FAT (entry 0x03ed77b8)
2014-10-05T17:37:36.580187+08:00 jamir kernel:   412.124739] FAT-fs (sdb2): error, invalid access to FAT (entry 0x670da0f1)
2014-10-05T17:37:36.581162+08:00 jamir kernel:   412.125566] FAT-fs (sdb2): error, invalid access to FAT (entry 0xc3dbb4be)
2014-10-05T17:37:36.582165+08:00 jamir kernel:   412.126940] FAT-fs (sdb2): error, invalid access to FAT (entry 0xde6be38e)
2014-10-05T17:37:36.583149+08:00 jamir kernel:   412.127780] FAT-fs (sdb2): error, invalid access to FAT (entry 0xfc3dacbc)
2014-10-05T17:37:41.303942+08:00 jamir dbus[563]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
2014-10-05T17:37:42.881766+08:00 jamir dbus[563]: [system] Successfully activated service 'org.freedesktop.PackageKit'
2014-10-05T17:38:37.803145+08:00 jamir kernel:   473.347168] FAT-fs (sdb2): error, invalid access to FAT (entry 0x4a3efda2)
2014-10-05T17:38:41.430141+08:00 jamir kernel:   476.974283] FAT-fs (sdb2): error, invalid access to FAT (entry 0x185de89d)
2014-10-05T17:38:41.431133+08:00 jamir kernel:   476.975142] FAT-fs (sdb2): error, invalid access to FAT (entry 0xfc01a5b6)
2014-10-05T17:38:41.431144+08:00 jamir kernel:   476.975964] FAT-fs (sdb2): error, invalid access to FAT (entry 0x088c210d)
2014-10-05T17:38:41.432128+08:00 jamir kernel:   476.976840] FAT-fs (sdb2): error, invalid access to FAT (entry 0x11e86482)
2014-10-05T17:38:41.433151+08:00 jamir kernel:   476.977638] FAT-fs (sdb2): error, invalid access to FAT (entry 0x3e713f11)
2014-10-05T17:38:41.434127+08:00 jamir kernel:   476.978477] FAT-fs (sdb2): error, invalid access to FAT (entry 0x5b0b2b47)
2014-10-05T17:38:41.435129+08:00 jamir kernel:   476.979430] FAT-fs (sdb2): error, invalid access to FAT (entry 0xd73074fe)
2014-10-05T17:38:41.436152+08:00 jamir kernel:   476.980329] FAT-fs (sdb2): error, invalid access to FAT (entry 0x3facda6e)
2014-10-05T17:38:41.437150+08:00 jamir kernel:   476.981201] FAT-fs (sdb2): error, invalid access to FAT (entry 0x203f5168)
2014-10-05T17:38:41.438132+08:00 jamir kernel:   476.982141] FAT-fs (sdb2): error, invalid access to FAT (entry 0x209ce477)
2014-10-05T17:38:41.438140+08:00 jamir kernel:   476.982969] FAT-fs (sdb2): error, invalid access to FAT (entry 0x8477f250)
2014-10-05T17:38:41.439130+08:00 jamir kernel:   476.983837] FAT-fs (sdb2): error, invalid access to FAT (entry 0x6419b51b)
2014-10-05T17:38:41.440127+08:00 jamir kernel:   476.984688] FAT-fs (sdb2): error, invalid access to FAT (entry 0xe85611ef)
2014-10-05T17:38:41.441128+08:00 jamir kernel:   476.985572] FAT-fs (sdb2): error, invalid access to FAT (entry 0x3a193918)
2014-10-05T17:38:41.442136+08:00 jamir kernel:   476.986409] FAT-fs (sdb2): error, invalid access to FAT (entry 0x6983de9f)
2014-10-05T17:38:41.449128+08:00 jamir kernel:   476.993735] FAT-fs (sdb2): error, invalid access to FAT (entry 0x707a126f)
2014-10-05T17:38:41.450129+08:00 jamir kernel:   476.994657] FAT-fs (sdb2): error, invalid access to FAT (entry 0x9fb00516)
2014-10-05T17:38:41.451128+08:00 jamir kernel:   476.995521] FAT-fs (sdb2): error, invalid access to FAT (entry 0xfdbfb4bb)
2014-10-05T17:38:45.028141+08:00 jamir kernel:   480.572851] FAT-fs (sdb2): error, invalid access to FAT (entry 0x04a84b8d)
2014-10-05T17:38:45.029161+08:00 jamir kernel:   480.573621] FAT-fs (sdb2): error, invalid access to FAT (entry 0xc400a83d)
2014-10-05T17:38:45.030165+08:00 jamir kernel:   480.574538] FAT-fs (sdb2): error, invalid access to FAT (entry 0xed7bd1d9)
2014-10-05T17:38:45.031181+08:00 jamir kernel:   480.575396] FAT-fs (sdb2): error, invalid access to FAT (entry 0x7ee1190d)
2014-10-05T17:38:45.032170+08:00 jamir kernel:   480.576231] FAT-fs (sdb2): error, invalid access to FAT (entry 0x45e29061)
2014-10-05T17:38:45.033244+08:00 jamir kernel:   480.577133] FAT-fs (sdb2): error, invalid access to FAT (entry 0xd7e600cf)
2014-10-05T17:38:45.033254+08:00 jamir kernel:   480.577963] FAT-fs (sdb2): error, invalid access to FAT (entry 0xa77286cf)
2014-10-05T17:38:45.034172+08:00 jamir kernel:   480.578791] FAT-fs (sdb2): error, invalid access to FAT (entry 0x46908a9b)
2014-10-05T17:38:45.035168+08:00 jamir kernel:   480.579649] FAT-fs (sdb2): error, invalid access to FAT (entry 0xdcb6fad0)
2014-10-05T17:38:45.036168+08:00 jamir kernel:   480.580559] FAT-fs (sdb2): error, invalid access to FAT (entry 0x1e7978b6)
2014-10-05T17:38:45.074163+08:00 jamir kernel:   480.618520] FAT-fs (sdb2): error, invalid access to FAT (entry 0x37d2853c)
2014-10-05T17:38:45.075143+08:00 jamir kernel:   480.619502] FAT-fs (sdb2): error, invalid access to FAT (entry 0xc6ec698b)
2014-10-05T17:38:45.076153+08:00 jamir kernel:   480.620408] FAT-fs (sdb2): error, invalid access to FAT (entry 0x74b95b86)
2014-10-05T17:38:45.077146+08:00 jamir kernel:   480.621342] FAT-fs (sdb2): error, invalid access to FAT (entry 0x5b60c236)
2014-10-05T17:38:45.078148+08:00 jamir kernel:   480.622705] FAT-fs (sdb2): error, invalid access to FAT (entry 0xcc3f13bb)
2014-10-05T17:38:45.079145+08:00 jamir kernel:   480.623855] FAT-fs (sdb2): error, invalid access to FAT (entry 0xf727b54a)
2014-10-05T17:38:45.081139+08:00 jamir kernel:   480.625067] FAT-fs (sdb2): error, invalid access to FAT (entry 0xa81cd01b)
2014-10-05T17:38:45.081162+08:00 jamir kernel:   480.625973] FAT-fs (sdb2): error, invalid access to FAT (entry 0x26a2e4ac)
2014-10-05T17:38:45.083142+08:00 jamir kernel:   480.627242] FAT-fs (sdb2): error, invalid access to FAT (entry 0xca17ef9f)
2014-10-05T17:38:45.084151+08:00 jamir kernel:   480.628425] FAT-fs (sdb2): error, invalid access to FAT (entry 0x70f2cd54)
2014-10-05T17:38:45.085142+08:00 jamir kernel:   480.629580] FAT-fs (sdb2): error, invalid access to FAT (entry 0x1c71abd1)
2014-10-05T17:38:45.086152+08:00 jamir kernel:   480.630694] FAT-fs (sdb2): error, invalid access to FAT (entry 0x2a16f8e7)
2014-10-05T17:38:45.087149+08:00 jamir kernel:   480.631867] FAT-fs (sdb2): error, invalid access to FAT (entry 0xc79fd395)
2014-10-05T17:38:45.088145+08:00 jamir kernel:   480.632969] FAT-fs (sdb2): error, invalid access to FAT (entry 0x64298f40)
2014-10-05T17:38:45.090148+08:00 jamir kernel:   480.634094] FAT-fs (sdb2): error, invalid access to FAT (entry 0x6ad0b5d7)
2014-10-05T17:38:45.091143+08:00 jamir kernel:   480.635303] FAT-fs (sdb2): error, invalid access to FAT (entry 0x7edf3662)
2014-10-05T17:38:45.092150+08:00 jamir kernel:   480.636440] FAT-fs (sdb2): error, invalid access to FAT (entry 0xb54779ba)
2014-10-05T17:38:45.093147+08:00 jamir kernel:   480.637628] FAT-fs (sdb2): error, invalid access to FAT (entry 0xbe20b635)
2014-10-05T17:38:45.094151+08:00 jamir kernel:   480.638892] FAT-fs (sdb2): error, invalid access to FAT (entry 0x77ea3889)
2014-10-05T17:38:45.096148+08:00 jamir kernel:   480.640047] FAT-fs (sdb2): error, invalid access to FAT (entry 0x469a8265)
2014-10-05T17:38:45.096172+08:00 jamir kernel:   480.640965] FAT-fs (sdb2): error, invalid access to FAT (entry 0x211ccdbd)
2014-10-05T17:38:45.098148+08:00 jamir kernel:   480.642230] FAT-fs (sdb2): error, invalid access to FAT (entry 0xea469343)
2014-10-05T17:38:45.099144+08:00 jamir kernel:   480.643375] FAT-fs (sdb2): error, invalid access to FAT (entry 0xed85bbd1)
2014-10-05T17:38:45.100158+08:00 jamir kernel:   480.644518] FAT-fs (sdb2): error, invalid access to FAT (entry 0xcfda0629)
2014-10-05T17:38:45.101148+08:00 jamir kernel:   480.645722] FAT-fs (sdb2): error, invalid access to FAT (entry 0xbc37ac03)
2014-10-05T17:38:45.103137+08:00 jamir kernel:   480.647812] FAT-fs (sdb2): error, invalid access to FAT (entry 0x7b2c1193)
2014-10-05T17:38:45.105140+08:00 jamir kernel:   480.649054] FAT-fs (sdb2): error, invalid access to FAT (entry 0xb365c03b)
2014-10-05T17:38:45.106154+08:00 jamir kernel:   480.650368] FAT-fs (sdb2): error, invalid access to FAT (entry 0x89ea73a4)
2014-10-05T17:38:45.107142+08:00 jamir kernel:   480.651565] FAT-fs (sdb2): error, invalid access to FAT (entry 0xfbd1c059)
2014-10-05T17:38:45.108153+08:00 jamir kernel:   480.652700] FAT-fs (sdb2): error, invalid access to FAT (entry 0xa85702bc)
2014-10-05T17:38:45.109140+08:00 jamir kernel:   480.653894] FAT-fs (sdb2): error, invalid access to FAT (entry 0xed1e4ad9)
2014-10-05T17:38:45.111140+08:00 jamir kernel:   480.655030] FAT-fs (sdb2): error, invalid access to FAT (entry 0x2fdadd4d)
2014-10-05T17:38:45.111161+08:00 jamir kernel:   480.655968] FAT-fs (sdb2): error, invalid access to FAT (entry 0xf7f93f19)
2014-10-05T17:38:45.113140+08:00 jamir kernel:   480.657245] FAT-fs (sdb2): error, invalid access to FAT (entry 0xc8503a62)
2014-10-05T17:38:45.114152+08:00 jamir kernel:   480.658380] FAT-fs (sdb2): error, invalid access to FAT (entry 0x1a5ba599)
2014-10-05T17:38:45.115146+08:00 jamir kernel:   480.659548] FAT-fs (sdb2): error, invalid access to FAT (entry 0x5afe1b32)
2014-10-05T17:38:45.116157+08:00 jamir kernel:   480.660856] FAT-fs (sdb2): error, invalid access to FAT (entry 0x1054fdb0)
2014-10-05T17:38:45.118146+08:00 jamir kernel:   480.662043] FAT-fs (sdb2): error, invalid access to FAT (entry 0x12f0ee34)
2014-10-05T17:38:45.119148+08:00 jamir kernel:   480.663280] FAT-fs (sdb2): error, invalid access to FAT (entry 0x1775a0fe)
2014-10-05T17:38:45.120151+08:00 jamir kernel:   480.664521] FAT-fs (sdb2): error, invalid access to FAT (entry 0x618343d0)
2014-10-05T17:38:45.121139+08:00 jamir kernel:   480.665690] FAT-fs (sdb2): error, invalid access to FAT (entry 0xd87be989)
2014-10-05T17:38:45.122155+08:00 jamir kernel:   480.666807] FAT-fs (sdb2): error, invalid access to FAT (entry 0x2bce058f)
2014-10-05T17:38:45.124147+08:00 jamir kernel:   480.668034] FAT-fs (sdb2): error, invalid access to FAT (entry 0x19c6096a)
2014-10-05T17:38:45.138151+08:00 jamir kernel:   480.682298] FAT-fs (sdb2): error, invalid access to FAT (entry 0xee36040e)
2014-10-05T17:38:45.139144+08:00 jamir kernel:   480.683552] FAT-fs (sdb2): error, invalid access to FAT (entry 0x2c1694f5)
2014-10-05T17:38:45.140148+08:00 jamir kernel:   480.684749] FAT-fs (sdb2): error, invalid access to FAT (entry 0xf5015581)
2014-10-05T17:38:45.141143+08:00 jamir kernel:   480.685976] FAT-fs (sdb2): error, invalid access to FAT (entry 0xc66cc852)
2014-10-05T17:38:45.143141+08:00 jamir kernel:   480.687134] FAT-fs (sdb2): error, invalid access to FAT (entry 0x9adbf11e)
2014-10-05T17:38:45.144154+08:00 jamir kernel:   480.688283] FAT-fs (sdb2): error, invalid access to FAT (entry 0xf864b553)
2014-10-05T17:38:45.145142+08:00 jamir kernel:   480.689544] FAT-fs (sdb2): error, invalid access to FAT (entry 0x20ce05b9)
2014-10-05T17:38:45.163814+08:00 jamir polkitd[606]: Unregistered Authentication Agent for unix-session:1 (system bus name :1.36, object path /org/kde/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
2014-10-05T17:38:48.822139+08:00 jamir kernel:   484.366203] FAT-fs (sdb2): error, invalid access to FAT (entry 0x7e6e570a)
2014-10-05T17:38:48.823131+08:00 jamir kernel:   484.367156] FAT-fs (sdb2): error, invalid access to FAT (entry 0xd47bfc69)
2014-10-05T17:38:52.491141+08:00 jamir kernel:   488.035895] FAT-fs (sdb2): error, invalid access to FAT (entry 0x833ccc53)
2014-10-05T17:38:54.158464+08:00 jamir org.kde.kuiserver[1089]: kuiserver: Fatal IO error: client killed
2014-10-05T17:38:54.726565+08:00 jamir kdm: :0[685]: pam_unix(xdm:session): session closed for user aries
2014-10-05T17:38:54.920927+08:00 jamir systemd[1]: Stopping Session 1 of user aries.
2014-10-05T17:38:54.922153+08:00 jamir systemd[1]: Stopped Session 1 of user aries.
2014-10-05T17:38:54.923082+08:00 jamir systemd[1]: Stopping Sound Card.
2014-10-05T17:38:54.924096+08:00 jamir systemd[1]: Stopped target Sound Card.
2014-10-05T17:38:54.927533+08:00 jamir systemd[1]: Stopping Stop Read-Ahead Data Collection 10s After Completed Startup.
2014-10-05T17:38:54.929477+08:00 jamir systemd[1]: Stopped Stop Read-Ahead Data Collection 10s After Completed Startup.
2014-10-05T17:38:54.930540+08:00 jamir systemd[1]: Stopping User Manager for 1000...
2014-10-05T17:38:54.931540+08:00 jamir systemd[1]: Stopping Graphical Interface.
2014-10-05T17:38:54.932565+08:00 jamir systemd[1]: Stopped target Graphical Interface.
2014-10-05T17:38:55.077925+08:00 jamir rsyslogd: [origin software="rsyslogd" swVersion="7.4.7" x-pid="569" x-info="http://www.rsyslog.com"] exiting on signal 15.

alanbortu · October 5, 2014, 5:42pm

On 10/05/2014 07:56 AM, snowsun wrote:
>
> Hi,
> today, the system crashed twice: mouse and keyboard are not responded at
> all.
> I tried Ctrl+Alt+F1-6, It does not worked…
> I have to push the computer’s switch to force shut down…
> I look at the /var/log/message: (However, I can not understand it)
> ps: when the computer crashed, I am just surfing on the Internet and use
> vim at the same time.
> Who can tell me what is the problem? I do no want to try other Linux
> Distributions now…
> Thank you.

Not too familiar with these issues, but can you paste the contents of
your /etc/fstab file? All I see in the dmesg output is stuff about FAT
and NTFS so I guess thats a place to start…

–
openSUSE Factory 64 bit
KDE 4.14.0

hcvv · October 5, 2014, 5:50pm

I doubt that this is about the crash, but you obviously have a non-Linux fiile system (FAT) in sdb2 and it generates a lot of errors. Maybe remove that temporary (in your /etc/fstab, put a # at the start of the line, or, when it is USB connected disconnect) and run for some time without it,checking if it stops crashing. In any case there is somethiong wrong here that needs repair, either software wise or hardware.

robin_listas · October 5, 2014, 6:15pm

On 2014-10-05 13:56, snowsun wrote:


>   2014-10-05T17:37:33.087607+08:00 jamir kernel:   408.631900] fuse init (API version 7.22)
>   2014-10-05T17:37:33.088846+08:00 jamir systemd[1]: Mounting FUSE Control File System...
>   2014-10-05T17:37:33.103692+08:00 jamir systemd[1]: Mounted FUSE Control File System.
>   2014-10-05T17:37:34.091942+08:00 jamir ntfs-3g[1538]: Version 2013.1.13 external FUSE 29
>   2014-10-05T17:37:34.092467+08:00 jamir ntfs-3g[1538]: Mounted /dev/sdb1 (Read-Write, label "NTFS", NTFS 3.1)
>   2014-10-05T17:37:34.092770+08:00 jamir ntfs-3g[1538]: Cmdline options: rw,nodev,nosuid,uid=1000,gid=100,dmask=0077,fmask=0177,uhelper=udisks2
>   2014-10-05T17:37:34.093063+08:00 jamir ntfs-3g[1538]: Mount options: rw,nodev,nosuid,uhelper=udisks2,allow_other,nonempty,relatime,default_permissions,fsname=/dev/sdb1,blkdev,blksize=4096
>   2014-10-05T17:37:34.093431+08:00 jamir ntfs-3g[1538]: Global ownership and permissions enforced, configuration type 1
>   2014-10-05T17:37:34.100674+08:00 jamir udisksd[1252]: Mounted /dev/sdb1 at /run/media/aries/NTFS on behalf of uid 1000
>   2014-10-05T17:37:36.579146+08:00 jamir kernel:   412.123950] FAT-fs (sdb2): error, invalid access to FAT (entry 0x03ed77b8)
>   2014-10-05T17:37:36.580187+08:00 jamir kernel:   412.124739] FAT-fs (sdb2): error, invalid access to FAT (entry 0x670da0f1)

What do you have in sdb1 and sdb2?


>   2014-10-05T17:38:52.491141+08:00 jamir kernel:   488.035895] FAT-fs (sdb2): error, invalid access to FAT (entry 0x833ccc53)
>   2014-10-05T17:38:54.158464+08:00 jamir org.kde.kuiserver[1089]: kuiserver: Fatal IO error: client killed
>   2014-10-05T17:38:54.726565+08:00 jamir kdm: :0[685]: pam_unix(xdm:session): session closed for user aries
>   2014-10-05T17:38:54.920927+08:00 jamir systemd[1]: Stopping Session 1 of user aries.
>   2014-10-05T17:38:54.922153+08:00 jamir systemd[1]: Stopped Session 1 of user aries.
>   2014-10-05T17:38:54.923082+08:00 jamir systemd[1]: Stopping Sound Card.
>   2014-10-05T17:38:54.924096+08:00 jamir systemd[1]: Stopped target Sound Card.
>   2014-10-05T17:38:54.927533+08:00 jamir systemd[1]: Stopping Stop Read-Ahead Data Collection 10s After Completed Startup.
>   2014-10-05T17:38:54.929477+08:00 jamir systemd[1]: Stopped Stop Read-Ahead Data Collection 10s After Completed Startup.
>   2014-10-05T17:38:54.930540+08:00 jamir systemd[1]: Stopping User Manager for 1000...
>   2014-10-05T17:38:54.931540+08:00 jamir systemd[1]: Stopping Graphical Interface.
>   2014-10-05T17:38:54.932565+08:00 jamir systemd[1]: Stopped target Graphical Interface.
>   2014-10-05T17:38:55.077925+08:00 jamir rsyslogd: [origin software="rsyslogd" swVersion="7.4.7" x-pid="569" x-info="http://www.rsyslog.com"] exiting on signal 15.

It is not crashing, it is halting.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

knurpht · October 5, 2014, 9:59pm

My 2 cents:

Either you have /home on a FAT partition (now damaged) which you should not have, or
Your FAT partition belongs to a windu install, which did not shut down properly.
In the last case you should try to repair the filesystem from windows

snowsun · October 6, 2014, 4:48am

This is what I have on my computer when it crashed:
(sdb and sdc are all connected by USB)


jamir:~ # cat /etc/fstab
/dev/disk/by-id/ata-WDC_WD1600AVVS-63L2B0_WD-WCAUZ1097968-part2 swap                 swap       defaults              0 0
/dev/disk/by-id/ata-WDC_WD1600AVVS-63L2B0_WD-WCAUZ1097968-part3 /                    ext4       acl,user_xattr        1 1
jamir:~ # fdisk -l

Disk /dev/sda: 160.0 GB, 160041885696 bytes, 312581808 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0xad250a1f

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1              63    52436159    26218048+   7  HPFS/NTFS/exFAT
/dev/sda2        52436992    56631295     2097152   82  Linux swap / Solaris
/dev/sda3        56631296    98574335    20971520    5  Extended
/dev/sda4   *    98574336   312581807   107003736   83  Linux
/dev/sda5        56633344    98574335    20970496    7  HPFS/NTFS/exFAT

Disk /dev/sdb: 1000.2 GB, 1000204885504 bytes, 1953525167 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x92f8cb33

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               2   781250001   390625000    7  HPFS/NTFS/exFAT
/dev/sdb2       781250003  1709384546   464067272    b  W95 FAT32
/dev/sdb3   *  1709384548  1953525166   122070309+  af  HFS / HFS+

Disk /dev/sdc: 500.1 GB, 500107862016 bytes, 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x016c8108

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1              63   104872319    52436128+   7  HPFS/NTFS/exFAT
/dev/sdc2   *   104872320   209744639    52436160   83  Linux
/dev/sdc3       209745920   314615807    52434944   83  Linux
/dev/sdc4       314617021   976769071   331076025+   f  W95 Ext'd (LBA)
/dev/sdc5       314617023   524345534   104864256    7  HPFS/NTFS/exFAT
/dev/sdc6       524345598   734074109   104864256    7  HPFS/NTFS/exFAT
/dev/sdc7       734074880   972960659   119442890    7  HPFS/NTFS/exFAT
/dev/sdc8       972972080   974923823      975872   82  Linux swap / Solaris
/dev/sdc9       974925872   976769071      921600   82  Linux swap / Solaris

snowsun · October 6, 2014, 4:52am

I agree with you. But didn’t the system generate some log file when the computer crashes like that? I want to find the reason. I remember that all of the log are written to /var/log/messages…
Thank you for your replay

snowsun · October 6, 2014, 4:57am

robin_listas:

On 2014-10-05 13:56, snowsun wrote:

What do you have in sdb1 and sdb2?


>   2014-10-05T17:38:54.929477+08:00 jamir systemd[1]: Stopped Stop Read-Ahead Data Collection 10s After Completed Startup.
>   2014-10-05T17:38:54.930540+08:00 jamir systemd[1]: Stopping User Manager for 1000...
>   2014-10-05T17:38:54.931540+08:00 jamir systemd[1]: Stopping Graphical Interface.
>   2014-10-05T17:38:54.932565+08:00 jamir systemd[1]: Stopped target Graphical Interface.
>   2014-10-05T17:38:55.077925+08:00 jamir rsyslogd: [origin software="rsyslogd" swVersion="7.4.7" x-pid="569" x-info="http://www.rsyslog.com"] exiting on signal 15.

It is not crashing, it is halting.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

sdb is a hard disk connected with the computer by USB.
Yes, that is the computer is shutdown. But It is done by press the switch of the computer… Doesn’t the system detect that unusual shutdown?

Thank you for your reply and advice

snowsun · October 6, 2014, 5:57am

Maybe. on the disk sdc I have installed openSUSE and Windows. And I truly have a partition of HPFS/NTFS/exFAT on my computer. What do you mean “repair the filesystem from windows”? Sadly, my computer crashed again when I reply you just now… These are the last log before I force the computer shut down by press the switch…

 2014-10-06T11:30:01.411471+08:00 jamir systemd[2646]: Failed to open private bus connection: Failed to connect to socket /run/user/0/dbus/user_bus_socket: No such file or directory 2014-10-06T11:30:01.452793+08:00 jamir systemd[2646]: Mounted /sys/fs/fuse/connections. 2014-10-06T11:30:01.454098+08:00 jamir systemd[2646]: Stopped target Sound Card. 2014-10-06T11:30:01.454968+08:00 jamir systemd[2646]: Starting Default. 2014-10-06T11:30:01.455698+08:00 jamir systemd[2646]: Reached target Default. 2014-10-06T11:30:01.456542+08:00 jamir systemd[2646]: Startup finished in 48ms. 2014-10-06T11:30:01.457722+08:00 jamir systemd[1]: Started User Manager for 0. 2014-10-06T11:30:01.641325+08:00 jamir /USR/SBIN/CRON[2645]: pam_unix(crond:session): session closed for user root 2014-10-06T11:31:24.561190+08:00 jamir kernel:   626.097044] vboxdrv: Found 2 processor cores. 2014-10-06T11:31:24.565198+08:00 jamir kernel:   626.101215] vboxdrv: fAsync=1 offMin=0x13e783 offMax=0x13e783 2014-10-06T11:31:24.565226+08:00 jamir kernel:   626.101291] vboxdrv: TSC mode is 'asynchronous', kernel timer mode is 'normal'. 2014-10-06T11:31:24.565230+08:00 jamir kernel:   626.101293] vboxdrv: Successfully loaded version 4.3.16 (interface 0x001a0007). 2014-10-06T11:31:24.789221+08:00 jamir kernel:   626.325188] vboxpci: IOMMU not found (not registered) 2014-10-06T11:34:11.477364+08:00 jamir systemd-logind[629]: Removed session 1. 2014-10-06T11:35:44.558667+08:00 jamir kernel:   884.304057] nouveau E  PGRAPH][0000:02:00.0] vm flush timeout 2014-10-06T11:35:48.560348+08:00 jamir kernel:   888.027030] nouveau E  PGRAPH][0000:02:00.0] PGRAPH TLB flush idle timeout fail 2014-10-06T11:35:48.560471+08:00 jamir kernel:   888.027030] nouveau E  PGRAPH][0000:02:00.0] PGRAPH_STATUS  : 0x00b00003 BUSY DISPATCH TPROP TEX MP 2014-10-06T11:35:48.560541+08:00 jamir kernel:   888.027030] nouveau E  PGRAPH][0000:02:00.0] PGRAPH_VSTATUS0: 0x00000000 2014-10-06T11:35:48.560606+08:00 jamir kernel:   888.027030] nouveau E  PGRAPH][0000:02:00.0] PGRAPH_VSTATUS1: 0x00005068 TEXTURE

Thank you for your reply and your advice…

gogalthorp · October 6, 2014, 6:28am

FAT and NTFS file systems (ie Windows) can not in general be repaird from a Linux OS

Windows 8 has a feature called fastbooty that when used does not properly close down a file system when you quit Windows. It does that to make booting faster buit it leave the FS in such a state that Linux can not mount it.

Also if you have mounted a Windows file system as home it can cause very bad problems.

Show us as was asked the file
/etc/fstab
That will show what is being auto mounted

Also show us
fdisk -l
Note that is a lower case L not a one

In addition what video card do you have and did you install a driver for it?

Also for this kind of odd freeze it might be worth running a memory test ore night

there is one on the boot menu

snowsun · October 6, 2014, 7:42am

About the /etc/fstab and fdisk -l output. look up at my #6 reply.
about video card and driver:


jamir:~ # lspci
00:00.0 RAM memory: NVIDIA Corporation MCP67 Memory Controller (rev a2)
00:01.0 ISA bridge: NVIDIA Corporation MCP67 ISA Bridge (rev a2)
00:01.1 SMBus: NVIDIA Corporation MCP67 SMBus (rev a2)
00:01.2 RAM memory: NVIDIA Corporation MCP67 Memory Controller (rev a2)
00:02.0 USB controller: NVIDIA Corporation MCP67 OHCI USB 1.1 Controller (rev a2)
00:02.1 USB controller: NVIDIA Corporation MCP67 EHCI USB 2.0 Controller (rev a2)
00:04.0 USB controller: NVIDIA Corporation MCP67 OHCI USB 1.1 Controller (rev a2)
00:04.1 USB controller: NVIDIA Corporation MCP67 EHCI USB 2.0 Controller (rev a2)
00:06.0 IDE interface: NVIDIA Corporation MCP67 IDE Controller (rev a1)
00:07.0 Audio device: NVIDIA Corporation MCP67 High Definition Audio (rev a1)
00:08.0 PCI bridge: NVIDIA Corporation MCP67 PCI Bridge (rev a2)
00:09.0 IDE interface: NVIDIA Corporation MCP67 AHCI Controller (rev a2)
00:0b.0 PCI bridge: NVIDIA Corporation MCP67 PCI Express Bridge (rev a2)
00:0c.0 PCI bridge: NVIDIA Corporation MCP67 PCI Express Bridge (rev a2)
00:0d.0 PCI bridge: NVIDIA Corporation MCP67 PCI Express Bridge (rev a2)
00:0e.0 PCI bridge: NVIDIA Corporation MCP67 PCI Express Bridge (rev a2)
00:0f.0 PCI bridge: NVIDIA Corporation MCP67 PCI Express Bridge (rev a2)
00:10.0 PCI bridge: NVIDIA Corporation MCP67 PCI Express Bridge (rev a2)
00:11.0 PCI bridge: NVIDIA Corporation MCP67 PCI Express Bridge (rev a2)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:09.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8110SC/8169SC Gigabit Ethernet (rev 10)
02:00.0 VGA compatible controller: NVIDIA Corporation GT215 [GeForce GT 240] (rev a2)
02:00.1 Audio device: NVIDIA Corporation High Definition Audio Controller (rev a1)

robin_listas · October 6, 2014, 10:43am

On 2014-10-06 06:36, gogalthorp wrote:
>
> FAT and NTFS file systems (ie Windows) can not in general be repaird
> from a Linux OS

FAT can, but NTFS can not.
It is not done automatically on boot, I think, needs to be used manually.

Actually, fsck.vfat detects some problems that Windows does not.

> Show us as was asked the file
> /etc/fstab
> That will show what is being auto mounted

He did already, but it is strange, two lines only.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

robin_listas · October 6, 2014, 10:43am

On 2014-10-06 05:06, snowsun wrote:

> sdb is a hard disk connected with the computer by USB.
> Yes, that is the computer is shutdown. But It is done by press the
> switch of the computer… Doesn’t the system detect that unusual
> shutdown?

Well, that means that the desktop did not respond, but the machine did.
Linux did an orderly shutdown, not a forced shutdown by power off or
reset button. There is a difference, it is important to know that kernel
and systemd were responding.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

gogalthorp · October 6, 2014, 7:16pm

The fstab does not seem to match any of the drives


/dev/disk/by-id/ata-WDC_WD1600AVVS-63L2B0_WD-WCAUZ1097968-part2 swap                 swap       defaults              0 0 
/dev/disk/by-id/ata-WDC_WD1600AVVS-63L2B0_WD-WCAUZ1097968-part3 /                    ext4       acl,user_xattr        1 1

the 2 partition on none of the drives listed is a swap

Shutting down with power switch leaves the file system in a unpredictable state. But the a boot should correct this by running fsck on any partitions that may need it.

It is extremly unclear what is what on this system. Unplug the 1 gig USB and see if that helps I’m guessing the problem is there.

robin_listas · October 6, 2014, 8:28pm

On 2014-10-06 19:26, gogalthorp wrote:

> Shutting down with power switch leaves the file system in a
> unpredictable state. But the a boot should correct this by running fsck
> on any partitions that may need it.

That’s if you press and hold for > 4 seconds.
A brief press is captured by the system and handled properly.
Previously you configured this in inittab; now I suppose it is systemd.
The desktop can also intervene.

You can see in his log that his shutdown was orderly.

> It is extremly unclear what is what on this system.

True.

–
Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

snowsun · October 7, 2014, 3:17am

got it, thank you!

snowsun · October 7, 2014, 3:25am

gogalthorp:

The fstab does not seem to match any of the drives
/dev/disk/by-id/ata-WDC_WD1600AVVS-63L2B0_WD-WCAUZ1097968-part2 swap                 swap       defaults              0 0 
/dev/disk/by-id/ata-WDC_WD1600AVVS-63L2B0_WD-WCAUZ1097968-part3 /                    ext4       acl,user_xattr        1 1
the 2 partition on none of the drives listed is a swap

Shutting down with power switch leaves the file system in a unpredictable state. But the a boot should correct this by running fsck on any partitions that may need it.

It is extremly unclear what is what on this system. Unplug the 1 gig USB and see if that helps I’m guessing the problem is there.

/dev/sdb is just a hard disk of 1TB. Three partitions. One is NTFS, one is FAT, the last one is for Timemachine of mac.
/dev/sdc is the hard disk of my last laptop. Three OS on it. Win7, openSUSE, CentOS.
All of them are connected with the computer by USB.

However, When I unplugged /dev/sdb and /dev/sda. And switch to Xfce window manager. It does not crash until now.

Thank you so much.

snowsun · October 7, 2014, 3:27am

ok, thank you for you advice and help.

user · October 7, 2014, 11:17am

On Mon, 06 Oct 2014 04:06:01 GMT, snowsun
<snowsun@no-mx.forums.opensuse.org> wrote:

>session closed for user root 2014-10-06T11:31:24.561190+08:00 jamir kernel: 626.097044] vboxdrv: Found 2 processor cores.
>2014-10-06T11:31:24.565198+08:00 jamir kernel: 626.101215] vboxdrv: fAsync=1 offMin=0x13e783 offMax=0x13e783
>2014-10-06T11:31:24.565226+08:00 jamir kernel: 626.101291] vboxdrv: TSC mode is ‘asynchronous’, kernel timer mode is ‘normal’.
>2014-10-06T11:31:24.565230+08:00 jamir kernel: 626.101293] vboxdrv: Successfully loaded version 4.3.16 (interface 0x001a0007).
>2014-10-06T11:31:24.789221+08:00 jamir kernel: 626.325188] vboxpci: IOMMU not found (not registered)
>2014-10-06T11:34:11.477364+08:00 jamir systemd-logind[629]: Removed session 1. 2014-10-06T11:35:44.558667+08:00 jamir kernel:

You should tell us how virtualbox is part of this tangle

?-)

snowsun · October 7, 2014, 12:59pm

josephkk:

On Mon, 06 Oct 2014 04:06:01 GMT, snowsun
<snowsun@no-mx.forums.opensuse.org> wrote:

>session closed for user root 2014-10-06T11:31:24.561190+08:00 jamir kernel: 626.097044] vboxdrv: Found 2 processor cores.
>2014-10-06T11:31:24.565198+08:00 jamir kernel: 626.101215] vboxdrv: fAsync=1 offMin=0x13e783 offMax=0x13e783
>2014-10-06T11:31:24.565226+08:00 jamir kernel: 626.101291] vboxdrv: TSC mode is ‘asynchronous’, kernel timer mode is ‘normal’.
>2014-10-06T11:31:24.565230+08:00 jamir kernel: 626.101293] vboxdrv: Successfully loaded version 4.3.16 (interface 0x001a0007).
>2014-10-06T11:31:24.789221+08:00 jamir kernel: 626.325188] vboxpci: IOMMU not found (not registered)
>2014-10-06T11:34:11.477364+08:00 jamir systemd-logind[629]: Removed session 1. 2014-10-06T11:35:44.558667+08:00 jamir kernel:

You should tell us how virtualbox is part of this tangle

?-)

Maybe virtualbox is running when the computer is crashed.