search for: cryptroot

Hi! I've written an article on setting up cryptroot on CentOS: http://www.msquared.id.au/articles/cryptroot I'd like to create links to it from a few places in the wiki. For example: * http://wiki.centos.org/HowTos Create a 'security' heading and link to either my article or a page on the wiki that links to my article...

...have=2075122916315869932 Check tree block failed, want=4268204032, have=2075122916315869932 read block failed check_tree_block gandalfthegreat:~# btrfs-zero-log /dev/mapper/root gandalfthegreat:~# Full kernel debug info: [ 3829.908692] device label btrfs_pool2 devid 1 transid 66367 /dev/mapper/cryptroot [ 3964.563483] device label btrfs_pool1 devid 1 transid 305644 /dev/mapper/root [ 3964.564164] btrfs: enabling auto recovery [ 3964.564172] btrfs: disk space caching is enabled [ 3964.728275] Btrfs detected SSD devices, enabling SSD mode [ 3964.728509] btrfs bad tree block start 2075122916315869932...

Im new to the list and CentOS and wonder if there is any option to do full disk encryption with dmcrypt and LUKS during the install stage of CentOS 5.1? I use Debian Etch at the moment and Debian is able to to this. If not possible, are there any good guides that anyone knows about that explain how to dmcrypt everything but /boot on CentOS manually? --andrew -- GnuPG Key ID: ECB18ABA

I asked the debian maintainer to add btrfs-zero-log to the initramfs since I unfortunately have to use it from time to time. It still fixes the problem for me when btrfs won''t mount, but it errors at the end. See screenshot Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems ....

...: uninitialized urandom read (4 bytes read) [ 144.793573] e1000e 0000:00:1f.6 eth0: NIC Link is Down [ 159.627780] random: crng init done [ 171.814064] process '/usr/bin/fstype' started with executable stack [ 181.949989] BTRFS: device label btrfs_boot devid 1 transid 394687 /dev/mapper/cryptroot scanned by btrfs (1063) [ 181.953437] BTRFS: device label btrfs_pool4 devid 1 transid 78270 /dev/sdb4 scanned by btrfs (1063) [ 181.956989] BTRFS: device label btrfs_pool3 devid 1 transid 27410 /dev/sda5 scanned by btrfs (1063) [ 181.960473] BTRFS: device fsid de9694f8-9c0d-4e9d-bd12-57adc4381cd...

...afterwards to maintain write speed when I''m using the laptop after the copy and reboot". Now, I rebooted with the new ssd and zlib compressed rootfs, and it seemed to boot slower than it did before with the same root files on btrfs lzo. My mount options are back to lzo: /dev/mapper/cryptroot / btrfs rw,noatime,compress=lzo,nossd,discard,space_cache 0 0 Is my feeling of slower boot wrong, or is zlib also noticeably slower than lzo to read and decompress? And separately, back a while ago, I read in multiple places that ''nossd'' actually worked better than ''ssd...

Is this useful to anyone? Got this after a crash/reboot: if (block_rsv) { WARN_ON(block_rsv->size > 0); <<<<<<<<<<<<<<<<<<<<<< btrfs_free_block_rsv(root, block_rsv); } ------------[ cut here ]------------ WARNING: at fs/btrfs/inode.c:2165 btrfs_orphan_commit_root+0xcb/0xdf() Hardware name: 2429A78 Modules linked in:

...dom read (4 bytes read) > [ 144.793573] e1000e 0000:00:1f.6 eth0: NIC Link is Down > [ 159.627780] random: crng init done > [ 171.814064] process '/usr/bin/fstype' started with executable stack > [ 181.949989] BTRFS: device label btrfs_boot devid 1 transid 394687 /dev/mapper/cryptroot scanned by btrfs (1063) > [ 181.953437] BTRFS: device label btrfs_pool4 devid 1 transid 78270 /dev/sdb4 scanned by btrfs (1063) > [ 181.956989] BTRFS: device label btrfs_pool3 devid 1 transid 27410 /dev/sda5 scanned by btrfs (1063) > [ 181.960473] BTRFS: device fsid de9694f8-9c0d-4e9d-b...

...ubsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Linux version 3.4.4-amd64-preempt-noide-20120410 (root@gandalfthegreat) (gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP PREEMPT Sun Jun 24 15:32:40 PDT 2012 [ 0.000000] Command line: BOOT_IMAGE=linux344x64 ro root=/dev/mapper/cryptroot panic=20 resume=/dev/sdb3 usbcore.autosuspend=1 i915.modeset=1 pcie_aspm=force rootflags=subvol=backuproot cryptopts=source=/dev/sdb4,keyscript=/sbin/cryptgetpw [ 0.000000] BIOS-provided physical RAM map: [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009d800 (usable) [ 0.000000] BIO...

On Tue, Sep 08, 2020 at 01:51:19AM +0200, Karol Herbst wrote: > oh, I somehow missed that "disp ctor failed" message. I think that > might explain why things are a bit hanging. From the top of my head I > am not sure if that's something known or something new. But just in > case I CCed Lyude and Ben. And I think booting with > nouveau.debug=disp=trace could already

Ok, I have an update to this problem. I added the nouveau list because I can't quite tell if the issue is: - the PCIe changes that went in 5.6 I think (or 5.5?), referenced below - a new issue with thunderbold on thinkpad P73, that seems to be triggered if I have a USB-C yubikey in the port. With 5.7, my issues went away if I removed the USB key during boot, showing an interaction