LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This 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


Reply
  Search this Thread
Old 01-01-2015, 05:48 PM   #1
LeoDroid30
LQ Newbie
 
Registered: Jan 2015
Posts: 6

Rep: Reputation: Disabled
GRUB BOOT PROBLEM, HELP! Boot Info Script in post!


Hello, I am fairly new with linux and such and the computer (desktop) I have was running Linux Mint 17 KDE. I have no idea as to what happened or why it happened but after turning the computer off overnight, then turning it on this morning it boots but ends up at the Grub> screen. I did alittle research on grub and all that and found Boot Info Script and followed the directions to get it and now I have no idea really what to do with the info , so i was hoping to post it here and see if i could get some help or interpretation , lol.
Code:
 Boot Info Script e7fc706 + Boot-Repair extra info      [Boot-Info 31Jan2013]


============================= Boot Info Summary: ===============================

 => Grub2 (v1.99) is installed in the MBR of /dev/sda and looks at sector 1 of 
    the same hard drive for core.img. core.img is at this location and looks 
    in partition 112 for .
 => Grub Legacy (v0.97) is installed in the MBR of /dev/sdb and looks on boot 
    drive #1 in partition #1 for /boot/grub/stage2 and /boot/grub/menu.lst.

sda1: __________________________________________________________________________

    File system:       ext4
    Boot sector type:  -
    Boot sector info: 
    Operating System:  
    Boot files:        /boot/grub/i386-pc/core.img

sdb1: __________________________________________________________________________

    File system:       ext4
    Boot sector type:  -
    Boot sector info: 
    Operating System:  
    Boot files:        

============================ Drive/Partition Info: =============================

Drive: sda _____________________________________________________________________

Disk /dev/sda: 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

Partition  Boot  Start Sector    End Sector  # of Sectors  Id System

/dev/sda1    *          2,048    71,096,319    71,094,272  83 Linux


Drive: sdb _____________________________________________________________________

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

Partition  Boot  Start Sector    End Sector  # of Sectors  Id System

/dev/sdb1    *          2,048    71,096,319    71,094,272  83 Linux


"blkid" output: ________________________________________________________________

Device           UUID                                   TYPE       LABEL

/dev/loop0                                              squashfs   
/dev/sda1        255c095f-9661-4d7b-824c-d205ec0c785c   ext4       Hard Disk 2-36gb
/dev/sdb1        6318eedc-cc84-4380-ae5c-98d441086074   ext4       Memory Bank
/dev/sr0                                                iso9660    Boot-Repair-Disk 32bit

================================ Mount points: =================================

Device           Mount_Point              Type       Options

/dev/loop0       /rofs                    squashfs   (ro,noatime)
/dev/sr0         /cdrom                   iso9660    (ro,noatime)


=================== sda1: Location of files loaded by Grub: ====================

           GiB - GB             File                                 Fragment(s)

  22.224693298 = 23.863582720   boot/grub/i386-pc/core.img                     1

=============================== StdErr Messages: ===============================

cat: write error: Broken pipe
File descriptor 8 (/proc/2627/mounts) leaked on lvscan invocation. Parent PID 8282: bash
  No volume groups found

ADDITIONAL INFORMATION :
=================== log of boot-repair 2015-01-01__21h12 ===================
boot-repair version : 3.198~ppa16~raring
boot-sav version : 3.198~ppa16~raring
glade2script version : 3.2.2~ppa45~raring
boot-sav-extra version : 3.198~ppa16~raring
File descriptor 8 (/proc/2627/mounts) leaked on lvs invocation. Parent PID 4201: /bin/sh
No volume groups found
boot-repair is executed in live-session (Boot-Repair-Disk 32bit 24avr2013, raring, Ubuntu, i686)
ls: cannot access /home/usr/.config: No such file or directory
file=/cdrom/preseed/lubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --

=================== os-prober:


=================== blkid:
/dev/loop0: TYPE="squashfs"
/dev/sr0: LABEL="Boot-Repair-Disk 32bit" TYPE="iso9660"
/dev/sda1: LABEL="Hard Disk 2-36gb" UUID="255c095f-9661-4d7b-824c-d205ec0c785c" TYPE="ext4"
/dev/sdb1: LABEL="Memory Bank" UUID="6318eedc-cc84-4380-ae5c-98d441086074" TYPE="ext4"

