Tag Info

New answers tagged

0

Well, It seems to be that there was a small typos in my fstab file. UID=00e0172b-f19c-470c-bbf7-5e5b135d52e1 /home ext4 defaults 0 2 I've changed UID to UUID and my computer booted normally again. Still, thanks for your helps.


0

The message says some errors were found on the filesystem which fsck will not fix automatically,since it may affect your data so you should do it manually. To do this, press M (when you be asked for) - this will drop you into a root console fsck /dev/sdXX Replace XX with your /home disk name partition If this doesn't work try the command sudo ...


0

Check your SSD using GSmartControl, it's also for Windows. When I suspected my own SSD of failing I also tried SSD Life, but I'm not sure if its results are entirely accurate.


0

I'm pretty sure my SSD crashed, as it doesn't even show up in BIOS. I tried the power reset procedure for SSDs but it did no good. Well, this is unfortunate.


0

Boot-Repair uses glade2script and therefore needs some gui. Not sure if just installing glade2script would work or not. Better to just use the Ubuntu Desktop and add Boot-Repair or download the Boot-RepairCD itself. It expects to see glade2script. Glade2script allows a script (Bash, Python or other) to display and interact with a GUI (created with ...


0

Grub menu will appear if you press and hold Shift during loading Grub. For permanent change you'll need to edit your /etc/default/grub file -- place a "#" symbol at the start of line GRUB_HIDDEN_TIMEOUT=0. Save changes and run sudo update-grub to apply changes. Documentation: https://help.ubuntu.com/community/Grub2


1

I figured it out! UEFI was enabled on my motherboard, I was using http://www.pendrivelinux.com/, which apparently didn’t boot me as UEFI. Using Rufus worked, then i had to use recommended boot repair, and afterwards use windows boot repair to get windows working as well!


1

You have to go into the bios to enable uefi. Hit delete or f12 or something to get into the bios. From there you'll need to find the setting to enable UEFI.


1

I solved that problem with reruninng boot-repair and after that running sudo update-grub


0

You seem to be in a very tight spot with very little help... As you haven't given much data on what exactly is wrong with your system (no logs or anything) I can only conclude, based on the data you provided that I would: Boot from a LiveDVD Back up all of my data and config files without password (the last one are mine: Your mileage may vary) Wipe EXT4 ...


0

1> use win7 disk 2> start up repair 3> chkdsk >>>> restart after restart win boot louder start but GRUB not. to fix that USE "BOOT-repair" disk and "fsck.msdos" commands. both answers are very helpful together.


0

The suggested actions at the bottom of the Boot-Repair script actually look like the right thing to do here, but you said it got stuck, so we'll need to look for a manual solution. The Grub boot loader appears to be alive and well, but the boot menu has no entries, so you'll need to follow the instructions of this answer to repopulate it. Check the output ...


0

Did you try its suggestion and use sudo apt-get install -f boot-repair also try sudo apt-get autoremove sudo apt-get dist-upgrade sudo apt-get upgrade sudo apt-get update sudo ap-get install libgl1-mesa-dri-lts-utopic:i386 Then try to re-install



Top 50 recent answers are included