Reputation
Top tag
Next privilege 200 Rep.
See reduced ads
Badges
6
Impact
~3k people reached

  • 0 posts edited
  • 0 helpful flags
  • 4 votes cast
May
26
accepted how does Thunar generate thumbnails?
May
25
asked how does Thunar generate thumbnails?
Apr
19
accepted I can read from hard disk, but I can't mount it read only
Apr
19
revised I can read from hard disk, but I can't mount it read only
fixed device name
Apr
18
asked I can read from hard disk, but I can't mount it read only
Jan
1
asked bootup hangs on “started monitoring of lvm2 mirrors”
Dec
13
awarded  Popular Question
Jul
21
awarded  Popular Question
Jan
21
accepted after replacing motherboard, Debian gets blank screen while booting
Jan
21
answered after replacing motherboard, Debian gets blank screen while booting
Jan
5
comment after replacing motherboard, Debian gets blank screen while booting
Debian, which I have on hard disk, uses 3.0.2 kernel while Knoppix, which I use now, uses 3.6.11 kernel. Isn't it a problem? Will everything work fine if I use 3.6.11 kernel when I create initrd to be used by 3.0.2 kernel?
Jan
5
revised after replacing motherboard, Debian gets blank screen while booting
more details
Jan
5
asked after replacing motherboard, Debian gets blank screen while booting
Dec
29
awarded  Supporter
Dec
23
revised after adding one more physical volume and enlarging logical volume, grub fails
improved final solution
Dec
23
awarded  Editor
Dec
23
revised after adding one more physical volume and enlarging logical volume, grub fails
final solution
Dec
18
accepted after adding one more physical volume and enlarging logical volume, grub fails
Dec
18
comment after adding one more physical volume and enlarging logical volume, grub fails
Your diagnosis may be right, because the uuid "EFc551-(...)" really is the uuid of the encrypted PV on my new partition. Which, by the way (maybe somebody else will have similar problem), I found out by first decrypting it with "cryptsetup luksOpen /dev/sda3 test3" and then doing "pvdisplay".
Dec
18
comment after adding one more physical volume and enlarging logical volume, grub fails
I don't think this is the reason of my problems. My boot partition doesn't have /etc/fstab, initrd which is inside it doesn't have it. And I guess that the /etc/fstab which is on logical volume isn't the cause of problem, because during boot this logical volume isn't activated yet while the error message is shown.