specing | before I nuke the broken VM... is there a way for apt to repair damaged rootfs? | 01:10 |
---|---|---|
specing | i.e. does it know checksums of everything that was installed and can it re-check and reinstall? | 01:11 |
furrywolf | I've seen a utility that can do that, but it was for detecting maliciously modified files. | 01:13 |
watchcat | tripwire | 01:16 |
specing | Well, well, well | 01:21 |
specing | this is interesting | 01:21 |
specing | I unmounted the VM's filesystem from the host | 01:21 |
specing | booted the VM again, ran btrfs scrub inside VM and it comes back clean. No errors | 01:21 |
specing | and it is the same 4.9.x kernel series on both host and VM | 01:21 |
specing | ?_? | 01:21 |
specing | I'll have a chat with btrfs devs | 01:21 |
fsmithred | specing, you want debsums | 01:33 |
gnarface | specing: is it possible the volume came up for auto-fsck on boot at one point and the script just failed? the scripts for reiserfs and xfs had been recently broken due to some boneheaded systemd related change. mabye the btrfs one got the same treatment? | 06:00 |
gnarface | anyway, that could explain it in theory anyway | 06:01 |
gnarface | (the fix for reiserfs was to delete it and just replace the symlink that was there before) | 06:02 |
va7lnx | hi gnarface | 06:22 |
gnarface | sorry, va7lnx, i had wandered away | 07:45 |
straube | Hi all... someone know something about problem with bridge.ko? | 19:08 |
straube | I have problem with lxc-net | 19:08 |
straube | when I launch I have this answer: [....] Starting LXC network bridge: :RTNETLINK answers: Operation not supported | 19:09 |
straube | Failed to setup lxc-net. And if I try to do modprobe bridge I have this answer: modprobe: ERROR: could not insert 'bridge': Unknown symbol in module, or unknown parameter (see dmesg) | 19:09 |
straube | This problem is same in two different server after upgrade modprobe: ERROR: could not insert 'bridge': Unknown symbol in module, or unknown parameter (see dmesg) | 20:47 |
helios21 | straube: did you actually look in dmesg as the error message told you to do? | 20:54 |
straube | of course, but dmseg do not show any message | 20:54 |
straube | I mean, anyone related | 20:56 |
helios21 | hmmm… that is strange | 21:09 |
va7lnx | gnarface: I wandered to bed :P | 23:11 |
gnarface | how's it all working for you now va7lnx? | 23:12 |
gnarface | i forget what your setup was, but i trust it's all ironed out now? | 23:12 |
va7lnx | I have most of it worked out. | 23:17 |
va7lnx | I can't seem to mount my android phone though | 23:17 |
va7lnx | I can use bluetooth, so I'm not SOL | 23:17 |
gnarface | hmmm | 23:18 |
va7lnx | this computer is barely being used now. between Devuan's light footprint and the much better motherboard, I rarely break 25% RAM | 23:18 |
va7lnx | I guess I'll play with VMs :) | 23:19 |
gnarface | sometimes phones need to be manually switched to some sort of "mass storage mode" to be mountable. often they will come with windows tools that can do that somehow from the client side, but on linux you'll have to edit the phone's config first afaik | 23:19 |
va7lnx | yes. I did this, but it won't mount. | 23:19 |
va7lnx | not sure why. It's not really important. As I said, I can use bluetooth connectivity. | 23:19 |
gnarface | hmm. what error does it give you? it could be a permissions problem too | 23:19 |
va7lnx | but I would like it if I could mount over USB | 23:19 |
gnarface | yea bluetooth is really slow | 23:19 |
gnarface | and the tools are usually crippled | 23:19 |
gnarface | usb mounts might not work but usually they do if the phone has a mass storage mode | 23:20 |
va7lnx | no error. | 23:20 |
gnarface | hmm | 23:20 |
va7lnx | it's weird. | 23:21 |
gnarface | you sure it didn't mount? | 23:21 |
va7lnx | I don't think it even tried quite frankly | 23:21 |
gnarface | usually silence is the expected output of a successful call to the mount command. it might look like it didn't try | 23:21 |
gnarface | if you run dmesg before and after plugging it in, the new lines added to the output should shed some light on the subject | 23:21 |
watchcat | if the phone is rooted and android, you can use 'ums enabler' to get mass storage mode | 23:22 |
gnarface | there's also the very real possibility that you don't have the right filesystem driver loaded, but i would expect a specific error about that | 23:22 |
va7lnx | that is possible. | 23:23 |
va7lnx | yeah, there's no "errors" | 23:23 |
va7lnx | [1346758.021083] usb 4-1.2: new high-speed USB device number 21 using ehci-pci | 23:23 |
va7lnx | [1346758.135332] usb 4-1.2: New USB device found, idVendor=04e8, idProduct=6860 | 23:23 |
va7lnx | [1346758.135343] usb 4-1.2: New USB device strings: Mfr=2, Product=3, SerialNumber=4 | 23:23 |
va7lnx | [1346758.135345] usb 4-1.2: Product: SAMSUNG_Android | 23:23 |
va7lnx | [1346758.135347] usb 4-1.2: Manufacturer: SAMSUNG | 23:23 |
va7lnx | [1346758.135348] usb 4-1.2: SerialNumber: 988678445752583937 | 23:23 |
va7lnx | [1346767.270467] usb 4-1.2: USB disconnect, device number 21 | 23:23 |
va7lnx | [1346767.493019] usb 4-1.2: new high-speed USB device number 22 using ehci-pci | 23:23 |
va7lnx | [1346767.603309] usb 4-1.2: New USB device found, idVendor=04e8, idProduct=6860 | 23:23 |
va7lnx | [1346767.603312] usb 4-1.2: New USB device strings: Mfr=2, Product=3, SerialNumber=4 | 23:23 |
va7lnx | [1346767.603314] usb 4-1.2: Product: SAMSUNG_Android | 23:23 |
va7lnx | [1346767.603315] usb 4-1.2: Manufacturer: SAMSUNG | 23:23 |
gnarface | yikes, use paste.debian.net for big pastes like that. you risk getting auto-kicked by security | 23:24 |
va7lnx | yeah. I just got a warning | 23:24 |
va7lnx | anyhow. | 23:24 |
gnarface | that looks like normal output from a phone being plugged in, unplugged, then part of the output of it being plugged in again | 23:25 |
va7lnx | probably when I switched modes | 23:26 |
gnarface | it's not an unrecognized device | 23:26 |
va7lnx | maybe I need to apt-cache search for mtp | 23:26 |
KatolaZ | va7lnx: is that a phone? | 23:27 |
gnarface | oh, that sounds familiar. yea some phones might need mtp or something like that | 23:27 |
KatolaZ | (sorry not looking at the backlog) | 23:27 |
va7lnx | KatolaZ: yes. android lineage | 23:27 |
va7lnx | that's okay | 23:27 |
KatolaZ | jmtpf | 23:27 |
KatolaZ | jmtpfs | 23:27 |
KatolaZ | (to access it as a storage device) | 23:27 |
va7lnx | that's what I'm thinking | 23:28 |
KatolaZ | don't think, just do it ;) | 23:28 |
va7lnx | do I need to restart anything when I install it? | 23:28 |
KatolaZ | nope | 23:28 |
KatolaZ | you need to run the command from cli | 23:29 |
va7lnx | ah. okay. | 23:31 |
va7lnx | sweet! there it is! | 23:31 |
va7lnx | now to get it to do it automagically | 23:31 |
va7lnx | mounted it under my home directory too | 23:32 |
KatolaZ | va7lnx: there was a trick with a udev rule | 23:34 |
KatolaZ | never used it though | 23:34 |
KatolaZ | I guess the more phone-savvies here might have a hint | 23:34 |
va7lnx | yeah. I'll have a look at that. at least I can do it manually | 23:34 |
KatolaZ | yep | 23:35 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!