=================== No kernel in /mnt/boot-sav/sda1/boot:
grub


=================== UEFI/Legacy mode:
This live-session is not EFI-compatible.
SecureBoot maybe enabled.


=================== PARTITIONS & DISKS:
sda1	: sda,	maybesepboot,	no-grubenv	nogrub,	no-docgrub,	no-update-grub,	32,	no-kernel,	no-os,	not--efi--part,	part-has-no-fstab,	part-has-no-fstab,	no-nt,	no-winload,	no-recov-nor-hid,	no-bmgr,	notwinboot,	nopakmgr,	nogrubinstall,	no---usr,	part-has-no-fstab,	not-sep-usr,	standard,	not-far,	/mnt/boot-sav/sda1.
sdb1	: sdb,	maybesepboot,	no-grubenv	nogrub,	no-docgrub,	no-update-grub,	32,	no-boot,	no-os,	not--efi--part,	part-has-no-fstab,	part-has-no-fstab,	no-nt,	no-winload,	no-recov-nor-hid,	no-bmgr,	notwinboot,	nopakmgr,	nogrubinstall,	no---usr,	part-has-no-fstab,	not-sep-usr,	standard,	not-far,	/mnt/boot-sav/sdb1.

sda	: not-GPT,	BIOSboot-not-needed,	has-no-EFIpart, 	not-usb,	no-os,	2048 sectors * 512 bytes
sdb	: not-GPT,	BIOSboot-not-needed,	has-no-EFIpart, 	not-usb,	no-os,	2048 sectors * 512 bytes


=================== parted -l:

Model: IBM-ESXS MAP3367NP FN (scsi)
Disk /dev/sda: 36.4GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End     Size    Type     File system  Flags
1      1049kB  36.4GB  36.4GB  primary  ext4         boot


Model: IBM-ESXS MAP3367NP FN (scsi)
Disk /dev/sdb: 36.4GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End     Size    Type     File system  Flags
1      1049kB  36.4GB  36.4GB  primary  ext4         boot



                                                                          
Warning: Unable to open /dev/sr0 read-write (Read-only file system).  /dev/sr0
has been opened read-only.

                                                                          
Error: /dev/sr0: unrecognised disk label

=================== parted -lm:

BYT;
/dev/sda:36.4GB:scsi:512:512:msdos:IBM-ESXS MAP3367NP FN;
1:1049kB:36.4GB:36.4GB:ext4::boot;

BYT;
/dev/sdb:36.4GB:scsi:512:512:msdos:IBM-ESXS MAP3367NP FN;
1:1049kB:36.4GB:36.4GB:ext4::boot;


                                                                          
Warning: Unable to open /dev/sr0 read-write (Read-only file system).  /dev/sr0
has been opened read-only.

                                                                          
Error: /dev/sr0: unrecognised disk label


=================== mount:
/cow on / type overlayfs (rw)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
/dev/sr0 on /cdrom type iso9660 (ro,noatime)
/dev/loop0 on /rofs type squashfs (ro,noatime)
none on /sys/fs/cgroup type tmpfs (rw)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755)
gvfsd-fuse on /run/user/lubuntu/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,user=lubuntu)
/dev/sda1 on /mnt/boot-sav/sda1 type ext4 (rw)
/dev/sdb1 on /mnt/boot-sav/sdb1 type ext4 (rw)


=================== ls:
/sys/block/fd0 (filtered):  alignment_offset bdi capability dev device discard_alignment events events_async events_poll_msecs ext_range holders inflight power queue range removable ro size slaves stat subsystem trace uevent
/sys/block/sda (filtered):  alignment_offset bdi capability dev device discard_alignment events events_async events_poll_msecs ext_range holders inflight power queue range removable ro sda1 size slaves stat subsystem trace uevent
/sys/block/sdb (filtered):  alignment_offset bdi capability dev device discard_alignment events events_async events_poll_msecs ext_range holders inflight power queue range removable ro sdb1 size slaves stat subsystem trace uevent
/sys/block/sr0 (filtered):  alignment_offset bdi capability dev device discard_alignment events events_async events_poll_msecs ext_range holders inflight power queue range removable ro size slaves stat subsystem trace uevent
/sys/block/sr1 (filtered):  alignment_offset bdi capability dev device discard_alignment events events_async events_poll_msecs ext_range holders inflight power queue range removable ro size slaves stat subsystem trace uevent
/dev (filtered):  agpgart alarm ashmem autofs binder block bsg btrfs-control bus cdrom cdrom1 cdrw cdrw1 char console core cpu cpu_dma_latency disk dri dvd dvd1 dvdrw1 ecryptfs fb0 fd fd0 full fuse fw0 hidraw0 hpet input kmsg log mapper mcelog mem net network_latency network_throughput null oldmem parport0 port ppp psaux ptmx pts random rfkill rtc rtc0 sda sda1 sdb sdb1 sg0 sg1 sg2 sg3 shm snapshot snd sr0 sr1 stderr stdin stdout uinput urandom vga_arbiter vhost-net zero
ls /dev/mapper:  control

=================== df -Th:

Filesystem     Type       Size  Used Avail Use% Mounted on
/cow           overlayfs 1009M   21M  989M   2% /
udev           devtmpfs   993M   12K  993M   1% /dev
tmpfs          tmpfs      202M  724K  201M   1% /run
/dev/sr0       iso9660    496M  496M     0 100% /cdrom
/dev/loop0     squashfs   431M  431M     0 100% /rofs
none           tmpfs      4.0K     0  4.0K   0% /sys/fs/cgroup
tmpfs          tmpfs     1009M  8.0K 1009M   1% /tmp
none           tmpfs      5.0M     0  5.0M   0% /run/lock
none           tmpfs     1009M     0 1009M   0% /run/shm
none           tmpfs      100M   12K  100M   1% /run/user
/dev/sda1      ext4        34G   33G     0 100% /mnt/boot-sav/sda1
/dev/sdb1      ext4        34G  4.7G   27G  15% /mnt/boot-sav/sdb1

=================== fdisk -l:

Disk /dev/sda: 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/sda1   *        2048    71096319    35547136   83  Linux

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: 0x00012a59

Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *        2048    71096319    35547136   83  Linux


No OS has been found on this computer.

=================== Recommended repair
Recommended-Repair
This setting will not act on the MBR.



No change has been performed on your computer.
 
Old 01-01-2015, 06:16 PM   #2
vincix
Member
 
Registered: Feb 2011
Distribution: Centos 6.7, 7
Posts: 514

Rep: Reputation: 48
If you've installed your linux mint from a CD, you can boot that as a liveCD (when the menu shows up, choose "start Linux Mint" or something like that).

After you've done that, open a terminal, identify your linux partition ($ sudo fdisk -l).

Mount it: $ sudo mount /dev/sdXY /mnt (change X and Y with your disk and partition id; e.g. /dev/sda1)

If there's no error displayed, then you can reinstall your grub (bootloader) (be careful not to take it for some other partition): # sudo grub-install --root-directory=/mnt /dev/sdX (for instance /dev/sda - without the final number, so that you install it on the whole hdd, including MBR, not on the partition - basically so it can boot)

Optionally, you can add # sudo update-grub for the MBR update.
Restart and that's it.

Last edited by vincix; 01-01-2015 at 06:26 PM.
 
Old 01-01-2015, 06:16 PM   #3
Head_on_a_Stick
Senior Member
 
Registered: Dec 2014
Location: London, England
Distribution: Arch & Debian
Posts: 1,183

Rep: Reputation: 283Reputation: 283Reputation: 283
Quote:
Originally Posted by LeoDroid30 View Post
Code:
No OS has been found on this computer.
That looks relevant.
 
Old 01-01-2015, 06:30 PM   #4
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida
Distribution: slackware64-current, puppy, ubuntu
Posts: 1,904

Rep: Reputation: 261Reputation: 261Reputation: 261
Quote:
/dev/sda1 ext4 34G 33G 0 100%
This could be the problem no free space on sda1
 
