You will need to mark one of your partitions as bootable, the one that
contains the initrd image.  If mint mounts a separate /boot partition, then
mark that partition as bootable with fdisk.  If everything is on a single
partition on a single disk, then "sudo fdisk /dev/sda", you should see
something similar to this:

Command (m for help):

If you use the "p" key you should see a list of partitions, below is what
one of my machines looks like"

Disk /dev/sdh: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders, total 234441648 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: 0x00059f35

   Device Boot      Start         End      Blocks   Id  System
/dev/sdh1   *        2048   222062591   111030272   83  Linux
/dev/sdh2       222064638   234440703     6188033    5  Extended
/dev/sdh5       222064640   234440703     6188032   82  Linux swap / Solaris

The first partition contains my /boot (well everything since this machine
has everything under /) and is marked as bootable (denoted by the asterisk
in the boot column).  Toggle the bootable flag with the "a" key.

Press "w" to write out the changes and quit.  Then run "sudo update-grub"
to reinstall grub, initrd and the kernel.

Hth,

On Tue, Jun 2, 2015 at 3:43 PM, caziz <[email protected]> wrote:

> Mint 17.1 apparently pranged a couple of weeks ago.
> Didn't find out until I rebooted a couple weeks later.
> Had to use Live DVD and  pull old Feb 12 initrd.img-3.13.0-37-generic
> and named it initrd.img-3.13.0-37-0generic.20150517SAFE  to reboot.
>
> The initramfs-tools error persists but can install other packages OK.
>
> What is/was  my malfunction?
>
> Thanks,
> Chris
>
>
> root apr01 # apt-get install initramfs-tools --reinstall
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 52 not
> upgraded.
> 1 not fully installed or removed.
> After this operation, 0 B of additional disk space will be used.
> E: Internal Error, No file name for initramfs-tools:amd64
>
>
> root apr01 # apt-get install mintupdate
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> The following packages will be upgraded:
>   mintupdate
> 1 upgraded, 0 newly installed, 0 to remove and 51 not upgraded.
> 1 not fully installed or removed.
> Need to get 114 kB of archives.
> After this operation, 188 kB disk space will be freed.
> Get:1 http://packages.linuxmint.com/ rebecca/main mintupdate all 4.8.4
> [114 kB]
> Fetched 114 kB in 0s (279 kB/s)
> (Reading database ... 186340 files and directories currently installed.)
> Preparing to unpack .../mintupdate_4.8.4_all.deb ...
> Unpacking mintupdate (4.8.4) over (4.8.1) ...
> Processing triggers for mime-support (3.54ubuntu1.1) ...
> Processing triggers for gnome-menus (3.10.1-0ubuntu2) ...
> Processing triggers for desktop-file-utils (0.22-1ubuntu1) ...
> Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ...
> Rebuilding /usr/share/applications/bamf-2.index...
> Setting up initramfs-tools (0.103ubuntu4.2) ...
> update-initramfs: deferring update (trigger activated)
> Setting up mintupdate (4.8.4) ...
> Processing triggers for initramfs-tools (0.103ubuntu4.2) ...
> update-initramfs: Generating /boot/initrd.img-3.13.0-37-generic
> E: No boot partition found !
> run-parts: /etc/initramfs/post-update.d//zz-flash-touch-initrd exited with
> return code 1
> dpkg: error processing package initramfs-tools (--configure):
>  subprocess installed post-installation script returned error exit status 1
> Processing triggers for initramfs-tools-ubuntu-touch (0.72) ...
> Errors were encountered while processing:
>  initramfs-tools
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
>
> _______________________________________________
> clug-talk mailing list
> [email protected]
> http://clug.ca/mailman/listinfo/clug-talk_clug.ca
> Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
> **Please remove these lines when replying
>
_______________________________________________
clug-talk mailing list
[email protected]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying

Reply via email to