[I'm on the list, so there's no reason to reply off-list unless it's
something more personal or that nobody would be likely to want to
read... :-)]
Dan Ritter grabbed a keyboard and wrote:
> On Fri, Aug 30, 2013 at 10:15:48AM -0700, David Guntner wrote:
>> I'm guessing that there's a config file entry somewhere that grub is
>> using, which probably got auto-set up for that drive back when I first
>> installed Debian from scratch on an empty /dev/sda1 drive, and when the
>> installer probed the system, it saw the then-bootable partition sitting
>> on /dev/sdb1.
>>
>> So my question is, after all that, :-) is where exactly is that
>> information stored so that I can get rid of the extraneous extra
>> no-longer-bootable drive? I know it doesn't hurt anything... well, as
>> long as I don't try to boot off of it. lol But I don't like clutter in
>> the boot menu so I'd prefer to get rid of it if I can.
>
> /boot/grub/grub.cfg
>
> (or menu.lst for very old grub configs)
Ok, I've looked there. I found the following entries which look like
those are them:
> ### BEGIN /etc/grub.d/30_os-prober ###
> menuentry "Debian GNU/Linux, with Linux 3.2.0-4-amd64 (on /dev/sdb1)" --class gnu-linux --class gnu --class os {
> insmod part_msdos
> insmod ext2
> set root='(hd0,msdos1)'
> search --no-floppy --fs-uuid --set=root 6129819e-bf92-4786-a54d-a9d63f68e126
> linux /vmlinuz-3.2.0-4-amd64 root=UUID=36f6b922-0e9a-4ce5-aeee-c92104fa2428 ro quiet
> initrd /initrd.img-3.2.0-4-amd64
> }
> menuentry "Debian GNU/Linux, with Linux 3.2.0-4-amd64 (recovery mode) (on /dev/sdb1)" --class gnu-linux --class gnu --class os {
> insmod part_msdos
> insmod ext2
> set root='(hd0,msdos1)'
> search --no-floppy --fs-uuid --set=root 6129819e-bf92-4786-a54d-a9d63f68e126
> linux /vmlinuz-3.2.0-4-amd64 root=UUID=36f6b922-0e9a-4ce5-aeee-c92104fa2428 ro single
> initrd /initrd.img-3.2.0-4-amd64
> }
> ### END /etc/grub.d/30_os-prober ###
I'm a little concerned by the "os-prober" mention there. Does that mean
that something still thinks there's a bootable OS on /dev/sdb1? If so,
how exactly do I convince it otherwise. I've checked the partition and
it's not marked as "active" or "boot"....
Not only that, but given the comments around all the sections that point
at /etc/grub.d/{whatever}, does this mean that /boot/grub/grub.cfg is
being built by something, from those other files? If so, it seems that
directly editing /boot/grub/grub.cfg might not be such a good idea....
--Dave
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature