Chris Bannister grabbed a keyboard and wrote:
> On Fri, Aug 30, 2013 at 07:58:39PM -0700, David Guntner wrote:
>>
>>> # dd if=/dev/zero of=/dev/sdb1 bs=512 count=1
>>> 1+0 records in
>>> 1+0 records out
>>> 512 bytes (512 B) copied, 0.000983331 s, 521 kB/s
>>> # update-grub
>>> Generating grub.cfg ...
>>> Found background image: /usr/share/images/desktop-base/desktop-grub.png
>>> Found linux image: /boot/vmlinuz-3.2.0-4-amd64
>>> Found initrd image: /boot/initrd.img-3.2.0-4-amd64
>>> Found memtest86+ image: /memtest86+.bin
>>> Found memtest86+ multiboot image: /memtest86+_multiboot.bin
>>> Found Debian GNU/Linux (6.0.7) on /dev/sdb1
>>> done
>
> Are there any clues in any of the files under:
> root@tal:~# ls -al /etc/grub.d/
>
> Maybe one of those still has the info about it and update-grub is just
> blindly going through the motions?
> # pwd
> /etc/grub.d
> # hunt sdb
> # declare -f hunt
> hunt ()
> {
> find . -type f -print0 | xargs -0 egrep -i $* | more
> }
Nope. "hunt" searched for sdb in every file in that directory and came
up blank.
I'm really starting to think it's just something that got stuck in the
partition table. Now that I think about it, I think when I re-purposed
that drive, I deleted all partitions except for sdb1 and then just
resized it to fill the whole drive. I'm going to move the contents off,
delete the partition outright and recreate it (gparted) and reformat,
etc. We'll see what happens then....
--Dave
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature