| 31 May 2023 |
 ElvishJerricco | * systemctl show -p After --no-pager -l zfs-import-POOL.service? | 22:26:21 |
 Copa Dium | look good so far | 22:30:53 |
| Copa Dium | no timeout after 4 minute wait, i think this means it works | 22:32:08 |
| Copa Dium | Thank you! | 22:32:14 |
| ElvishJerricco | nice | 22:32:14 |
 @lily:lily.flowers | In reply to @elvishjerricco:matrix.org
in fact, when I finally decided to enter the passphrase, the little "waiting for..." message about the mapper device showed up for a second, saying it had been waiting for 9mins, so that definitely doesn't time out :P Yeah it still timed out for me. I'll see if I can find out why | 22:42:19 |
| @lily:lily.flowers | dev-nixos-root.device is what is timing out for me (trimmed snippet of relevant journal log section):
May 31 18:41:16 localhost systemd[1]: dev-nixos-root.device: Job dev-nixos-root.device/start timed out.
May 31 18:41:16 localhost systemd[1]: Timed out waiting for device /dev/nixos/root.
May 31 18:41:16 localhost systemd[1]: Dependency failed for /sysroot/nix.
May 31 18:41:16 localhost systemd[1]: Dependency failed for Initrd File Systems.
May 31 18:41:16 localhost systemd[1]: initrd-fs.target: Job initrd-fs.target/start failed with result 'dependency'.
May 31 18:41:16 localhost systemd[1]: initrd-fs.target: Triggering OnFailure= dependencies.
May 31 18:41:16 localhost systemd[1]: sysroot-nix.mount: Job sysroot-nix.mount/start failed with result 'dependency'.
May 31 18:41:16 localhost systemd[1]: Dependency failed for /sysroot/state.
May 31 18:41:16 localhost systemd[1]: Dependency failed for /sysroot/var/log.
May 31 18:41:16 localhost systemd[1]: sysroot-var-log.mount: Job sysroot-var-log.mount/start failed with result 'dependency'.
May 31 18:41:16 localhost systemd[1]: sysroot-state.mount: Job sysroot-state.mount/start failed with result 'dependency'.
May 31 18:41:16 localhost systemd[1]: Dependency failed for Initrd Root Device.
May 31 18:41:16 localhost systemd[1]: Dependency failed for Rolling over and creating new filesystem root.
May 31 18:41:16 localhost systemd[1]: Dependency failed for Initrd Root File System.
May 31 18:41:16 localhost systemd[1]: Dependency failed for Mountpoints Configured in the Real Root.
May 31 18:41:16 localhost systemd[1]: initrd-parse-etc.service: Job initrd-parse-etc.service/start failed with result 'dependency'.
May 31 18:41:16 localhost systemd[1]: initrd-parse-etc.service: Triggering OnFailure= dependencies.
May 31 18:41:16 localhost systemd[1]: initrd-root-fs.target: Job initrd-root-fs.target/start failed with result 'dependency'.
May 31 18:41:16 localhost systemd[1]: initrd-root-fs.target: Triggering OnFailure= dependencies.
May 31 18:41:16 localhost systemd[1]: create-root.service: Job create-root.service/start failed with result 'dependency'.
May 31 18:41:16 localhost systemd[1]: initrd-root-device.target: Job initrd-root-device.target/start failed with result 'dependency'.
May 31 18:41:16 localhost systemd[1]: initrd-root-device.target: Triggering OnFailure= dependencies.
May 31 18:41:16 localhost systemd[1]: Dependency failed for /sysroot.
May 31 18:41:16 localhost systemd[1]: Dependency failed for /sysroot/persist.
May 31 18:41:16 localhost systemd[1]: sysroot-persist.mount: Job sysroot-persist.mount/start failed with result 'dependency'.
May 31 18:41:16 localhost systemd[1]: sysroot.mount: Job sysroot.mount/start failed with result 'dependency'.
May 31 18:41:16 localhost systemd[1]: dev-nixos-root.device: Job dev-nixos-root.device/start failed with result 'timeout'.
May 31 18:41:16 localhost systemd[1]: panic-on-fail.service was skipped because no trigger condition checks were met.
May 31 18:41:16 localhost systemd[1]: Stopping Dispatch Password Requests to Console...
May 31 18:41:16 localhost systemd[1]: systemd-ask-password-console.service: Deactivated successfully.
May 31 18:41:16 localhost systemd[1]: Stopped Dispatch Password Requests to Console.
May 31 18:41:16 localhost systemd[1]: systemd-ask-password-console.path: Deactivated successfully.
May 31 18:41:16 localhost systemd[1]: Stopped Dispatch Password Requests to Console Directory Watch.
May 31 18:41:16 localhost systemd[1]: Started Emergency Shell.
May 31 18:41:16 localhost systemd[1]: Reached target Emergency Mode.
| 22:44:07 |
| @lily:lily.flowers | If I don't enter password after 1.5 minutes | 22:44:16 |
| @lily:lily.flowers | Or whatever the timeout is | 22:44:21 |
| @lily:lily.flowers | If it helps ElvishJerricco, here's json of my config evaluated for boot.initrd.luks.devices:
{
"nixos": {
"allowDiscards": false,
"bypassWorkqueues": false,
"crypttabExtraOpts": [],
"device": "/dev/nvme0n1p2",
"fallbackToPassword": false,
"fido2": {
"credential": null,
"credentials": [],
"gracePeriod": 10,
"passwordLess": false
},
"gpgCard": null,
"header": null,
"keyFile": null,
"keyFileOffset": null,
"keyFileSize": null,
"keyFileTimeout": null,
"name": "nixos",
"postOpenCommands": "",
"preLVM": true,
"preOpenCommands": "",
"tryEmptyPassphrase": false,
"yubikey": null
}
}
And evaluated fileSystems with x-initrd.mount:
{
"/": {
"autoFormat": false,
"autoResize": false,
"depends": [],
"device": "/dev/nixos/root",
"encrypted": {
"blkDev": null,
"enable": false,
"keyFile": null,
"label": null
},
"formatOptions": "",
"fsType": "btrfs",
"label": null,
"mountPoint": "/",
"neededForBoot": false,
"noCheck": false,
"options": [
"x-initrd.mount",
"defaults",
"subvol=/root"
],
"stratis": {
"poolUuid": null
}
},
"/nix": {
"autoFormat": false,
"autoResize": false,
"depends": [],
"device": "/dev/nixos/root",
"encrypted": {
"blkDev": null,
"enable": false,
"keyFile": null,
"label": null
},
"formatOptions": "",
"fsType": "btrfs",
"label": null,
"mountPoint": "/nix",
"neededForBoot": false,
"noCheck": false,
"options": [
"x-initrd.mount",
"defaults",
"subvol=/nix"
],
"stratis": {
"poolUuid": null
}
},
"/persist": {
"autoFormat": false,
"autoResize": false,
"depends": [],
"device": "/dev/nixos/root",
"encrypted": {
"blkDev": null,
"enable": false,
"keyFile": null,
"label": null
},
"formatOptions": "",
"fsType": "btrfs",
"label": null,
"mountPoint": "/persist",
"neededForBoot": true,
"noCheck": false,
"options": [
"x-initrd.mount",
"defaults",
"subvol=/persist"
],
"stratis": {
"poolUuid": null
}
},
"/state": {
"autoFormat": false,
"autoResize": false,
"depends": [],
"device": "/dev/nixos/root",
"encrypted": {
"blkDev": null,
"enable": false,
"keyFile": null,
"label": null
},
"formatOptions": "",
"fsType": "btrfs",
"label": null,
"mountPoint": "/state",
"neededForBoot": true,
"noCheck": false,
"options": [
"x-initrd.mount",
"defaults",
"subvol=/state"
],
"stratis": {
"poolUuid": null
}
}
}
| 22:53:29 |
| @lily:lily.flowers | * If it helps ElvishJerricco, here's json of my config evaluated for boot.initrd.luks.devices:
{
"nixos": {
"allowDiscards": false,
"bypassWorkqueues": false,
"crypttabExtraOpts": [],
"device": "/dev/nvme0n1p2",
"fallbackToPassword": false,
"fido2": {
"credential": null,
"credentials": [],
"gracePeriod": 10,
"passwordLess": false
},
"gpgCard": null,
"header": null,
"keyFile": null,
"keyFileOffset": null,
"keyFileSize": null,
"keyFileTimeout": null,
"name": "nixos",
"postOpenCommands": "",
"preLVM": true,
"preOpenCommands": "",
"tryEmptyPassphrase": false,
"yubikey": null
}
}
And evaluated fileSystems with x-initrd.mount:
{
"/": {
"autoFormat": false,
"autoResize": false,
"depends": [],
"device": "/dev/nixos/root",
"encrypted": {
"blkDev": null,
"enable": false,
"keyFile": null,
"label": null
},
"formatOptions": "",
"fsType": "btrfs",
"label": null,
"mountPoint": "/",
"neededForBoot": false,
"noCheck": false,
"options": [
"x-initrd.mount",
"defaults",
"subvol=/root"
],
"stratis": {
"poolUuid": null
}
},
"/nix": {
"autoFormat": false,
"autoResize": false,
"depends": [],
"device": "/dev/nixos/root",
"encrypted": {
"blkDev": null,
"enable": false,
"keyFile": null,
"label": null
},
"formatOptions": "",
"fsType": "btrfs",
"label": null,
"mountPoint": "/nix",
"neededForBoot": false,
"noCheck": false,
"options": [
"x-initrd.mount",
"defaults",
"subvol=/nix"
],
"stratis": {
"poolUuid": null
}
},
"/persist": {
"autoFormat": false,
"autoResize": false,
"depends": [],
"device": "/dev/nixos/root",
"encrypted": {
"blkDev": null,
"enable": false,
"keyFile": null,
"label": null
},
"formatOptions": "",
"fsType": "btrfs",
"label": null,
"mountPoint": "/persist",
"neededForBoot": true,
"noCheck": false,
"options": [
"x-initrd.mount",
"defaults",
"subvol=/persist"
],
"stratis": {
"poolUuid": null
}
},
"/state": {
"autoFormat": false,
"autoResize": false,
"depends": [],
"device": "/dev/nixos/root",
"encrypted": {
"blkDev": null,
"enable": false,
"keyFile": null,
"label": null
},
"formatOptions": "",
"fsType": "btrfs",
"label": null,
"mountPoint": "/state",
"neededForBoot": true,
"noCheck": false,
"options": [
"x-initrd.mount",
"defaults",
"subvol=/state"
],
"stratis": {
"poolUuid": null
}
},
"/var/log": {
"autoFormat": false,
"autoResize": false,
"depends": [
"/state"
],
"device": "/state/var/log",
"encrypted": {
"blkDev": null,
"enable": false,
"keyFile": null,
"label": null
},
"formatOptions": "",
"fsType": "auto",
"label": null,
"mountPoint": "/var/log",
"neededForBoot": false,
"noCheck": true,
"options": [
"x-initrd.mount",
"bind",
"x-gvfs-hide"
],
"stratis": {
"poolUuid": null
}
}
}
| 22:59:26 |
 Charles ⚡️ | Should I be concerned if I see "Stopping Rule-based Manager for Device Events and Files" take upwards of 15 seconds on startup? Maybe relevant section of journalctl --boot=0 logs:
