![]() No errors found in the Boot Parameter Block.īoot files: /boot/grub/grub.cfg /efi/BOOT/grub圆4.efi ![]() SYSLINUX is installed in the /uuiĭirectory. Sdc1: _ _īoot sector info: Syslinux looks at sector 60998 of /dev/sdc1 for its => Grub2 (v1.99) is installed in the MBR of /dev/sdc and looks at sector 1 of => No boot loader is installed in the MBR of /dev/sdb. => Grub2 (v1.99) is installed in the MBR of /dev/sda and looks at sectorġ3368 of the same hard drive for core.img, but core.img can not be found Hi, I am trying to change the boot from my USB to SDD. ![]() Does anybody know how best to fix this? I have not yet tried any advanced options in fear of not being able to boot into Ubuntu too! Ubuntu 14.04 boots fine, but I still have the same issue with Windows 8. I tried the recommended repair as this worked with my 12.10 installation, but this time around I get a warning about an error occuring during the repair and the following url: Sudo apt-get install -y boot-repair & boot-repair Sudo sh -c "sed -i 's/trusty/saucy/g' /etc/apt//yannubuntu-boot-repair-trusty.list" Sudo add-apt-repository ppa:yannubuntu/boot-repair I've tried booting from my Ubuntu 14.04 DVD and using the following commands, installing and running Boot Repair: For my installation today, Ubuntu appears to be working fine, but when I select Windows 8 from the grub menu, the grub menu blinks and re-appears. I previously duel booted Windows 8 and Ubuntu 12.10, and had to use Boot-Repair to get things working. I have installed Ubuntu 14.04 from a DVD. #if errors: -y auto answers yes for fixes needing response, also see man e2fsck p trys fixes where response not required #e2fsck is used to check the ext2/ext3/ext4 family of file systems. #From liveDVD/Flash so everything is unmounted,swap off if necessary, change example shown with partition sdb1 to your partition(s) Was /home encrypted? That would explain that & swap not showing, but then only way to recover is from last backup. I might see what test disk shows even deeper search just to see if partition table was somehow messed up.Īnd/or you can try running fsck on the ext4 partitions. Unless not a normal install the first partition starts at sector 2048. Partitions do not start at normal location. It can run lots of tests on a drive, but all I really know is passed is good and anything else is a new drive. What does Disks or Disk utility say under Smart Status. Often a bad shutdown or powerfailure may corrupt on other another but not all. I'm now making a bootable Gparted usb stick and i'll see if that can help, although i have a feeling the drive is corrupted or dead.It is strange that all the partitions will not mount. I tried Paragon Partition and that wouldn't open either. I tried another version of it and that wouldn't open. I tried to use EaseUS to look at the partitions but it won't open. Even Disk Management won't open with them in the system, it just sits on "connecting to virtual disk service", plus windows doesn't feel right either - it takes much longer to boot up and installing software takes ages too. I then booted back into AHCI mode and both drives were there, but again the HDD wasn't accessible. However, the 2 partitions on the HDD had no sizes assigned, and if i tried to open one it crashed the system. I found the latest raid drivers on the AMD page and installed them and both the SSD and HDD appeared in this computer. The HDD still wouldn't boot in AHCI so i booted back into Raid mode and noticed in Device Manager that there were 2 items flagged under Storage as Raid Controllers. Not ideal but not the end of the world, and it now works fine. I took out the HDD and tried working on the SSD and that booted in AHCI mode with no problems, but needed to be initialised in Disk Management which required a full format.
0 Comments
Leave a Reply. |