Old 01-01-2015, 06:33 PM   #5
vincix
Member
 
Registered: Feb 2011
Distribution: Centos 6.7, 7
Posts: 514

Rep: Reputation: 48
Quote:
Originally Posted by colorpurple21859 View Post
This could be the problem no free space on sda1
Can that really happen? An OS refusing to boot because it doesn't have enough disk space? Isn't it a bit of a weird behaviour?
 
Old 01-01-2015, 07:34 PM   #6
yancek
LQ Guru
 
Registered: Apr 2008
Distribution: PCLinux, Slackware
Posts: 6,871

Rep: Reputation: 1249Reputation: 1249Reputation: 1249Reputation: 1249Reputation: 1249Reputation: 1249Reputation: 1249Reputation: 1249Reputation: 1249
Quote:
Can that really happen? An OS refusing to boot because it doesn't have enough disk space? Isn't it a bit of a weird behaviour?
Yes it can and it does happen regularly. I've seen quite a number of posts with the non-boot problem the result of a full disk. Did it myself last week testing a backup script. Walked away from the computer and forgot about it for several hours and had a problem rebooting that particular system. I was able to boot and login as root user which can probably be done on many systems. Having a full disk and no OS are problems. Difficult to guess what happened here. Pretty small hard drives.
 
Old 01-01-2015, 08:50 PM   #7
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 14,839

Rep: Reputation: 1822Reputation: 1822Reputation: 1822Reputation: 1822Reputation: 1822Reputation: 1822Reputation: 1822Reputation: 1822Reputation: 1822Reputation: 1822Reputation: 1822
A full disk should still be bootabe (by root) if there are reserved blocks (the default) as @yancek notes.
Not finding an OS or grub config files says to me broken file system. The fact it was mounted rw by boot-repair means any outstanding journal entries would have been automatically re-run during mount. All of that is bad news (in this case).
I'd just restore in toto from most recent backup - or failing the existance of a good backup, re-install.

No idea of what could have caused it - certainly an unusual event.
 
Old 01-02-2015, 07:25 AM   #8
zafar_dandoti
Member
 
Registered: Dec 2005
Location: India
Distribution: centos
Posts: 169

Rep: Reputation: Disabled
=================== UEFI/Legacy mode:
This live-session is not EFI-compatible.
SecureBoot maybe enabled.

Turn off the secureboot in bios setup...
 
Old 01-02-2015, 06:27 PM   #9
vincix
Member
 
Registered: Feb 2011
Distribution: Centos 6.7, 7
Posts: 514

Rep: Reputation: 48
Quote:
Originally Posted by yancek View Post
Yes it can and it does happen regularly. I've seen quite a number of posts with the non-boot problem the result of a full disk. Did it myself last week testing a backup script. Walked away from the computer and forgot about it for several hours and had a problem rebooting that particular system. I was able to boot and login as root user which can probably be done on many systems.
But don't you see it as a big hole for linux-based systems? I mean, you'd probably never hear of such a thing in Windows or Mac OS, would you? You'd still be able to boot the system even if it's full and clear it up, right?

Last edited by vincix; 01-02-2015 at 06:29 PM.
 
Old 01-02-2015, 07:38 PM   #10
yancek
LQ Guru
 
Registered: Apr 2008
Distribution: PCLinux, Slackware
Posts: 6,871

Rep: Reputation: 1249Reputation: 1249Reputation: 1249Reputation: 1249Reputation: 1249Reputation: 1249Reputation: 1249Reputation: 1249Reputation: 1249
Quote:
But don't you see it as a big hole for linux-based systems? I mean, you'd probably never hear of such a thing in Windows or Mac OS, would you? You'd still be able to boot the system even if it's full and clear it up, right?
No. Did you not read the post? There is no problem booting it nor is there a problem deleting files, you just log in as root. Since most windows users don't bother with a separate administrative user, who knows. I don't use windows and have never used a Mac.
 
Old 01-03-2015, 03:32 AM   #11
vincix
Member
 
Registered: Feb 2011
Distribution: Centos 6.7, 7
Posts: 514