May 31 16:31:54 compy systemd[1]: Stopping Rule-based Manager for Device Events and Files...
May 31 16:31:54 compy systemd[1]: initrd-cleanup.service: Deactivated successfully.
May 31 16:31:54 compy systemd[1]: Finished Cleaning Up and Shutting Down Daemons.
May 31 16:31:54 compy systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dsetup.service.mount: Deactivated successfully.
May 31 16:31:54 compy systemd[1]: run-credentials-systemd\x2dsysctl.service.mount: Deactivated successfully.
May 31 16:31:55 compy kernel: usb 3-2: New USB device found, idVendor=046d, idProduct=085c, bcdDevice= 0.16
May 31 16:31:55 compy kernel: usb 3-2: New USB device strings: Mfr=0, Product=2, SerialNumber=1
May 31 16:31:55 compy kernel: usb 3-2: Product: C922 Pro Stream Webcam
May 31 16:31:55 compy kernel: usb 3-2: SerialNumber: 4A6771BF
May 31 16:31:55 compy kernel: usb 1-6: New USB device found, idVendor=0b05, idProduct=1a5c, bcdDevice= 0.02
May 31 16:31:55 compy kernel: usb 1-6: New USB device strings: Mfr=3, Product=1, SerialNumber=0
May 31 16:31:55 compy kernel: usb 1-6: Product: USB Audio
May 31 16:31:55 compy kernel: usb 1-6: Manufacturer: Generic
May 31 16:31:56 compy kernel: hid-generic 0003:0B05:1A5C.0009: hiddev101,hidraw8: USB HID v1.11 Device [Generic USB Audio] on usb-0000:0c:00.0-6/input7
May 31 16:31:56 compy kernel: usb 1-7: new full-speed USB device number 4 using xhci_hcd
May 31 16:31:56 compy kernel: usb 1-7: config 1 has an invalid interface number: 2 but max is 1
May 31 16:31:56 compy kernel: usb 1-7: config 1 has no interface number 1
May 31 16:31:56 compy kernel: usb 1-7: New USB device found, idVendor=0b05, idProduct=19af, bcdDevice= 1.00
May 31 16:31:56 compy kernel: usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
May 31 16:31:56 compy kernel: usb 1-7: Product: AURA LED Controller
May 31 16:31:56 compy kernel: usb 1-7: Manufacturer: AsusTek Computer Inc.
May 31 16:31:56 compy kernel: usb 1-7: SerialNumber: 9876543210
May 31 16:31:56 compy kernel: hid-generic 0003:0B05:19AF.000A: hiddev102,hidraw9: USB HID v1.11 Device [AsusTek Computer Inc. AURA LED Controller] on usb-0000:0c:00.0-7/input2
May 31 16:31:56 compy kernel: usb 1-11: new high-speed USB device number 5 using xhci_hcd
May 31 16:32:02 compy kernel: usb 1-11: device descriptor read/64, error -110
May 31 16:32:18 compy kernel: usb 1-11: device descriptor read/64, error -110
May 31 16:32:18 compy kernel: usb 1-11: new high-speed USB device number 6 using xhci_hcd
May 31 16:32:23 compy kernel: usb 1-11: device descriptor read/64, error -110
May 31 16:32:39 compy kernel: usb 1-11: device descriptor read/64, error -110
May 31 16:32:39 compy kernel: usb usb1-port11: attempt power cycle
May 31 16:32:40 compy kernel: usb 1-11: new high-speed USB device number 7 using xhci_hcd
May 31 16:32:45 compy kernel: usb 1-11: Device not responding to setup address.
May 31 16:32:50 compy kernel: usb 1-11: Device not responding to setup address.
May 31 16:32:50 compy kernel: usb 1-11: device not accepting address 7, error -71
May 31 16:32:50 compy kernel: usb 1-11: new high-speed USB device number 8 using xhci_hcd
May 31 16:32:55 compy systemd-udevd[292]: usb1: Worker [394] processing SEQNUM=2289 is taking a long time
May 31 16:32:55 compy kernel: usb 1-11: Device not responding to setup address.
May 31 16:33:00 compy kernel: usb 1-11: Device not responding to setup address.
May 31 16:33:00 compy kernel: usb 1-11: device not accepting address 8, error -71
May 31 16:33:00 compy kernel: usb usb1-port11: unable to enumerate USB device
May 31 16:33:00 compy systemd[1]: systemd-udevd.service: Deactivated successfully.
May 31 16:33:00 compy systemd[1]: Stopped Rule-based Manager for Device Events and Files.
I see the "Stopping" and "Stopped" timestamps are within 6 seconds of each other, but I swear I see the little moving red *s for substantially longer than that on startup
| 23:36:28 |
| Charles ⚡️ | $ nixos-version --json
{"configurationRevision":"7d39cad56d1a2126a606a74d47ba4a823fb4c144","nixosVersion":"23.11.20230523.d30264c","nixpkgsRevision":"d30264c2691128adc261d7c9388033645f0e742b"}
| 23:37:27 |
| Charles ⚡️ | * Should I be concerned if I see "Stopping Rule-based Manager for Device Events and Files" take upwards of 15 seconds on startup? Maybe relevant section of journalctl --boot=0 logs:
May 31 16:31:54 compy systemd[1]: Stopping Rule-based Manager for Device Events and Files...
May 31 16:31:54 compy systemd[1]: initrd-cleanup.service: Deactivated successfully.
May 31 16:31:54 compy systemd[1]: Finished Cleaning Up and Shutting Down Daemons.
May 31 16:31:54 compy systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dsetup.service.mount: Deactivated successfully.
May 31 16:31:54 compy systemd[1]: run-credentials-systemd\x2dsysctl.service.mount: Deactivated successfully.
May 31 16:31:55 compy kernel: usb 3-2: New USB device found, idVendor=046d, idProduct=085c, bcdDevice= 0.16
May 31 16:31:55 compy kernel: usb 3-2: New USB device strings: Mfr=0, Product=2, SerialNumber=1
May 31 16:31:55 compy kernel: usb 3-2: Product: C922 Pro Stream Webcam
May 31 16:31:55 compy kernel: usb 3-2: SerialNumber: 4A6771BF
May 31 16:31:55 compy kernel: usb 1-6: New USB device found, idVendor=0b05, idProduct=1a5c, bcdDevice= 0.02
May 31 16:31:55 compy kernel: usb 1-6: New USB device strings: Mfr=3, Product=1, SerialNumber=0
May 31 16:31:55 compy kernel: usb 1-6: Product: USB Audio
May 31 16:31:55 compy kernel: usb 1-6: Manufacturer: Generic
May 31 16:31:56 compy kernel: hid-generic 0003:0B05:1A5C.0009: hiddev101,hidraw8: USB HID v1.11 Device [Generic USB Audio] on usb-0000:0c:00.0-6/input7
May 31 16:31:56 compy kernel: usb 1-7: new full-speed USB device number 4 using xhci_hcd
May 31 16:31:56 compy kernel: usb 1-7: config 1 has an invalid interface number: 2 but max is 1
May 31 16:31:56 compy kernel: usb 1-7: config 1 has no interface number 1
May 31 16:31:56 compy kernel: usb 1-7: New USB device found, idVendor=0b05, idProduct=19af, bcdDevice= 1.00
May 31 16:31:56 compy kernel: usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
May 31 16:31:56 compy kernel: usb 1-7: Product: AURA LED Controller
May 31 16:31:56 compy kernel: usb 1-7: Manufacturer: AsusTek Computer Inc.
May 31 16:31:56 compy kernel: usb 1-7: SerialNumber: 9876543210
May 31 16:31:56 compy kernel: hid-generic 0003:0B05:19AF.000A: hiddev102,hidraw9: USB HID v1.11 Device [AsusTek Computer Inc. AURA LED Controller] on usb-0000:0c:00.0-7/input2
May 31 16:31:56 compy kernel: usb 1-11: new high-speed USB device number 5 using xhci_hcd
May 31 16:32:02 compy kernel: usb 1-11: device descriptor read/64, error -110
May 31 16:32:18 compy kernel: usb 1-11: device descriptor read/64, error -110
May 31 16:32:18 compy kernel: usb 1-11: new high-speed USB device number 6 using xhci_hcd
May 31 16:32:23 compy kernel: usb 1-11: device descriptor read/64, error -110
May 31 16:32:39 compy kernel: usb 1-11: device descriptor read/64, error -110
May 31 16:32:39 compy kernel: usb usb1-port11: attempt power cycle
May 31 16:32:40 compy kernel: usb 1-11: new high-speed USB device number 7 using xhci_hcd
May 31 16:32:45 compy kernel: usb 1-11: Device not responding to setup address.
May 31 16:32:50 compy kernel: usb 1-11: Device not responding to setup address.
May 31 16:32:50 compy kernel: usb 1-11: device not accepting address 7, error -71
May 31 16:32:50 compy kernel: usb 1-11: new high-speed USB device number 8 using xhci_hcd
May 31 16:32:55 compy systemd-udevd[292]: usb1: Worker [394] processing SEQNUM=2289 is taking a long time
May 31 16:32:55 compy kernel: usb 1-11: Device not responding to setup address.
May 31 16:33:00 compy kernel: usb 1-11: Device not responding to setup address.
May 31 16:33:00 compy kernel: usb 1-11: device not accepting address 8, error -71
May 31 16:33:00 compy kernel: usb usb1-port11: unable to enumerate USB device
May 31 16:33:00 compy systemd[1]: systemd-udevd.service: Deactivated successfully.
May 31 16:33:00 compy systemd[1]: Stopped Rule-based Manager for Device Events and Files.
I see the "Stopping" and "Stopped" timestamps are within 6 seconds of each other, but I swear I see the little moving red *s for substantially longer than that on startup I can't read the difference is 6 seconds plus 1 minute
| 23:44:27 |
| Charles ⚡️ | * Should I be concerned if I see "Stopping Rule-based Manager for Device Events and Files" take upwards of 15 seconds on startup? Maybe relevant section of journalctl --boot=0 logs:
May 31 16:31:54 compy systemd[1]: Stopping Rule-based Manager for Device Events and Files...
May 31 16:31:54 compy systemd[1]: initrd-cleanup.service: Deactivated successfully.
May 31 16:31:54 compy systemd[1]: Finished Cleaning Up and Shutting Down Daemons.
May 31 16:31:54 compy systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dsetup.service.mount: Deactivated successfully.
May 31 16:31:54 compy systemd[1]: run-credentials-systemd\x2dsysctl.service.mount: Deactivated successfully.
May 31 16:31:55 compy kernel: usb 3-2: New USB device found, idVendor=046d, idProduct=085c, bcdDevice= 0.16
May 31 16:31:55 compy kernel: usb 3-2: New USB device strings: Mfr=0, Product=2, SerialNumber=1
May 31 16:31:55 compy kernel: usb 3-2: Product: C922 Pro Stream Webcam
May 31 16:31:55 compy kernel: usb 3-2: SerialNumber: 4A6771BF
May 31 16:31:55 compy kernel: usb 1-6: New USB device found, idVendor=0b05, idProduct=1a5c, bcdDevice= 0.02
May 31 16:31:55 compy kernel: usb 1-6: New USB device strings: Mfr=3, Product=1, SerialNumber=0
May 31 16:31:55 compy kernel: usb 1-6: Product: USB Audio
May 31 16:31:55 compy kernel: usb 1-6: Manufacturer: Generic
May 31 16:31:56 compy kernel: hid-generic 0003:0B05:1A5C.0009: hiddev101,hidraw8: USB HID v1.11 Device [Generic USB Audio] on usb-0000:0c:00.0-6/input7
May 31 16:31:56 compy kernel: usb 1-7: new full-speed USB device number 4 using xhci_hcd
May 31 16:31:56 compy kernel: usb 1-7: config 1 has an invalid interface number: 2 but max is 1
May 31 16:31:56 compy kernel: usb 1-7: config 1 has no interface number 1
May 31 16:31:56 compy kernel: usb 1-7: New USB device found, idVendor=0b05, idProduct=19af, bcdDevice= 1.00
May 31 16:31:56 compy kernel: usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
May 31 16:31:56 compy kernel: usb 1-7: Product: AURA LED Controller
May 31 16:31:56 compy kernel: usb 1-7: Manufacturer: AsusTek Computer Inc.
May 31 16:31:56 compy kernel: usb 1-7: SerialNumber: 9876543210
May 31 16:31:56 compy kernel: hid-generic 0003:0B05:19AF.000A: hiddev102,hidraw9: USB HID v1.11 Device [AsusTek Computer Inc. AURA LED Controller] on usb-0000:0c:00.0-7/input2
May 31 16:31:56 compy kernel: usb 1-11: new high-speed USB device number 5 using xhci_hcd
May 31 16:32:02 compy kernel: usb 1-11: device descriptor read/64, error -110
May 31 16:32:18 compy kernel: usb 1-11: device descriptor read/64, error -110
May 31 16:32:18 compy kernel: usb 1-11: new high-speed USB device number 6 using xhci_hcd
May 31 16:32:23 compy kernel: usb 1-11: device descriptor read/64, error -110
May 31 16:32:39 compy kernel: usb 1-11: device descriptor read/64, error -110
May 31 16:32:39 compy kernel: usb usb1-port11: attempt power cycle
May 31 16:32:40 compy kernel: usb 1-11: new high-speed USB device number 7 using xhci_hcd
May 31 16:32:45 compy kernel: usb 1-11: Device not responding to setup address.
May 31 16:32:50 compy kernel: usb 1-11: Device not responding to setup address.
May 31 16:32:50 compy kernel: usb 1-11: device not accepting address 7, error -71
May 31 16:32:50 compy kernel: usb 1-11: new high-speed USB device number 8 using xhci_hcd
May 31 16:32:55 compy systemd-udevd[292]: usb1: Worker [394] processing SEQNUM=2289 is taking a long time
May 31 16:32:55 compy kernel: usb 1-11: Device not responding to setup address.
May 31 16:33:00 compy kernel: usb 1-11: Device not responding to setup address.
May 31 16:33:00 compy kernel: usb 1-11: device not accepting address 8, error -71
May 31 16:33:00 compy kernel: usb usb1-port11: unable to enumerate USB device
May 31 16:33:00 compy systemd[1]: systemd-udevd.service: Deactivated successfully.
May 31 16:33:00 compy systemd[1]: Stopped Rule-based Manager for Device Events and Files.
I see the "Stopping" and "Stopped" timestamps are within 6 seconds of each other, but I swear I see the little moving red *s for substantially longer than that on startup I can't read, the difference is 6 seconds plus 1 minute
| 23:44:38 |
| Charles ⚡️ | Still happens if I remove all my USB devices, and seems to be consistently 66 +/- 1 seconds | 23:49:38 |
| 1 Jun 2023 |
| ElvishJerricco | Lily Foster: What creates /dev/nixos/root? | 00:00:25 |
| ElvishJerricco | That's not a normal path for a LUKS device | 00:00:30 |
| ElvishJerricco | Charles ⚡️: that's... interesting. I have no idea what that means | 00:01:23 |
| Charles ⚡️ | cool lol | 00:01:35 |
| Charles ⚡️ | i'm running a few-days-old nixpkgs so i'll try updating and see if it goes away | 00:01:48 |
| Charles ⚡️ | but this wasn't happening in association with another upgrade or bios change or anything | 00:02:07 |
| Charles ⚡️ | it just kinda started happening | 00:02:10 |
| Charles ⚡️ | same behavior after updating | 00:11:54 |
| @lily:lily.flowers | In reply to @elvishjerricco:matrix.org
That's not a normal path for a LUKS device It's an LVM inside LUKS. Which was maybe not my best idea and I now realize is probably related to why I'm encountering timeouts | 00:23:42 |
| ElvishJerricco | Lily Foster: Oh, no that seems entirely reasonable. I still don't understand why that would lead to timeouts though... | 00:24:38 |
| @lily:lily.flowers | See disko here: https://github.com/lilyinstarlight/foosteros/blob/ab117ba2dd69d77fffc6384c1ace1f3227221490/hosts/bina/disks.nix | 00:24:53 |
| @lily:lily.flowers | For disk layout | 00:24:57 |
| ElvishJerricco | so as for the ISO stuff I wanted to look into this week, turns out we do something really kinda weird? | 02:35:08 |
| ElvishJerricco | We use root= on the cmdline for... /iso, not / | 02:36:23 |
