[Bug 1424062] Re: Disk suddenly became unaccesible (all of it)

2015-04-22 Thread Launchpad Bug Tracker
[Expired for Ubuntu because there has been no activity for 60 days.] ** Changed in: ubuntu Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1424062 Title: Disk sud

[Bug 1424062] Re: Disk suddenly became unaccesible (all of it)

2015-02-21 Thread Manuel Cantu Reinhard
Hi, this justo happened again. Common factor is chrome. This time unlike the previous one it crashed. dmesg crashes the terminal. sudoing gives: unable to open /var/lib/sudo/manuel/1: no such file or directory. ls works, but ls -lrth crashes the terminal. Tab to auto complete in terminal gives mess

[Bug 1424062] Re: Disk suddenly became unaccesible (all of it)

2015-02-21 Thread Manuel Cantu Reinhard
Software I've installed from when this did not happen to when it started. CiscoVPN, putty, SSL/SSH VNC Viewer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1424062 Title: Disk suddenly became unacc

[Bug 1424062] Re: Disk suddenly became unaccesible (all of it)

2015-02-21 Thread Manuel Cantu Reinhard
Please discard the crash for chrome, from the restored tabs I see it was caused because it was unable to read or write from/to disk. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1424062 Title: Disk

[Bug 1424062] Re: Disk suddenly became unaccesible (all of it)

2015-02-21 Thread Martin Pitt
Next time this happens, please check "dmesg", and record it. You could e. g. put it onto an USB stick, or copy it to a remote host with something like $ dmesg | sudo tee /run/dmesg.txt $ scp /run/dmesg.txt user@some.server: It for sure sounds like what Philip said, the disk getting mounted rea

[Bug 1424062] Re: Disk suddenly became unaccesible (all of it)

2015-02-20 Thread Phillip Susi
What you describe sounds like some sort of error caused the filesystem to be remounted read/only. Unfortunately, that prevents recording the logs of what happened which were lost when you rebooted. Without that, further diagnosis won't be possible. For now I would suggest fscking the filesystem