Rep: Reputation: 48
Quote:
Originally Posted by yancek View Post
No. Did you not read the post? There is no problem booting it nor is there a problem deleting files, you just log in as root. Since most windows users don't bother with a separate administrative user, who knows. I don't use windows and have never used a Mac.
Are you talking about your post or the main post?

By loging in with root do you mean single-mode? If that is the case, then I see it as a big problem if, for instance, you have a server to which you connect remotely and, just like you did, happen to "let" a software spam data until the disk is full. What do you do then? Do you need to intervene physically? That would be a big drawback.
 
Old 01-03-2015, 10:57 AM   #12
yancek
LQ Guru
 
Registered: Apr 2008
Distribution: PCLinux, Slackware
Posts: 6,871

Rep: Reputation: 1249Reputation: 1249Reputation: 1249Reputation: 1249Reputation: 1249Reputation: 1249Reputation: 1249Reputation: 1249Reputation: 1249
I was referring to my post and the situation I described which is different than that of the OP. He had only one partition while I have about a dozen. I also have about 10 Linux systems installed so if I am unable to boot one because of the partition being full or for any reason, I just boot another system.

I googled the full disk windows and got a number of posts so if a disk is full on windows or Linux it's the same problem. I don't use windows so don't know what one would do. The situation you describe on a remote server, I have no idea as I don't run remote servers and don't work in IT. The only thing I would say is that if someone is responsible for a remote server with someone else's data, they would need to be a lot more careful than a home computer user such as myself. Maybe someone else will respond with some useful info?
 
Old 01-04-2015, 02:23 PM   #13
Arcane
Member
 
Registered: May 2006
Location: Latvia, Europe
Distribution: random
Posts: 303

Rep: Reputation: 233Reputation: 233Reputation: 233
Quote:
Originally Posted by LeoDroid30 View Post
Hello, I am fairly new with linux and such and the computer (desktop) I have was running Linux Mint 17 KDE. I have no idea as to what happened or why it happened but after turning the computer off overnight, then turning it on this morning it boots but ends up at the Grub> screen. I did alittle research on grub and all that and found Boot Info Script and followed the directions to get it and now I have no idea really what to do with the info , so i was hoping to post it here and see if i could get some help or interpretation , lol.
If you are new then let's not complicate things. Mint is based on Ubuntu so next sentence will work. There exists simple tool Boot-Repair to fix common boot loader problems.
 
Old 01-04-2015, 02:47 PM   #14
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida
Distribution: slackware64-current, puppy, ubuntu
Posts: 1,904

Rep: Reputation: 261Reputation: 261Reputation: 261
If it was me I would use something like SystemRescueCD to see what is taking up all the drive space and see if my root files system is still intact.
 
Old 01-04-2015, 05:38 PM   #15
EDDY1
LQ Addict
 
Registered: Mar 2010
Location: Oakland,Ca
Distribution: wins7, Debian wheezy
Posts: 6,838

Rep: Reputation: 649Reputation: 649Reputation: 649Reputation: 649Reputation: 649Reputation: 649
2 drives both with /mnt/boot. sdb says memory, but how many OS were on the system?
Did you remove a drive?
Have you tried moving sdb to 1st boot device?
sdb has plenty of free space have you tried moving some of your large files, from Downloads or Documents to sdb?

Last edited by EDDY1; 01-04-2015 at 05:39 PM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Win 8.1 / Kubuntu 13.10 Dual Boot fault (with Boot-Info URL from Boot Repair) renzanel Linux - Laptop and Netbook 2 02-05-2014 02:23 PM
[SOLVED] Can't select XP OS in a dual boot with Isadora at boot screen (grub problem) faby1321 Linux Mint 10 08-10-2010 07:07 PM
boot info script question msc8127 Linux - Newbie 3 08-30-2009 12:10 AM
boot to GUI problem want grub boot to single user mode. hocheetiong Linux - Newbie 1 09-26-2007 07:41 PM
Can someone give me grub boot info? alphster Slackware 1 01-05-2005 12:38 PM


All times are GMT -5. The time now is 12:23 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration