Siduction Forum
Siduction Forum => Upgrade Warnings => Topic started by: agaida on 2013/01/28, 01:22:33
-
Its not a warning, only a hint. We have synced grub2 from experimental to fixes. If you have experimental in your sources list it is very likely that the packages will be pulled from experimental, not from $mirror/fixes. This is intentional, please dont worry about it, the packages are identical :twisted:
If you have no experimental activated in your source.list.d, the packages will be pulled from $mirror/fixes.
------
Wenn ihr einen d-u macht und auf einmal Grub-Pakete aus experimental gezogen werden, keine Sorge. Wir haben grub-$foo nach fixes gespielt, bei aktiviertem experimental zieht apt die Pakete wahrscheinlich von experimental. Keine Sorge, es sind die selben, die ihr auch aus fixes bekommen würdet. Falls ihr experimental nicht aktiviert habt, dann werden die Pakete aus $mirror/fixes gezogen.
-
Hehe, thanks for the work involved!
I never thought that I live long enough to see grub 2 coming to reach the stable number 2 ;-)
-
I use grub 2 since a few month in Arch. And a few of us use the "real" grub2 since november - in order to test grub themes and such things.
-
Its not a warning, only a hint. We have synced grub2 from experimental to fixes. ...
Coincidence or am I missing something? Grub2 is comming in from Debian experimental (not siduction).
Is this supposed to work this way?
Holen: 1 http://ftp.de.debian.org/debian/ experimental/main grub-pc i386 2.00-12 [169 kB]
...
Holen: 3 http://ftp.de.debian.org/debian/ experimental/main grub-pc-bin i386 2.00-12 [800 kB]
Holen: 4 http://ftp.de.debian.org/debian/ experimental/main grub2-common i386 2.00-12 [115 kB]
Holen: 5 http://ftp.de.debian.org/debian/ experimental/main grub-common i386 2.00-12 [2.027 kB]
# apt-cache policy grub2-common
# apt-cache policy grub2-common
grub2-common:
Installiert: 1.99-26
Installationskandidat: 2.00-12
Versionstabelle:
2.00-12 0
1 http://ftp.de.debian.org/debian/ experimental/main i386 Packages
500 http://packages.siduction.org/fixes/ unstable/main i386 Packages
1.99-27 0
500 http://http.debian.net/debian/ sid/main i386 Packages
*** 1.99-26 0
500 http://ftp.de.debian.org/debian/ testing/main i386 Packages
100 /var/lib/dpkg/status
-
Sach mal, michaa7: Liest Du auch, was ich geschrieben habe? Sogar in englisch und deutsch?
Wenn der die Pakete aus experimental zieht, dann hast Du wahrscheinlich experimental aktiviert. Der Anstoß für die Pakete kommt aus fixes, der Resolver stellt äquivalente Pakete in fixes und experimental fest und entscheidet sich für experimental. Warum das so ist: Keine wirkliche Ahnung, es soll aber in diesem Fall nicht weh tun.
Spätestens, wenn die Pakete aus sid kommen, ist alles so wie es soll. Falls uns bis dahin ein apt-guru erleuchten kann, wären wir froh.
Natürlich könnten wir auch einen Praktikanten einstellen, der die Pakete mit neuer Version baut und nach fixes lädt. Freiwillige vor. :twisted:
-
Sach mal, michaa7: Liest Du auch, was ich geschrieben habe? Sogar in englisch und deutsch?
Meine güte, bleib in der spur, hätte ich es nicht gelesen, hätte ich es nicht missverstanden.
Ich zweifle das ich der einzige bin der bei "from experimental to fixes" nur an Siduction denkt (auch wenn mir dieser sync selbst merkwürdig, aber eben nicht unmöglich erschien).
Diese Fehlannahme liese sich durch ein "from Debian/experimental to Siduction/fixes" *leicht* vermeiden, für diejenigen die nicht so wie wie du mit den gerade aktuellen siduction repos vertraut sind und denen daher die gemeinten Zusammenhänge nicht so unmittelbar vor augen liegen wie dir. Dann käme deine Botschaft um so klarer rüber.
n8 (is auch englisch und deutsch)
-
Are there more grub2 packages needed? I thought I had them all installed, but "update-grub" gives me this:
GRUB >= 2.00 has been unpacked but not yet configured.
grub-mkconfig will not work until the upgrade is complete.
It should run later as part of configuring the new GRUB packages.
Also this same message came up after d-u pulled in the new 3.7-5 towo kernel, and so after reboot the grub menu is not updated.
grub-pc seems to be installed satisfactorily.
root@imerabox:/home/don# dpkg -s grub-pc
Package: grub-pc
Status: install ok installed
Priority: optional
Section: admin
Installed-Size: 543
Maintainer: GRUB Maintainers <pkg>
Architecture: amd64
Multi-Arch: foreign
Source: grub2
Version: 2.00-12
Replaces: grub, grub-common (<= 1.97~beta2-1), grub-coreboot, grub-efi-amd64, grub-efi-ia32, grub-ieee1275, grub-legacy, grub2 (<<2>= 0.5) | debconf-2.0, grub-common, grub2-common (= 2.00-12), grub-pc-bin (= 2.00-12), ucf
Conflicts: grub (<< 0.97-54), grub-coreboot, grub-efi-amd64, grub-efi-ia32, grub-ieee1275, grub-legacy
Conffiles:
/etc/kernel/postinst.d/zz-update-grub 396cb3f6a6534f7d2a02db9e8192e54f
/etc/kernel/postrm.d/zz-update-grub 396cb3f6a6534f7d2a02db9e8192e54f
Description: GRand Unified Bootloader, version 2 (PC/BIOS version)
GRUB is a portable, powerful bootloader. This version of GRUB is based on a
cleaner design than its predecessors, and provides the following new features:
.
- Scripting in grub.cfg using BASH-like syntax.
- Support for modern partition maps such as GPT.
- Modular generation of grub.cfg via update-grub. Packages providing GRUB
add-ons can plug in their own script rules and trigger updates by invoking
update-grub.
- VESA-based graphical mode with background image support and complete 24-bit
color set.
- Support for extended charsets. Users can write UTF-8 text to their menu
entries.
.
This package contains a version of GRUB that has been built for use with
traditional PC/BIOS architecture.
Homepage: http://www.gnu.org/software/grub/
Google tells me others have run into this, but I don't find any solutions, except to purge all grub packages and reinstall grub2. Is that my only path forward?
:(
-
My / is installed on a 2-device btrfs filesystem. When I upgraded, this morning, this is what I got:
Setting up grub2-common (2.00-12) ...
Setting up grub-pc-bin (2.00-12) ...
Setting up grub-pc (2.00-12) ...
Installing new version of config file /etc/kernel/postinst.d/zz-update-grub ...
Installing new version of config file /etc/kernel/postrm.d/zz-update-grub ...
device node has wrong file type
device node has wrong file type
device node has wrong file type
device node has wrong file type
Installation finished. No error reported.
Installation finished. No error reported.
Generating grub.cfg ...
/usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/sda2
/dev/sda2. Check your device.map.
Found linux image: /boot/vmlinuz-3.7-4.towo-siduction-amd64
Found initrd image: /boot/initrd.img-3.7-4.towo-siduction-amd64
Found linux image: /boot/vmlinuz-3.7-3.towo.1-siduction-amd64
Found initrd image: /boot/initrd.img-3.7-3.towo.1-siduction-amd64
/usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/sda2
/dev/sda2. Check your device.map.
Found memtest86+ image: /boot/memtest86+.bin
Found memtest86+ multiboot image: /boot/memtest86+_multiboot.bin
No volume groups found
done
Setting up grub-efi-amd64-bin (2.00-12) ...
When I rebooted, my grub menu was very ugly (tiny, squirrelly font) and there was no choice to boot Siduction. However, as I sat looking at it trying to think what to do next, it booted anyway and Siduction came up just fine.
However, I would still like to have a good grub menu. What to do, next?
Tim
-
Fixed. It was necessary to manually remove every grub* package, then to install grub-pc, then to run update-grub, and afterward it booted into the new kernel. Looks like there are things to learn about the new menu -- I never saw the kernels, only "Debian GNU/Linux", so I will become a student of grub2.
@timc, I run a 2-drive BTRFS filesystem, but I have always kept /boot on a separate SSD, because booting from BTRFS was not recommended when I built this system 2 years ago. You may be running into a new version of the old problem.
-
I guess people will be a little scared of the transition to grub2.
I found this at:
http://wiki.debian.org/Grub#Upgrading_from_v1_to_v2
Upgrading from v1 to v2
To upgrade to grub v2, you should:
Install grub v2 (but don't remove the grub 1 yet).
Follow the instruction displayed the package installation (i.e grub v1 now has an entry to cascade to grub v2, so reboot and try it, then you can actually enable grub2 bootloader by running upgrade-from-grub-legacy).
Transition from v1 to v2
Grub Transition page.
Grub Transition page is a link to:
http://wiki.debian.org/GrubTransition
I'm not able to check this out until tomorrow.
Do the devs think this is a pain free method for upgrading Grub2?
-
We do not ship grub 1, so there is no transition.
-
One of the grub developers informed me in the grub IRC channel that the problem is "fixed in trunk". I assume that means that a future package update will resolve the problem and that the revised package should be available, soon.
Tim
-
after dist-upgrade, grub2 is not working. When I try update-grub, I have:
root@W3GOR5JX63KOR37:/home/siduction# update-grub
GRUB >= 2.00 has been unpacked but not yet configured.
grub-mkconfig will not work until the upgrade is complete.
It should run later as part of configuring the new GRUB packages.
What must I do to configure GRUB?
-
what does
apt-get -f install
have to say?
greetz
devil
-
or dpkg-reconfigrure $package?
-
towo: so why isn't grub 1.99 not grub 1? Your curt answers often say so very little about the topic.
Aside: Don't know why this post appears twice. I only submitted once. And trying to delete one of them deletes both.
-
grub-legacy is grub 1
grub 1.99 is grub 2 v 1.99 aka beta
-
I tried apt-get -f install:
root@W3GOR5JX63KOR37:/home/siduction# apt-get -f install
Lendo listas de pacotes... Pronto
Construindo árvore de dependências
Lendo informação de estado... Pronto
0 pacotes atualizados, 0 pacotes novos instalados, 0 a serem removidos e 0 não atualizados.
With dpkg-reconfigure I have nothing:
root@W3GOR5JX63KOR37:/home/siduction# dpkg-reconfigure grub2-common
root@W3GOR5JX63KOR37:/home/siduction# dpkg-reconfigure grub-pc-bin
root@W3GOR5JX63KOR37:/home/siduction# dpkg-reconfigure grub-common
root@W3GOR5JX63KOR37:/home/siduction# dpkg-reconfigure grub-efi-amd64-bin
root@W3GOR5JX63KOR37:/home/siduction#
-
No, none of that will fix it. I had the same problem -- see my posts above -- you must use apt-get and remove each and every grub package on your system. To see them all, do
apt-cache policy grub*
and find the ones that are installed (I'm sure there is a more elegant way ...) then remove each one until there are none installed. Then
apt-get install grub-pc
and it should be installed correctly. Then update-grub
and then if you see no errors, you can reboot.
-
towo:
Thank you for the clarification of the grub versions.
-
dibl:
I've successfully used your method for installing grub2. I only had to remove grub-pc-bin, grub-common, grub-pc and grub2-common and install grub-pc and update-grub.
Thank you very much.
-
dibl, I follow your 3-steps recommendation, and it didn't work: what could be happen?
-
gilpier
What shows
# dpkg-query -l 'grub*'
# dpkg-reconfigure grub-pc
should work and invoke update-grub
No problem here and no necessity to reinstall any package. Did you notice any other error?
Abraço
Bequimão
-
dibl, I follow your 3-steps recommendation, and it didn't work: what could be happen?
I don't know -- are you sure you removed every installed grub package, before you installed grub-pc?
Yesterday I googled your error, which also happened on my oldest installation, but not on 2 other ones. The only solution I could find was to remove all grub packages of any kind first, then there was no error when I installed grub-pc.
I also had no luck with dpkg-reconfigure grub-pc, and no luck with apt-get -f install.
-
Bequimão, # dpkg-query -l 'grub*' output is:
root@W3GOR5JX63KOR37:/home/siduction# dpkg-query -l 'grub*'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Nome Versão Arquitectura Descrição
+++-=======================================-========================-========================-===================================================================================
un grub <nenhuma> (nenhuma descrição disponível)
ii grub-common 2.00-12 amd64 GRand Unified Bootloader (common files)
rc grub-coreboot 2.00-12 amd64 GRand Unified Bootloader, version 2 (Coreboot version)
un grub-coreboot-bin <nenhuma> (nenhuma descrição disponível)
un grub-doc <nenhuma> (nenhuma descrição disponível)
un grub-efi <nenhuma> (nenhuma descrição disponível)
un grub-efi-amd64 <nenhuma> (nenhuma descrição disponível)
un grub-efi-ia32 <nenhuma> (nenhuma descrição disponível)
un grub-efi-ia64 <nenhuma> (nenhuma descrição disponível)
un grub-emu <nenhuma> (nenhuma descrição disponível)
un grub-ieee1275 <nenhuma> (nenhuma descrição disponível)
un grub-legacy <nenhuma> (nenhuma descrição disponível)
un grub-legacy-doc <nenhuma> (nenhuma descrição disponível)
un grub-linuxbios <nenhuma> (nenhuma descrição disponível)
ii grub-pc 2.00-12 amd64 GRand Unified Bootloader, version 2 (PC/BIOS version)
ii grub-pc-bin 2.00-12 amd64 GRand Unified Bootloader, version 2 (PC/BIOS binaries)
un grub-yeeloong <nenhuma> (nenhuma descrição disponível)
un grub2 <nenhuma> (nenhuma descrição disponível)
ii grub2-common 2.00-12 amd64 GRand Unified Bootloader (common files for version 2)
When I tried # dpkg-reconfigure grub-pc , the output was:
root@W3GOR5JX63KOR37:/home/siduction# # dpkg-reconfigure grub-pc
root@W3GOR5JX63KOR37:/home/siduction# update-grub
GRUB >= 2.00 has been unpacked but not yet configured.
grub-mkconfig will not work until the upgrade is complete.
It should run later as part of configuring the new GRUB packages.
root@W3GOR5JX63KOR37:/home/siduction#
Um grande abraço,
Gilbert
-
dibl, I follow your 3-steps recommendation, and it didn't work: what could be happen?
I don't know -- are you sure you removed every installed grub package, before you installed grub-pc?
Yesterday I googled your error, which also happened on my oldest installation, but not on 2 other ones. The only solution I could find was to remove all grub packages of any kind first, then there was no error when I installed grub-pc.
I also had no luck with dpkg-reconfigure grub-pc, and no luck with apt-get -f install.
Dibl, I repeat and verify the procedure several times.
In my computer there are 5 differents OS: windows 7, Siduction, Aptosid, Ubuntu and Mepis. When siduction grub problem began, I installed Mepis grub at MBR, that is what I am using now.
Thanks,
Gilbert
-
gilpier,
dpkg -l grub* | grep ii
shows only what grub-packages areinstalled.
greetz
devil
-
root@siductionbox:/home/bequimao# LANG=C dpkg-query -l 'grub*'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==========================================-==========================-==========================-=========================================================================================
un grub <none> (no description available)
ii grub-common 2.00-12 amd64 GRand Unified Bootloader (common files)
un grub-coreboot <none> (no description available)
un grub-doc <none> (no description available)
un grub-efi <none> (no description available)
un grub-efi-amd64 <none> (no description available)
ii grub-efi-amd64-bin 2.00-12 amd64 GRand Unified Bootloader, version 2 (EFI-AMD64 binaries)
un grub-efi-ia32 <none> (no description available)
un grub-efi-ia64 <none> (no description available)
un grub-emu <none> (no description available)
un grub-ieee1275 <none> (no description available)
un grub-legacy <none> (no description available)
un grub-legacy-doc <none> (no description available)
un grub-linuxbios <none> (no description available)
ii grub-pc 2.00-12 amd64 GRand Unified Bootloader, version 2 (PC/BIOS version)
ii grub-pc-bin 2.00-12 amd64 GRand Unified Bootloader, version 2 (PC/BIOS binaries)
un grub-yeeloong <none> (no description available)
un grub2 <none> (no description available)
ii grub2-common 2.00-12 amd64 GRand Unified Bootloader (common files for version 2)
ii grub2-fll-fromiso 0.3.0 all update-grub (grub2) plugin for fullstory fromiso
This is how it look like in my system. Differences are found in grub-coreboot and grub-efi-amd64-bin. grub-efi-amd64-bin is installed, though I have no efi system. Are there different active repos?
root@siductionbox:/home/bequimao# cat /etc/apt/sources.list.d/siduction.list
## os pacotes oficiais do siduction
deb http://www.las.ic.unicamp.br/pub/siduction/base unstable main contrib non-free
#deb http://www.las.ic.unicamp.br/pub/siduction/experimental unstable main contrib non-free
#deb-src http://www.las.ic.unicamp.br/pub/siduction/base unstable main contrib non-free
#deb http://www.las.ic.unicamp.br/pub/siduction/extra unstable main contrib non-free
#deb-src http://www.las.ic.unicamp.br/pub/siduction/extra unstable main contrib non-free
#deb http://www.las.ic.unicamp.br/pub/siduction/user unstable main contrib non-free
#deb-src http://www.las.ic.unicamp.br/pub/siduction/user unstable main contrib non-free
## correções de pacotes Debian
deb http://www.las.ic.unicamp.br/pub/siduction/fixes unstable main contrib non-free
#deb http://www.las.ic.unicamp.br/pub/siduction/experimental unstable main
#deb-src http://www.las.ic.unicamp.br/pub/siduction/fixes unstable main contrib non-free
## somente para o razor-qt
#deb http://www.las.ic.unicamp.br/pub/siduction/razorqt unstable main
#deb-src http://www.las.ic.unicamp.br/pub/siduction/razorqt unstable main
Bequimão
-
In my computer there are 5 differents OS: windows 7, Siduction, Aptosid, Ubuntu and Mepis. When siduction grub problem began, I installed Mepis grub at MBR, that is what I am using now.
I have only siduction (other OSs are VMs) on my system, so possibly the problem is with the new os-prober. But the error was exactly the same on my system, and if you try a google with the full error, you will learn that you are not the only one.
-
When I removed 00_header and 00_header.dpkg.dist from inside /etc/grub.d, #update-grub works, but now /etc/default/grub isn't working.
It seems that 00_header and 00_header.dpkg.dist are corrupted: how can I create new 00_archives?
Thanks.
-
In /etc/grub.d I have only 00_header -- no 00_header.dpkg.dist (I have never heard of that file). If you PM me with your e-mail address, I will zip up 00_header and send it to you -- maybe that will fix it.
-
In /etc/grub.d I have only 00_header -- no 00_header.dpkg.dist (I have never heard of that file). If you PM me with your e-mail address, I will zip up 00_header and send it to you -- maybe that will fix it.
dibl, my e.mail is :
thanks,
Gilbert
-
The problem was in corrupted 00_header. I copy 00_header from MEPIS 12, and now my grub is working fine.
Much thanks for everybody who help me.
Gilbert
-
Little hint: delete your mail-address in the above post. You won't test the spamfilter of your provider...
-
Little hint: delete your mail-address in the above post. You won't test the spamfilter of your provider...
I already do it, thanks !
-
I solved the problem by purging all old grub-files.
Then installed grup-pc and dependecies.
After that a config-script started and i could select the device where grub has to be installed.
Greetings
-
@all: purging is a good idea - or try at least
mv /etc/grub.d /etc/grub.d.sss
if you have own scripts or modified scripts. You can diff them later.
Another way is to use the complete maintainer files. apt will ask you. Your own files remain untouched.
-
Grub erst zu löschen und dann neu in den mbr zu installieren löst mein Problem nicht:
Entpacken von grub-common (aus .../grub-common_2.00-12_amd64.deb) ...
Vormals nicht ausgewähltes Paket grub2-common wird gewählt.
Entpacken von grub2-common (aus .../grub2-common_2.00-12_amd64.deb) ...
Vormals nicht ausgewähltes Paket grub-pc-bin wird gewählt.
Entpacken von grub-pc-bin (aus .../grub-pc-bin_2.00-12_amd64.deb) ...
Vormals nicht ausgewähltes Paket grub-pc wird gewählt.
Entpacken von grub-pc (aus .../grub-pc_2.00-12_amd64.deb) ...
Trigger für man-db werden verarbeitet ...
Trigger für install-info werden verarbeitet ...
install-info: warning: no info dir entry in `/usr/share/info/gtkdialog.info.gz'
grub-common (2.00-12) wird eingerichtet ...
grub2-common (2.00-12) wird eingerichtet ...
grub-pc-bin (2.00-12) wird eingerichtet ...
grub-pc (2.00-12) wird eingerichtet ...
Creating config file /etc/default/grub with new version
installation beendet. Keine Fehler aufgetreten.
grub.cfg wird erstellt …
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Linux-Abbild gefunden: /boot/vmlinuz-3.7-5.towo-siduction-amd64
initrd-Abbild gefunden: /boot/initrd.img-3.7-5.towo-siduction-amd64
Linux-Abbild gefunden: /boot/vmlinuz-3.7-2.towo-siduction-amd64
initrd-Abbild gefunden: /boot/initrd.img-3.7-2.towo-siduction-amd64
Linux-Abbild gefunden: /boot/vmlinuz-3.6-7.towo-siduction-amd64
initrd-Abbild gefunden: /boot/initrd.img-3.6-7.towo-siduction-amd64
No volume groups found
Windows 7 (loader) auf /dev/sdb1 gefunden
cat: /video.lst: Datei oder Verzeichnis nicht gefunden
/usr/sbin/grub-probe: Fehler: Kanonischer Pfad von »« konnte nicht ermittelt werden.
/usr/sbin/grub-probe: Fehler: Für konnte kein GRUB-Laufwerk gefunden werden. Überprüfen Sie Ihre device.map.
dpkg: Fehler beim Bearbeiten von grub-pc (--configure):
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
Fehler traten auf beim Bearbeiten von:
grub-pc
Was hat es denn mit dieser video.lst auf sich? Wo kann ich die finden und ggf. modifizieren? (Oder tut das gar nicht Not?)
Wäre dankbar für nen spontanen Hinweis …
-
OK. Bin wohl nen Schritt weiter. Das Problem scheint die fehlende device.map zu sein. Die wird - warumauchimmer - nicht erzeugt. Kann ich das per Hand erledigen; was muss da rein?
-
t0mte,
root@siductionbox:/home/devil# cat /boot/grub/device.map
(hd0) /dev/disk/by-id/ata-OCZ-VERTEX3_OCZ-8S25SB84NT4EB514
(hd1) /dev/disk/by-id/ata-OCZ-VERTEX3_OCZ-P1273E8764B066A5
(hd2) /dev/disk/by-id/ata-ST3160023AS_3JS3BKZD
(hd3) /dev/disk/by-id/usb-Generic_Flash_Disk_B90C46BB-0:0
und ja, kannst du auch manuell erstellen.
greetz
devil
-
Hilft nicht wirklich; update-grub scheitert weiterhin. Vermutlich weil grub-probe scheitert, welches udev nicht findet . Wattnu?
-
...I never saw the kernels, only "Debian GNU/Linux", so I will become a student of grub2.
...
Hi dibl,
did you find a way to make visible the expanded, real kernel name in Grub2 menue?
(I did not d-u for some days as I was concerned about the grub2 bug mentioned in this thread. Now I d-u-ed nontheless and no error occured. It seems this error triggers only under specific conditions.
But when rebooting, apart from the fonts in the Grub menue now being tiny, I only see "Debian GNU/Linux", no real kernel name)
-
Hilft nicht wirklich; update-grub scheitert weiterhin. Vermutlich weil grub-probe scheitert, welches udev nicht findet . Wattnu?
Oder weil deine device.map nicht stimmt und daher deine pfade auch nicht.
Oder:
Is udev (noch) installiert?
# apt-cache policy udev
udev:
Installiert: 175-7.1
...
-
udev ist installiert und aktuell.
Und die device.map hab ich per Hand erstellt
ego@~ > cat /boot/grub/device.map
(hd0) /dev/disk/by-id/ata-WDC_WD15EARS-00MVWB0_WD-WMAZA0483864
(hd1) /dev/disk/by-id/ata-SAMSUNG_HD501LJ_S0MUJ1FPA87519
Weitere Vorschläge?
-
...
Weitere Vorschläge?
Wie kommst du darauf, dass aktuell dies die richtige reihenfolge darstellt (nicht dass ich behaupten will sie wäre falsch!)?
Wenn der eintrag willkürlich war, dreh' in doch mal *testweise* um.
EDIT://
BTW: versuchmal TAB statt leerzeichen in der device.map, zumindest habe ich das mal in nem forum als fehlerursache so gelesen
-
Das stellt die richtige Reihenfolge dar, zumindest wenn ich /dev glauben darf (und da auch sonst nüscht am System gebastelt wurde); und darauf verlasse ich mich gerade einfach mal …
-
Hi dibl,
did you find a way to make visible the expanded, real kernel name in Grub2 menue?
Yes. If you click the next line down, "Advanced option for Debian GNU/Linux", then it will expand and show you the installed kernels, and you can choose one.
Regarding the grub splash image, I am finding different behaviors on different computers. The method I posted above works great on two older computers, but not at all on my Asus P6X58D-E motherboard. Fortunately this one only gets rebooted when towo releases a new kernel, so I don't see grub much anyway.
-
Hallo zusammen,
habe ebenfalls Probleme bei einem Laptop mit grub. Fehlermeldung lautete etwa sinngemäß:
Der MBR konnte nicht auf /dev/sda geschrieben werden.
Auch ein Löschen sämtlicher grub-* Pakete und anschließender Neuinstallation brachte nichts, ebenso verhielt sich "dpk-reconfigure grub-pc" :?
Vermutlich ist das ein Bug. Werde mal nachforschen. Ich habe alle grub-Pakete auf HOLD gesetzt und dann einen d-u durchgeführt.
-
Das stellt die richtige Reihenfolge dar, zumindest wenn ich /dev glauben darf ...
Das ist eine alphabetische reihenfolge, nichts sonst. Ich zweifle das Grub das alphabet beherrscht bzw. sich daran hält, dann bräuchte man nämlich keine device.map, wenn das alphabet *für Grub* eine verbindliche regel darstellen würde.
Klar ist lediglich dass grub eine installierte komponente nicht findet. Das kann dann nur ein pfadfehler sein. Und wenn zwischenzeitlich grub auf die verkehrte platte geschrieben wurde, dann ist ja garnicht klar ob du an dem grub herumschraubst der beim neustart dann versucht das OS zu booten.
-
Yes. If you click the next line down, "Advanced option for Debian GNU/Linux", ..
Easy-peasy. I should have found myself. Thanks anyway.
-
@micha and dibl: a good starting point is /etc/default/grub.
Edit: für den Kernelname. Ich empfehle die Nutzung von programmen wie awk und für den Distributor /etc/siduction-version.
GRUB_DISTRIBUTOR=`awk -F '(' '{ print $1 }' /etc/siduction-version`
-
Nice command, agaida, works fine.
Actually I like the naming "Debian GNU/Linux" as it reflects my affection for Debian. OTOH, I am / we are not using a Debian stock kernel and thus your command is very sensible.
-
Ich empfehle die Nutzung von programmen wie awk und für den Distributor /etc/siduction-version.
GRUB_DISTRIBUTOR=`awk -F '(' '{ print $1 }' /etc/siduction-version`
awk is on the long list of languages which I cannot speak.
However, thank you for doing it for me! :D
-
Hallo zusammen,
ich hoffe ich bin in diesem Thread richtig.
Leider habe ich auch ein Problem mit Grub/LVM und fehlender module.
Nach einem dist-upgrade, wobei grub2 von version 1.98 nach 2.01 ersetzt wurde, scheitert ein update-grub mit der Meldung, dass core.img sei zu gross und könne nicht in den MBR grschrieben werden.
Leider konnte ich die alten grub2 Paket nicht mit apt oder dkpg wegen diverser Paketabhängigkeiten zurückspielen.
Also entschied ich mich für eine Neuinstallation, da ich noch aptosid auf dem Laptop hatte und mich Siduction 2012.2 interessiert.
Also installer gestartet. LVM die schon bestanden dem installer mitgeteilt.
Alles neu installiert ohne Fehlermeldung. System neu gebootet. Alles funktioniert.
Neu gebootet. Danach:
- init 3
- apt-get update, dist-upgrade
Jetzt werden die neuen Grub pakete eingespielt und es gibt die gleiche Fehlermeldung core.img ist zu gross für MBR.
nun mit apt-get install die alten Grub (1.9X) Pakete wieder eingespielt. Mit update-grub aktualisiert. Keine Fehlermeldung. Scheinbar alles OK.
Heute Laptop hochgefahren:
Bootvorgang stoppt bei (initramfs) mit Meldung "findet kein LVM".
mit vgchange -a y die volumes angegeben und sie werden erkannt.
(initramfs) mit exit beendet. Geht leider nicht, da Fehlermeldung:
modprobe: module i8042 not found in modules.dep
modprobe: module atkbd not found in modules.dep
Jetzt weiss ich leider nicht mehr weiter, was kann ich tun?
Wäre nett wenn Ihr mir helfen könntet.
Danke und Gruß,
Markus
-
die modules Fehlermeldung kann man ignorieren.
da von den 2 lv's eines verschlüselt ist, musste ich erst dieses verschlüsselte lv mit luksOpen öffnen danach war ich im System.
Muss später probieren, wie ich grub das luksOpen wieder beibringe, da ich jetzt keine Zeit habe.
Gruss,
Markus
-
@ WhiteDwarf,
Prinzipiell funktioniert die neue Grub-Version im (unverschlüsselten) LVM, jedenfalls hier. Also kein Upgrade Warning. Damit es funzt, muß die Datei core.img zusammenhängend (contiguous) sein und mit den Blockgrenzen der Festplatte übereinstimmen. Eventuell kein Platz mehr in der logischen Partition für die Installation des core.img?
Grüße
Bequimão
-
@ WhiteDwarf,
Prinzipiell funktioniert die neue Grub-Version im (unverschlüsselten) LVM, jedenfalls hier. Also kein Upgrade Warning. Damit es funzt, muß die Datei core.img zusammenhängend (contiguous) sein und mit den Blockgrenzen der Festplatte übereinstimmen. Eventuell kein Platz mehr in der logischen Partition für die Installation des core.img?
Grüße
Bequimão
Hallo Bequimão,
ich bleibe erst mal bei der alten Version von Grub2 (1.9X).
Ich muss zuerst das Problem lösen, dass initramfs keine Passwortfrage zum Öffnen des LV-Crypt auslöst, das die VG für root, home und swap enthält.
Ging bisher immer, warum jetzt nicht mehr ist mir noch schleierhaft.
Hat jemand eine Idee?
Gruß,
Markus
-
Das Problem hatte ich doch auch schon, und es liegt vor dem Öffnen der /root-partition
http://forum.siduction.org/index.php?msg=23397#23397 (http://forum.siduction.org/index.php?msg=23397#23397)
Bitte gib die englischen Originalfehlermeldungen an, so daß kein Ratespiel entsteht.
Grüße,
Bequimão
-
Sorry, but I really wonder? Is all this really about upgrade warnings? I usually have a look here to check if it's ok to d-u and now there have been a very long German discussion about Grub here? If all this is a Grub d-u problem, please write in English and if not, maybe it shall be moved somewhere else?
-
The grub d-u issue was not an issue for me this morning (over 12 hours ago).
Sorry, but I really wonder? Is all this really about upgrade warnings?
Yes. At least mostly. My German (DE) is not what I would like it to be but I have been able to derive from what little I understand there and the English (EN) to make sense of it all.
I usually have a look here to check if it's ok to d-u and now there have been a very long German discussion about Grub here? If all this is a Grub d-u problem, please write in English and if not, maybe it shall be moved somewhere else?
Growing pains for the forum maybe? This is a dual-language section of the forum (note the "DE & EN" in the name) so this is probably the best place for this thread.
That said, I don't see where this is marked 'solved', though. I never had a problem but, like you, was checking here to see if it was safe to d-u. From my perspective, it is.
dpkg -l grub*|grep ii
yields
ii grub-common 2.00-12 i386 GRand Unified Bootloader (common files)
ii grub-pc 2.00-12 i386 GRand Unified Bootloader, version 2 (PC/BIOS version)
ii grub-pc-bin 2.00-12 i386 GRand Unified Bootloader, version 2 (PC/BIOS binaries)
ii grub2-common 2.00-12 i386 GRand Unified Bootloader (common files for version 2)
-
This threat is not really a upgrade warning. The majority of users had no problem with updating to grub2. The ones that do had most probably altered config-files they should not have altered or have issues with LVM/RAID and/or encryption. I will leave this threat here, as it is DE/EN already and therefore fits nowhere else really.
greetz
devil
-
:twisted: May be some nasty user or mod might do a little imposition or extra excercise to split this into two or three threads in german and english to clean it. :twisted:
-
This threat is not really a upgrade warning. The majority of users had no problem with updating to grub2. The ones that do had most probably altered config-files they should not have altered or have issues with LVM/RAID and/or encryption. I will leave this threat here, as it is DE/EN already and therefore fits nowhere else really.
greetz
devil
Thank you devil, that made me understand a little more whats going on.
-
Das Problem hatte ich doch auch schon, und es liegt vor dem Öffnen der /root-partition
http://forum.siduction.org/index.php?msg=23397#23397 (http://forum.siduction.org/index.php?msg=23397#23397)
Bitte gib die englischen Originalfehlermeldungen an, so daß kein Ratespiel entsteht.
Grüße,
Bequimão
Dear all,
for making sure everybody who is interested in this issue, I will hopefully explain a little bit more clear about my setup.
Aim is to setup siduction 2012.2 on a laptop with encryprted LV / VG according to siduction manual. I have done it with aptosid on 3 Laptops years ago.
With the last "dist-upgrade" on one of this laptops,I received the message during "update-grub": "core.img" is to big, can't be installed on MBR of /dev/sda. And it also failed to install into a logical volume.
So I decided to switch completly from aptosid to siduction.
I installed installed Siduction 2012.2 with following LV/VG setup on disk /dev/sda and everything was working well.
This is the LV-Setup:
root@spica:/home/markus# lvdisplay
--- Logical volume ---
LV Path /dev/crypt_spica/swap
LV Name swap
VG Name crypt_spica
LV UUID m1gKh1-CrA9-ANAD-x13p-pWxh-DOuJ-9B6Epo
LV Write Access read/write
LV Creation host, time ,
LV Status available
# open 2
LV Size 2,00 GiB
Current LE 512
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:3
--- Logical volume ---
LV Path /dev/crypt_spica/root
LV Name root
VG Name crypt_spica
LV UUID rt8M3l-HwsN-j0kR-Ihf3-foCe-B9lg-rdwOXq
LV Write Access read/write
LV Creation host, time ,
LV Status available
# open 1
LV Size 30,00 GiB
Current LE 7680
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:4
--- Logical volume ---
LV Path /dev/crypt_spica/home
LV Name home
VG Name crypt_spica
LV UUID O1HCCv-tG7w-HXi5-GhVt-1jf2-Bi2O-r1l20r
LV Write Access read/write
LV Creation host, time ,
LV Status available
# open 1
LV Size 42,28 GiB
Current LE 10823
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:5
--- Logical volume ---
LV Path /dev/spica/boot
LV Name boot
VG Name spica
LV UUID A3lgeV-1Olh-XGm7-mkD9-gxJh-a967-EzGDw9
LV Write Access read/write
LV Creation host, time ,
LV Status available
# open 1
LV Size 252,00 MiB
Current LE 63
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:0
--- Logical volume ---
LV Path /dev/spica/crypt
LV Name crypt
VG Name spica
LV UUID zkCfkW-7p1c-5c2D-wGHv-Bhj9-wHQt-k5PVLQ
LV Write Access read/write
LV Creation host, time ,
LV Status available
# open 1
LV Size 74,28 GiB
Current LE 19016
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:1
For having newest packages and firmware for ipw2200, i have made a "apt-get update" and "apt-get dist-upgrade".
Then I received the "update-grub" message, described above once more. For me, it looks like the easiest way seems to downgrade the grub packages to version 1.99 with apt-get install packageXY=version.
It run smoothly through with no error messages.
For being sure, I have made an "update-grub" once more.
But after rebooting the system it stops during boot and is going into initramfs shell.
"vgchange -ay" in the console will activate 2 logical volumes: spica-boot and spica-crypt
"cryptsetup luksOpen /dev/mapper/spica-crypt cryptroot" activates the password sequence and granted access to the crypted LV
"vgchange -ay" will activate now another 3 logical volumes: crypt_spica-root, crypt_spica-home, crypt_spica-swap
Now I can exit initramfs and the system is booting into runlevel 5.
In "etc/default/grub" I have added a rootdelay of 5 and made "update-grub", but still the same problem during boot.
I tried to pick out the messages as follows:
syslog:
Feb 7 10:39:02 spica /USR/SBIN/CRON[18170]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -depth -mindepth 1 -maxdepth 1 -type f -ignore_readdir_race -cmin +$(/usr/lib/php5/maxlifetime) ! -execdir fuser -s {} 2>/dev/null \; -delete)
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sda1
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/10freedos on mounted /dev/mapper/crypt_spica-home
Feb 7 10:41:06 spica 10freedos: debug: /dev/mapper/crypt_spica-home is not a FAT partition: exiting
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/10qnx on mounted /dev/mapper/crypt_spica-home
Feb 7 10:41:06 spica 10qnx: debug: /dev/mapper/crypt_spica-home is not a QNX4 partition: exiting
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/20macosx on mounted /dev/mapper/crypt_spica-home
Feb 7 10:41:06 spica macosx-prober: debug: /dev/mapper/crypt_spica-home is not an HFS+ partition: exiting
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/20microsoft on mounted /dev/mapper/crypt_spica-home
Feb 7 10:41:06 spica 20microsoft: debug: /dev/mapper/crypt_spica-home is not a MS partition: exiting
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/30utility on mounted /dev/mapper/crypt_spica-home
Feb 7 10:41:06 spica 30utility: debug: /dev/mapper/crypt_spica-home is not a FAT partition: exiting
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/40lsb on mounted /dev/mapper/crypt_spica-home
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/70hurd on mounted /dev/mapper/crypt_spica-home
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/80minix on mounted /dev/mapper/crypt_spica-home
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/83haiku on mounted /dev/mapper/crypt_spica-home
Feb 7 10:41:06 spica 83haiku: debug: /dev/mapper/crypt_spica-home is not a BeFS partition: exiting
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/90linux-distro on mounted /dev/mapper/crypt_spica-home
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/90solaris on mounted /dev/mapper/crypt_spica-home
Feb 7 10:41:06 spica os-prober: debug: /dev/mapper/crypt_spica-swap: is active swap
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/10freedos on mounted /dev/mapper/spica-boot
Feb 7 10:41:06 spica 10freedos: debug: /dev/mapper/spica-boot is not a FAT partition: exiting
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/10qnx on mounted /dev/mapper/spica-boot
Feb 7 10:41:06 spica 10qnx: debug: /dev/mapper/spica-boot is not a QNX4 partition: exiting
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/20macosx on mounted /dev/mapper/spica-boot
Feb 7 10:41:06 spica macosx-prober: debug: /dev/mapper/spica-boot is not an HFS+ partition: exiting
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/20microsoft on mounted /dev/mapper/spica-boot
Feb 7 10:41:06 spica 20microsoft: debug: /dev/mapper/spica-boot is not a MS partition: exiting
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/30utility on mounted /dev/mapper/spica-boot
Feb 7 10:41:06 spica 30utility: debug: /dev/mapper/spica-boot is not a FAT partition: exiting
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/40lsb on mounted /dev/mapper/spica-boot
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/70hurd on mounted /dev/mapper/spica-boot
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/80minix on mounted /dev/mapper/spica-boot
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/83haiku on mounted /dev/mapper/spica-boot
Feb 7 10:41:06 spica 83haiku: debug: /dev/mapper/spica-boot is not a BeFS partition: exiting
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/90linux-distro on mounted /dev/mapper/spica-boot
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/90solaris on mounted /dev/mapper/spica-boot
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/mapper/spica-crypt
Feb 7 10:41:06 spica 50mounted-tests: debug: /dev/mapper/spica-crypt is a LUKS partition; skipping
messages:
Feb 7 10:12:44 spica os-prober: debug: os detected by /usr/lib/os-probes/50mounted-tests
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sda1
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/10freedos on mounted /dev/mapper/crypt_spica-home
Feb 7 10:41:06 spica 10freedos: debug: /dev/mapper/crypt_spica-home is not a FAT partition: exiting
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/10qnx on mounted /dev/mapper/crypt_spica-home
Feb 7 10:41:06 spica 10qnx: debug: /dev/mapper/crypt_spica-home is not a QNX4 partition: exiting
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/20macosx on mounted /dev/mapper/crypt_spica-home
Feb 7 10:41:06 spica macosx-prober: debug: /dev/mapper/crypt_spica-home is not an HFS+ partition: exiting
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/20microsoft on mounted /dev/mapper/crypt_spica-home
Feb 7 10:41:06 spica 20microsoft: debug: /dev/mapper/crypt_spica-home is not a MS partition: exiting
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/30utility on mounted /dev/mapper/crypt_spica-home
Feb 7 10:41:06 spica 30utility: debug: /dev/mapper/crypt_spica-home is not a FAT partition: exiting
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/40lsb on mounted /dev/mapper/crypt_spica-home
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/70hurd on mounted /dev/mapper/crypt_spica-home
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/80minix on mounted /dev/mapper/crypt_spica-home
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/83haiku on mounted /dev/mapper/crypt_spica-home
Feb 7 10:41:06 spica 83haiku: debug: /dev/mapper/crypt_spica-home is not a BeFS partition: exiting
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/90linux-distro on mounted /dev/mapper/crypt_spica-home
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/90solaris on mounted /dev/mapper/crypt_spica-home
Feb 7 10:41:06 spica os-prober: debug: /dev/mapper/crypt_spica-swap: is active swap
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/10freedos on mounted /dev/mapper/spica-boot
Feb 7 10:41:06 spica 10freedos: debug: /dev/mapper/spica-boot is not a FAT partition: exiting
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/10qnx on mounted /dev/mapper/spica-boot
Feb 7 10:41:06 spica 10qnx: debug: /dev/mapper/spica-boot is not a QNX4 partition: exiting
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/20macosx on mounted /dev/mapper/spica-boot
Feb 7 10:41:06 spica macosx-prober: debug: /dev/mapper/spica-boot is not an HFS+ partition: exiting
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/20microsoft on mounted /dev/mapper/spica-boot
Feb 7 10:41:06 spica 20microsoft: debug: /dev/mapper/spica-boot is not a MS partition: exiting
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/30utility on mounted /dev/mapper/spica-boot
Feb 7 10:41:06 spica 30utility: debug: /dev/mapper/spica-boot is not a FAT partition: exiting
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/40lsb on mounted /dev/mapper/spica-boot
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/70hurd on mounted /dev/mapper/spica-boot
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/80minix on mounted /dev/mapper/spica-boot
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/83haiku on mounted /dev/mapper/spica-boot
Feb 7 10:41:06 spica 83haiku: debug: /dev/mapper/spica-boot is not a BeFS partition: exiting
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/90linux-distro on mounted /dev/mapper/spica-boot
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/90solaris on mounted /dev/mapper/spica-boot
Feb 7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/mapper/spica-crypt
Feb 7 10:41:06 spica 50mounted-tests: debug: /dev/mapper/spica-crypt is a LUKS partition; skipping
Feb 7 10:41:06 spica os-prober: debug: os detected by /usr/lib/os-probes/50mounted-tests
dmesg:
.
[ 0.000000] pcpu-alloc: [0] 0 [0] 1
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 257681
[ 0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.7-6.towo-siduction-686 root=/dev/mapper/crypt_spica-root ro rootdelay=5 quiet rootdelay=5
[ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
.
.
.
[ 215.950422] Adding 2097148k swap on /dev/mapper/crypt_spica-swap. Priority:-1 extents:1 across:2097148k
[ 215.967817] EXT4-fs (dm-4): re-mounted. Opts: (null)
[ 216.836896] EXT4-fs (dm-4): re-mounted. Opts: errors=remount-ro
[ 217.651772] fuse init (API version 7.20)
[ 219.159324] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: errors=remount-ro
[ 219.261545] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: errors=remount-ro
[ 220.962901] RPC: Registered named UNIX socket transport module.
[ 220.962907] RPC: Registered udp transport module.
[ 220.962910] RPC: Registered tcp transport module.
[ 220.962912] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 221.006380] FS-Cache: Loaded
[ 221.076521] FS-Cache: Netfs 'nfs' registered for caching
[ 221.151584] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[ 221.226148] 8139too 0000:02:01.0 eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
Sorry, for maybe too long code messages, but for now I dont know further.
I see the problem is that the encrypted LV is not recognized.
It would be nice if you could help.
Thanks and regards,
Markus
-
@WhiteDwarf: Please post the 'linux' line from the /etc/grub/grub.cfg file, the content of /etc/crypttab as well as /etc/fstab.
And please give the output of ls -al /dev/disk/by-label
ls -al /dev/disk/by-uuid
ls -al /dev/mapper
to check if the labels and uuids are picked up correctly.
P.S. You would be better of with a dedicated thread of your own... Though grub is part of the boot process, it is just one small part of it.
-
root@spica:/home/markus# ls -al /dev/disk/by-uuid
insgesamt 0
drwxr-xr-x 2 root root 140 Feb 7 11:45 .
drwxr-xr-x 5 root root 100 Feb 7 11:40 ..
lrwxrwxrwx 1 root root 10 Feb 7 11:45 0f6bce1f-6c1f-472c-9efd-558bb628bf3e -> ../../dm-5
lrwxrwxrwx 1 root root 10 Feb 7 11:40 131fae7f-72e4-4760-9107-fdc4e0c89671 -> ../../dm-0
lrwxrwxrwx 1 root root 10 Feb 7 11:45 5a8fe144-5178-4216-8a98-6d25d22765da -> ../../dm-4
lrwxrwxrwx 1 root root 10 Feb 7 11:40 79229db4-d606-4f32-9230-713af7e67e1e -> ../../dm-1
lrwxrwxrwx 1 root root 10 Feb 7 11:45 bbf43211-5015-40f8-8377-67d91718be00 -> ../../dm-3
grub.cfg
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Debian GNU/Linux, mit Linux 3.7-6.towo-siduction-686' --class debian --class gnu-linux --class gnu --class os {
load_video
insmod gzio
insmod lvm
insmod part_msdos
insmod ext2
set root='(spica-boot)'
search --no-floppy --fs-uuid --set=root 131fae7f-72e4-4760-9107-fdc4e0c89671
echo 'Linux 3.7-6.towo-siduction-686 wird geladen …'
linux /vmlinuz-3.7-6.towo-siduction-686 root=/dev/mapper/crypt_spica-root ro rootdelay=5 quiet rootdelay=5
echo 'Initiale Ramdisk wird geladen …'
initrd /initrd.img-3.7-6.towo-siduction-686
}
cryptab, was empty in the past and has worked well, now I have tried the following:
# <target> <source> <key> <options>
cryptroot /dev/spica-crypt 79229db4-d606-4f32-9230-713af7e67e1e none luks
fstab
UUID=131fae7f-72e4-4760-9107-fdc4e0c89671 /boot ext4 defaults,relatime,errors=remount-ro 0 2
UUID=bbf43211-5015-40f8-8377-67d91718be00 none swap sw 0 0
UUID=5a8fe144-5178-4216-8a98-6d25d22765da / ext4 defaults,relatime,errors=remount-ro 0 1
UUID=0f6bce1f-6c1f-472c-9efd-558bb628bf3e /home ext4 defaults,relatime,errors=remount-ro 0 2
192.168.1.12:/media /multimedia nfs nfsvers=3,rsize=65536,wsize=65536,tcp,noatime,intr
192.168.1.12:/backup /backup nfs nfsvers=3,rsize=65536,wsize=65536,tcp,noatime,intr
PS: I'm not quit sure if devil is happy, when starting a new thread
-
Let me asure you that if you open a new thread, it will leave me pretty much ummoved emotionaly. ;)
greetz
devil
-
Let me asure you that if you open a new thread, it will leave me pretty much ummoved emotionaly. ;)
greetz
devil
Hi devil,
if you say so...
I will try to open a new one.
regards,
M.
-
Dear all,
I opened a new thread for this "my problem"
http://forum.siduction.org/index.php?msg=27437#27437 (http://forum.siduction.org/index.php?msg=27437#27437)
Thanks,
Markus