GRUB BOOT PROBLEM, HELP! Boot Info Script in post!
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Well everyone I apprieciate your responses and help , thanks. I had actually responed myself yesterday giving more info on this and for some reason i am not exactly sure but obviously I forgot to actually press the "submit reply" button. So that entire message i wrote never posted ....Doh!, Homer said! So anyways I am gonna try this again .
Ok , before all this happened I had Linux Mint 17 KDE running/installed to an 80GB Hard Drive, (which was on sda1)and as the Boot info script shows , I have 2 other hard drives and they are both identical in size and and all ...36GB or something and those I just used as extra memory and stored backup files on and some Android Rom developmnet stuff I mess with ...u get the picture . So, I have no clue what happened but came turned the computer on and instead of booting I just get the grub>screen . So I have tried using the Boot--Repair live dvd as Arcane mentioned to no avail. I tried using a bootable partition manager by minitool, that didnt work either . I also followed Vincix recommendations....
Code:
mint mint # sudo fdisk -l
Disk /dev/sda: 31.0 GB, 31009800192 bytes
64 heads, 32 sectors/track, 29573 cylinders, total 60566016 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x3c49d92f
Device Boot Start End Blocks Id System
/dev/sda1 * 0 2758655 1379328 17 Hidden HPFS/NTFS
Disk /dev/sda1: 1412 MB, 1412431872 bytes
64 heads, 32 sectors/track, 1347 cylinders, total 2758656 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x3c49d92f
Device Boot Start End Blocks Id System
/dev/sda1p1 * 0 2758655 1379328 17 Hidden HPFS/NTFS
Disk /dev/sdb: 36.4 GB, 36401479680 bytes
255 heads, 63 sectors/track, 4425 cylinders, total 71096640 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xe264e264
Device Boot Start End Blocks Id System
/dev/sdb1 * 2048 71096319 35547136 83 Linux
Disk /dev/sdc: 36.4 GB, 36401479680 bytes
255 heads, 63 sectors/track, 4425 cylinders, total 71096640 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00012a59
Device Boot Start End Blocks Id System
/dev/sdc1 * 2048 71096319 35547136 83 Linux
mint mint # sudo mount /dev/sda1 /mnt
mount: block device /dev/sda1 is write-protected, mounting read-only
mint mint #
So there is the output of some of that. I also just FYI ---I dont know what happend like i said but before this happend when I would open the file manager and browse , the "main" hard drive that I had Linux installed on was always identified in the file manager as sda1. Then when this happend , i look in the file manager and it now it says "LOOP DEVICE"?? What would make it change to that? And in the boot info script , it says that this disk is 100% full....but before it was doing this total space was 80GB and I am 100% sure that I still had like 35gb of free space left on that disk/drive . And now when i run "sudo fdisk -l" it says
/dev/sda1 * 0 2758655 1379328 17 Hidden HPFS/NTFS
Now this is the first time I have seen this and i have ran that same command before and it would only list /dev/loop0 and would have no ther information on it.???
Ok one last thing I can actually browse that drive and look at the files while i am on the live dvd and when I am viewing all the folders like bin,boot;dev and so on...i can scroll to the bottom and find the two "links" one called "VMLINUZ" and the other called "INITRD.IMG. When I look at those properties it says that they are both "Broken" and the "Link to "" is not valid as the '' does not exist"????? I know those are the Kernel but thats about as much as I know . I hope all this info will help and apologize if i ramble , just trying to provide as much info as possible. Thanks again and if anything else u need me to provide just say it .
{...}So I have tried using the Boot--Repair live dvd as Arcane mentioned to no avail.{...}
And where did i suggest that nonsense? I suggested you something else but you missed my point. I was trying to tell you to boot into live mode of Mint and then using terminal install boot-repair and then run it to fix problem with MBR.
And where did i suggest that nonsense? I suggested you something else but you missed my point. I was trying to tell you to boot into live mode of Mint and then using terminal install boot-repair and then run it to fix problem with MBR.
Yeah , sorry about that I was confused obviously. I will try that option now that I understand what u meant , thanks.If i have any luck I will post.
He's using Mint. That means that he has update-grub. So instead of going through all that, couldn't he simply run update-grub from a live medium? Seems a lot easier than other things suggested in this thread.
Well when I run and try to mkdir and mount it says READONLY fs? I need to know how I can change that "read only" filesystem to read-write I suppose . thanks for the help everyone.
Well when I run and try to mkdir and mount it says READONLY fs? I need to know how I can change that "read only" filesystem to read-write I suppose . thanks for the help everyone.
Something is mounting it as read only. If you unmount it and remount it do you have the same issue?
Well when I run and try to mkdir and mount it says READONLY fs? I need to know how I can change that "read only" filesystem to read-write I suppose . thanks for the help everyone.
You need to remount: mount -ov remount,rw /mount/point
I forgot about this command, which is essential. So when you end up in that point, do that and then you can change whatever you want to.
[OFF-TOPIC]
Loop usually means mounting a file which contains a filesystem, so not a regular filesystem/partition. For instance, you can create a file partition with dd by directing it to a certain file, then you make a partition out of that file with mkfs and then you can mount it with mount -o loop.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
