atmaps
June 20th, 2016, 02:23 PM
Hi folks! I'm moving with my problem to this forum now, as I couldn't get any help elsewhere so far ...
I'm using Xubuntu 16.04 on an Acer TravelMate B116-M with an SSD (Samsung EVO 850) as its main HDD. The laptop is fully Linux-compatible, I've thoroughly checked it during an earlier install. Btw, I'm pretty sure the problem is not Xubuntu-specific, so I didn't tag the thread with "Xubuntu" ...
Having this problem now: after re-installing Xubuntu on my laptop, GRUB will start with a CLI-interface! The screen will look like this:
GNU GRUB version 2.02~beta2-36ubuntu3
Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions.
grub> _
After first thinking "WTF?", I entered "exit". Startup continued, but quite strangely. I'm not using "quiet splash", so I'm getting all that ... how do you call it? Status messages? But at first, they're totally unreadable, they just look like blocks, not letters. After a few seconds they suddenly become readable (system changing to better screen resolution?), and I have to enter my passphrase (encrypted system, see background info).
The system then starts quite normal, and I can see that the installation seems to be OK - everything works just as it was supposed to.
Background info: I've installed a fully encrypted system as follows: unencrypted /boot (ext4), then an encrypted LUKS-LVM volume with /swap, /(root) and /home partitions. I'm giving you the link to the "cooking recipe" for that install here (https://wiki.ubuntuusers.de/System_verschl%C3%BCsseln/), but it's all in German, so you might not profit from that ... Suffice to say that I used that install once and it worked just perfect, out of the box - until my root file system got corrupted . If you can read it (or get something out of Mr Google's translation (https://translate.google.de/translate?sl=de&tl=en&js=y&prev=_t&hl=de&ie=UTF-8&u=https%3A%2F%2Fwiki.ubuntuusers.de%2FSystem_versc hl%25C3%25BCsseln%2F&edit-text=&act=url)), let me add that I deviated from that recipe only in one point: not installing root and home integrally (one partition), but in two separate partitions. After I had been hit by the afore mentioned file system corruption I thought that might be a good idea: I'd fully install the system, then dd (http://pubs.opengroup.org/onlinepubs/9699919799/utilities/dd.html) the whole root partition, and if sh... happens again, I'd just re-dd that copy, and problem solved ...
I've already tried GRUB repair once, but it just bricked the system - no GRUB startup any more! I then re-installed, same problem, and I'm now asking you. Thanks for your help in advance!
And here some info to give you an idea about my system. I hope if I'm doing it so thoroughly, you will say: oh, that guy is so nice, let's just help him ;-) However, some of that output is in German, which pi... me off, too, but I can't help it for now. But maybe Linux itself is a language universal enough ... There you go:
uname -a; lsb_release -a
Linux [[computer_name]] 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04 LTS
Release: 16.04
Codename: xenial
sudo parted -l
Modell: ATA Samsung SSD 850 (scsi)
Festplatte /dev/sda: 500GB
Sektorgröße (logisch/physisch): 512B/512B
Partitionstabelle: gpt
Disk-Flags:
Nummer Anfang Ende Größe Dateisystem Name Flags
1 1049kB 538MB 537MB fat32 EFI System Partition boot, esp
2 539MB 1902MB 1363MB ext4 /boot
3 1902MB 446GB 445GB
Modell: TOSHIBA TransMemory (scsi)
Festplatte /dev/sdb: 7759MB
Sektorgröße (logisch/physisch): 512B/512B
Partitionstabelle: msdos
Disk-Flags:
Nummer Anfang Ende Größe Typ Dateisystem Flags
1 1049kB 5348MB 5347MB primary fat32 boot, LBA
2 5348MB 7759MB 2412MB primary ext4
Modell: Linux device-mapper (linear) (dm)
Festplatte /dev/mapper/vgubuntu-home: 410GB
Sektorgröße (logisch/physisch): 512B/512B
Partitionstabelle: loop
Disk-Flags:
Nummer Anfang Ende Größe Dateisystem Flags
1 0,00B 410GB 410GB ext4
Modell: Linux device-mapper (linear) (dm)
Festplatte /dev/mapper/vgubuntu-root: 21,5GB
Sektorgröße (logisch/physisch): 512B/512B
Partitionstabelle: loop
Disk-Flags:
Nummer Anfang Ende Größe Dateisystem Flags
1 0,00B 21,5GB 21,5GB ext4
Modell: Linux device-mapper (linear) (dm)
Festplatte /dev/mapper/vgubuntu-swap: 12,9GB
Sektorgröße (logisch/physisch): 512B/512B
Partitionstabelle: loop
Disk-Flags:
Nummer Anfang Ende Größe Dateisystem Flags
1 0,00B 12,9GB 12,9GB linux-swap(v1)
Fehler: /dev/mapper/lukslvm: unbekannte Partitionstabelle
Modell: Linux device-mapper (crypt) (dm)
Festplatte /dev/mapper/lukslvm: 445GB
Sektorgröße (logisch/physisch): 512B/512B
Partitionstabelle: unknown
Disk-Flags:
sudo lsblk -o NAME,UUID,FSTYPE,SIZE,LABEL,MOUNTPOINT
NAME UUID FSTYPE SIZE LABEL MOUNTPOINT
sda 465,8G
├─sda1 69D1-DAA7 vfat 512M
├─sda2 e126b9ec-4f9c-40af-a3b3-c6212b38f049 ext4 1,3G /boot
└─sda3 f5a136aa-f614-4fad-91dd-17e9fec5dfcf crypto_LUKS 414G
└─lukslvm 39iTvW-Wd72-Vqi3-IZn0-zWf4-H9d9-m9JMGl LVM2_member 414G
├─vgubuntu-swap 05b0c138-3288-46d0-b963-ffb8e7ea40d5 swap 12G [SWAP]
├─vgubuntu-root eda5f2b6-5f60-4d05-ac64-ba33bd01f364 ext4 20G /
└─vgubuntu-home 9eb8ca14-ec50-427b-9d76-b786f9373d19 ext4 382G /home
sdb 7,2G
├─sdb1 3F70-4520 vfat 5G /media/[[user_name]]/3F70-4520
└─sdb2 7d9520c8-db1f-4ce1-9f51-2daaecc3d5e1 ext4 2,3G /media/[[user_name]]/7d9520c8-db1f-4ce1-9f51-2daaecc3d5e1
cat /etc/fstab
# /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>
/dev/mapper/vgubuntu-root / ext4 errors=remount-ro 0 1
# /boot was on /dev/sda2 during installation
UUID=e126b9ec-4f9c-40af-a3b3-c6212b38f049 /boot ext4 defaults 0 2
/dev/mapper/vgubuntu-home /home ext4 defaults 0 2
/dev/mapper/vgubuntu-swap none swap sw 0 0
sudo pvs
PV VG Fmt Attr PSize PFree
/dev/mapper/lukslvm vgubuntu lvm2 a-- 413,98g 0
cat /etc/crypttab
lukslvm UUID=f5a136aa-f614-4fad-91dd-17e9fec5dfcf none luks
[[user_name]]@[[computer_name]]:~$ ls -la /dev/mapper/
insgesamt 0
drwxr-xr-x 2 root root 140 Jun 19 18:05 .
drwxr-xr-x 22 root root 4680 Jun 19 18:33 ..
crw------- 1 root root 10, 236 Jun 19 18:05 control
lrwxrwxrwx 1 root root 7 Jun 19 18:34 lukslvm -> ../dm-0
lrwxrwxrwx 1 root root 7 Jun 19 18:34 vgubuntu-home -> ../dm-3
lrwxrwxrwx 1 root root 7 Jun 19 18:34 vgubuntu-root -> ../dm-2
lrwxrwxrwx 1 root root 7 Jun 19 18:34 vgubuntu-swap -> ../dm-1
And at this point I tried to give you the output of cat /var/log/syslog for reboot -> startup -> system up & running (in a code block), but that was probably too much text so I couldn't post the whole thing. If you need it, please give me a hint on how to post it here.
I'm using Xubuntu 16.04 on an Acer TravelMate B116-M with an SSD (Samsung EVO 850) as its main HDD. The laptop is fully Linux-compatible, I've thoroughly checked it during an earlier install. Btw, I'm pretty sure the problem is not Xubuntu-specific, so I didn't tag the thread with "Xubuntu" ...
Having this problem now: after re-installing Xubuntu on my laptop, GRUB will start with a CLI-interface! The screen will look like this:
GNU GRUB version 2.02~beta2-36ubuntu3
Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions.
grub> _
After first thinking "WTF?", I entered "exit". Startup continued, but quite strangely. I'm not using "quiet splash", so I'm getting all that ... how do you call it? Status messages? But at first, they're totally unreadable, they just look like blocks, not letters. After a few seconds they suddenly become readable (system changing to better screen resolution?), and I have to enter my passphrase (encrypted system, see background info).
The system then starts quite normal, and I can see that the installation seems to be OK - everything works just as it was supposed to.
Background info: I've installed a fully encrypted system as follows: unencrypted /boot (ext4), then an encrypted LUKS-LVM volume with /swap, /(root) and /home partitions. I'm giving you the link to the "cooking recipe" for that install here (https://wiki.ubuntuusers.de/System_verschl%C3%BCsseln/), but it's all in German, so you might not profit from that ... Suffice to say that I used that install once and it worked just perfect, out of the box - until my root file system got corrupted . If you can read it (or get something out of Mr Google's translation (https://translate.google.de/translate?sl=de&tl=en&js=y&prev=_t&hl=de&ie=UTF-8&u=https%3A%2F%2Fwiki.ubuntuusers.de%2FSystem_versc hl%25C3%25BCsseln%2F&edit-text=&act=url)), let me add that I deviated from that recipe only in one point: not installing root and home integrally (one partition), but in two separate partitions. After I had been hit by the afore mentioned file system corruption I thought that might be a good idea: I'd fully install the system, then dd (http://pubs.opengroup.org/onlinepubs/9699919799/utilities/dd.html) the whole root partition, and if sh... happens again, I'd just re-dd that copy, and problem solved ...
I've already tried GRUB repair once, but it just bricked the system - no GRUB startup any more! I then re-installed, same problem, and I'm now asking you. Thanks for your help in advance!
And here some info to give you an idea about my system. I hope if I'm doing it so thoroughly, you will say: oh, that guy is so nice, let's just help him ;-) However, some of that output is in German, which pi... me off, too, but I can't help it for now. But maybe Linux itself is a language universal enough ... There you go:
uname -a; lsb_release -a
Linux [[computer_name]] 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04 LTS
Release: 16.04
Codename: xenial
sudo parted -l
Modell: ATA Samsung SSD 850 (scsi)
Festplatte /dev/sda: 500GB
Sektorgröße (logisch/physisch): 512B/512B
Partitionstabelle: gpt
Disk-Flags:
Nummer Anfang Ende Größe Dateisystem Name Flags
1 1049kB 538MB 537MB fat32 EFI System Partition boot, esp
2 539MB 1902MB 1363MB ext4 /boot
3 1902MB 446GB 445GB
Modell: TOSHIBA TransMemory (scsi)
Festplatte /dev/sdb: 7759MB
Sektorgröße (logisch/physisch): 512B/512B
Partitionstabelle: msdos
Disk-Flags:
Nummer Anfang Ende Größe Typ Dateisystem Flags
1 1049kB 5348MB 5347MB primary fat32 boot, LBA
2 5348MB 7759MB 2412MB primary ext4
Modell: Linux device-mapper (linear) (dm)
Festplatte /dev/mapper/vgubuntu-home: 410GB
Sektorgröße (logisch/physisch): 512B/512B
Partitionstabelle: loop
Disk-Flags:
Nummer Anfang Ende Größe Dateisystem Flags
1 0,00B 410GB 410GB ext4
Modell: Linux device-mapper (linear) (dm)
Festplatte /dev/mapper/vgubuntu-root: 21,5GB
Sektorgröße (logisch/physisch): 512B/512B
Partitionstabelle: loop
Disk-Flags:
Nummer Anfang Ende Größe Dateisystem Flags
1 0,00B 21,5GB 21,5GB ext4
Modell: Linux device-mapper (linear) (dm)
Festplatte /dev/mapper/vgubuntu-swap: 12,9GB
Sektorgröße (logisch/physisch): 512B/512B
Partitionstabelle: loop
Disk-Flags:
Nummer Anfang Ende Größe Dateisystem Flags
1 0,00B 12,9GB 12,9GB linux-swap(v1)
Fehler: /dev/mapper/lukslvm: unbekannte Partitionstabelle
Modell: Linux device-mapper (crypt) (dm)
Festplatte /dev/mapper/lukslvm: 445GB
Sektorgröße (logisch/physisch): 512B/512B
Partitionstabelle: unknown
Disk-Flags:
sudo lsblk -o NAME,UUID,FSTYPE,SIZE,LABEL,MOUNTPOINT
NAME UUID FSTYPE SIZE LABEL MOUNTPOINT
sda 465,8G
├─sda1 69D1-DAA7 vfat 512M
├─sda2 e126b9ec-4f9c-40af-a3b3-c6212b38f049 ext4 1,3G /boot
└─sda3 f5a136aa-f614-4fad-91dd-17e9fec5dfcf crypto_LUKS 414G
└─lukslvm 39iTvW-Wd72-Vqi3-IZn0-zWf4-H9d9-m9JMGl LVM2_member 414G
├─vgubuntu-swap 05b0c138-3288-46d0-b963-ffb8e7ea40d5 swap 12G [SWAP]
├─vgubuntu-root eda5f2b6-5f60-4d05-ac64-ba33bd01f364 ext4 20G /
└─vgubuntu-home 9eb8ca14-ec50-427b-9d76-b786f9373d19 ext4 382G /home
sdb 7,2G
├─sdb1 3F70-4520 vfat 5G /media/[[user_name]]/3F70-4520
└─sdb2 7d9520c8-db1f-4ce1-9f51-2daaecc3d5e1 ext4 2,3G /media/[[user_name]]/7d9520c8-db1f-4ce1-9f51-2daaecc3d5e1
cat /etc/fstab
# /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>
/dev/mapper/vgubuntu-root / ext4 errors=remount-ro 0 1
# /boot was on /dev/sda2 during installation
UUID=e126b9ec-4f9c-40af-a3b3-c6212b38f049 /boot ext4 defaults 0 2
/dev/mapper/vgubuntu-home /home ext4 defaults 0 2
/dev/mapper/vgubuntu-swap none swap sw 0 0
sudo pvs
PV VG Fmt Attr PSize PFree
/dev/mapper/lukslvm vgubuntu lvm2 a-- 413,98g 0
cat /etc/crypttab
lukslvm UUID=f5a136aa-f614-4fad-91dd-17e9fec5dfcf none luks
[[user_name]]@[[computer_name]]:~$ ls -la /dev/mapper/
insgesamt 0
drwxr-xr-x 2 root root 140 Jun 19 18:05 .
drwxr-xr-x 22 root root 4680 Jun 19 18:33 ..
crw------- 1 root root 10, 236 Jun 19 18:05 control
lrwxrwxrwx 1 root root 7 Jun 19 18:34 lukslvm -> ../dm-0
lrwxrwxrwx 1 root root 7 Jun 19 18:34 vgubuntu-home -> ../dm-3
lrwxrwxrwx 1 root root 7 Jun 19 18:34 vgubuntu-root -> ../dm-2
lrwxrwxrwx 1 root root 7 Jun 19 18:34 vgubuntu-swap -> ../dm-1
And at this point I tried to give you the output of cat /var/log/syslog for reboot -> startup -> system up & running (in a code block), but that was probably too much text so I couldn't post the whole thing. If you need it, please give me a hint on how to post it here.