dannyboyinpy
May 14th, 2016, 03:22 AM
This seems similar to my problem, but I tried the nomodeset tweak and it didn't seem to work. You can see the details of my situation on my askUbuntu post (no answers) here http://askubuntu.com/questions/771514/cant-start-up-after-updating-to-16-04 . With nomodeset the output at the alt-f7 screen reads
fsck from util-linux 2.26.2
/dev/sda1: recovering journal
/dev/sda1: clearing orphaned inode 524295 (uuid=122, gid=131, mode=0100600, size =0)
/dev/sda1: clearing orphaned inode 524293 (uuid=122, gid=131, mode=0100600, size =0)
/dev/sda1: clearing orphaned inode 524291 (uuid=122, gid=131, mode=0100600, size =0)
/dev/sda1: clearing orphaned inode 524290 (uuid=122, gid=131, mode=0100600, size =0
/dev/sda1: clean, 569967/9519104 files, 10823249/38047232 blocks
I really don't know if this output is important or useful, but thought it couldn't hurt to give all the information I can. I really appreciate any help I can get as I need this computer for a school project due soon.
fsck from util-linux 2.26.2
/dev/sda1: recovering journal
/dev/sda1: clearing orphaned inode 524295 (uuid=122, gid=131, mode=0100600, size =0)
/dev/sda1: clearing orphaned inode 524293 (uuid=122, gid=131, mode=0100600, size =0)
/dev/sda1: clearing orphaned inode 524291 (uuid=122, gid=131, mode=0100600, size =0)
/dev/sda1: clearing orphaned inode 524290 (uuid=122, gid=131, mode=0100600, size =0
/dev/sda1: clean, 569967/9519104 files, 10823249/38047232 blocks
I really don't know if this output is important or useful, but thought it couldn't hurt to give all the information I can. I really appreciate any help I can get as I need this computer for a school project due soon.