On Mar 19, 2014, at 9:08 PM, pgaltieri . <pgaltieri(a)gmail.com> wrote:
On Wed, Mar 19, 2014 at 11:12 AM, Chris Murphy <lists(a)colorremedies.com> wrote:
What do you get for
smartctl -x /dev/sda
Here's the link
https://www.amazon.com/clouddrive/share?s=K76mJvZKSG0mr5pSoDGM7k
No obvious problems there. I'm suspicious about the many device ready not ready
transitions in the phy event counter.
So I unplugged the hub after making sure no drives were mounted and rebooted. Guess
what? I'm now back to the emergency mode prompt. If I boot off an older kernel I
again get the emergency mode prompt. What was working fine earlier no longer works.
Here's the shutdown log
https://www.amazon.com/clouddrive/share?s=-h_XGxyZT-ws_rNy16Jr0g
This system has been running Linux since December and I've never had as much trouble
with it as I have had these last few days. Arggggghhhhh!!!!!
1.
[ 18.334181] systemd[1]: boot-efi.mount mount process exited, code=exited status=0
[ 18.334187] systemd[1]: boot-efi.mount changed mounting -> mounted
OK so you re-enabled the mounting of /boot/efi and no longer get unknown filesystem type
'vfat' apparently.
2.
Like I said before this device has major file system problems. Because it's in your
fstab, and fails to mount, you are dropped to emergency shell. *Any* volume in fstab that
fails to mount at boot time causes the system to behave this way. Use nofail mount option
otherwise.
[ 19.400333] systemd[1]: Child 382 died (code=exited, status=1/FAILURE)
[ 19.400335] systemd[1]: Child 382 belongs to media-NEWDATA2.mount
[ 19.400340] systemd[1]: media-NEWDATA2.mount mount process exited, code=exited
status=1
[ 19.401392] systemd[1]: media-NEWDATA2.mount changed mounting -> failed
3.
What is this watchdog?
[ 54.033972] systemd[1]: Shutting down.
[ 54.050617] systemd[1]: Hardware watchdog 'iTCO_wdt', version 0
[ 54.052299] systemd[1]: Set hardware watchdog to 10min.
[ 54.054024] watchdog watchdog0: watchdog did not stop!
Chris Murphy