-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Today I tried this out, making a /boot/ partition on the harddisk and changing /etc/fstab
accordingly. It is workable while the card remains in the expresscard-cardreader, but not
workable, when it is inserted in the internal mmcblk-cardreader.
Running update-grub on the stable system on the harddisk is not sufficient to make things
work:
> andrew@jessie:~$ ls -la /dev/disk/by-uuid/
> total 0
> drwxr-xr-x 2 root root 140 Feb 25 11:38 .
> drwxr-xr-x 5 root root 100 Feb 25 11:33 ..
> lrwxrwxrwx 1 root root 10 Feb 25 11:33 0dde64dc-8274-4266-a810-f9aee59153e8
> -> ../../sdb5 lrwxrwxrwx 1 root root 10 Feb 25 11:38
> 200716dc-4394-44af-94d4-304c05e4d84b -> ../../sda5 lrwxrwxrwx 1 root root 10 Feb 25
> 11:38 51909eab-ae25-46af-841d-62fbbd1dd7a2 -> ../../sda3 lrwxrwxrwx 1 root root 10 Feb
> 25 11:33 5e1b75fa-a3cc-4d0a-a535-6ef327488c44 -> ../../sdb1 lrwxrwxrwx 1 root root 10
> Feb 25 11:38 c650ce84-00cc-45e6-86bb-c792e524028c -> ../../sda1 andrew@jessie:~$ sudo
> gedit /etc/fstab
>
> (gedit:1942): Gtk-WARNING **: Calling Inhibit failed:
> GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
> org.gnome.SessionManager was not provided by any .service files
>
> (gedit:1942): Gtk-WARNING **: Calling Inhibit failed:
> GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
> org.gnome.SessionManager was not provided by any .service files
>
> (gedit:1942): Gtk-WARNING **: Calling Inhibit failed:
> GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
> org.gnome.SessionManager was not provided by any .service files
>
> ** (gedit:1942): WARNING **: Set document metadata failed: Setting attribute
> metadata::gedit-spell-language not supported
>
> ** (gedit:1942): WARNING **: Set document metadata failed: Setting attribute
> metadata::gedit-encoding not supported andrew@jessie:~$ sudo mount /dev/sda3/ /boot/
> mount: special device /dev/sda3/ does not exist (a path prefix is not a directory)
> andrew@jessie:~$ sudo mount /dev/sda3 /boot/
> andrew@jessie:~$ sudo update-grub
> Generating grub configuration file ...
> Found background image: /usr/share/images/desktop-base/desktop-grub.png
> Found linux image: /boot/vmlinuz-3.16.0-4-686-pae
> Found initrd image: /boot/initrd.img-3.16.0-4-686-pae
> Found linux image: /boot/vmlinuz-3.16-3-686-pae
> Found initrd image: /boot/initrd.img-3.16-3-686-pae
> Found Debian GNU/Linux (7.8) on /dev/sda1
> done
>
fstab looks like this:
> # /etc/fstab: static file system information.
> #
> # Use 'blkid' to print the universally unique identifier for a
> # device; this may be used with UUID= as a more robust way to name devices
> # that works even if disks are added and removed. See fstab(5).
> #
> # <file system> <mount point> <type> <options> <dump> <pass>
> # / was on /dev/sdc1 during installation
> UUID=5e1b75fa-a3cc-4d0a-a535-6ef327488c44 / xfs noatime
> 0 1 #separate /boot/ on /dev/sda3:
> UUID=51909eab-ae25-46af-841d-62fbbd1dd7a2 /boot/ xfs
> noatime 0 0 # swap was on /dev/sdc5 during installation
> UUID=0dde64dc-8274-4266-a810-f9aee59153e8 none swap sw
> 0 0 /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
> /dev/sda1 /media/usb0 auto rw,user,noauto 0 0
> /dev/sdc1 /media/usb1 auto rw,user,noauto 0 0
> /dev/sdc2 /media/usb2 auto rw,user,noauto 0 0
> /dev/sdc5 /media/usb3 auto rw,user,noauto 0 0
Result: [see screenshots 'grub-menu.JPG' and 'grub-error.JPG']
There is this recipe for Arch-Linux:
https://bbs.archlinux.org/viewtopic.php?id=97207
but I don't think, I need that stuff about manually changing the initrd, because I am
using stock-kernels and generic initrds with all drivers included.
Maybe it is only a matter of chrooting prior to doing update-grub, possible something
like this does the trick:
> 3) Setup a working grub.cfg
> Since it is recommended to not edit grub.cfg directly in Grub2 I just added the
> following entry to /etc/grub.d/40_custom
>
> menuentry "Arch (on /dev/mmcblk0p1) custom" {
> set root='(hd0,5)'
> linux /boot/vmlinuz26-custom root=/dev/mmcblk0p1
> initrd /boot/kernel26-custom.img
> }
It should work anyway, when installing newly. I remember, I had similar problems, when
trying to move an exiting system onto an md-raid, most probably I am not familiar enough
with grub2 yet.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iEYEARECAAYFAlTt420ACgkQ5+rBHyUt5wvJnACdEumqQvma8wvGlmc9ETMvF3zo
JOMAnR6i8lAylxOIQSDgdOjXh92w6oWQ
=1p16
-----END PGP SIGNATURE-----
Attachment:
grub-error.JPG
Description: JPEG image
Attachment:
grub-menu.JPG
Description: JPEG image
