sasha15 | I am working on Devuan Chimaera and I have installed it by : | 00:52 |
---|---|---|
sasha15 | pip install cassowary | 00:52 |
sasha15 | Launch cassowary configuration utility with: | 00:52 |
sasha15 | $ python3 -m cassowary -a | 00:52 |
sasha15 | But after that I received: | 00:52 |
sasha15 | What to do? | 00:52 |
sasha15 | I am working on Devuan Chimaera and I have installed it by : | 00:53 |
sasha15 | pip install cassowary | 00:53 |
sasha15 | Launch cassowary configuration utility with: | 00:53 |
sasha15 | $ python3 -m cassowary -a | 00:53 |
sasha15 | But after that I received: | 00:53 |
sasha15 | What to do? | 00:53 |
sasha15 | No module named cassowary.__main__; 'cassowary' is a package and cannot be directly executed | 00:54 |
onefang | Is cassowary an Aussie emu-lator? | 00:55 |
onefang | I'll get my coat. | 00:55 |
sasha15 | yep | 00:55 |
sasha15 | https://github.com/casualsnek/cassowary/blob/main/docs/2-cassowary-install.md | 00:56 |
sasha15 | i installed all but cant launch config | 00:58 |
gnarface | related to the packages python3-kiwisolver or librust-cassowary-dev? | 00:59 |
sasha15 | python3 | 01:00 |
sasha15 | Help me please. | 01:09 |
gnarface | sasha15: seems like you need python support unless it's just that you're missing the python3-kiwisolver .deb, that's my only guess | 01:12 |
sasha15 | So this means that I need to reinstall python ? python kiwisolver was installed | 01:23 |
gnarface | i don't think it means you need to reinstall python, but i don't know | 01:24 |
gnarface | it looks like there's a mistake in the code but i don't know python | 01:24 |
gnarface | you should ask in python's irc channel | 01:24 |
gnarface | but you should stay connected here in case someone comes back later who knows | 01:24 |
sasha15 | Ok. Installed casowary once again: pip install cassowary | 01:27 |
sasha15 | Requirement already satisfied: cassowary in /usr/local/lib/python3.9/dist-packages (0.5.2). But cant to launch it. | 01:27 |
systemdlete | I've done it again. Sheesh! | 01:33 |
systemdlete | I have destroyed my chimaera partition. I was trying to rename the raid device and screwed things up. I believe I clobbered it. | 01:33 |
systemdlete | I am wondering, can the original content on that device be recovered and made good again? Or am I S.O.L. | 01:34 |
systemdlete | (not a big deal, really. All I had on it was a minimal system, enough to run vbox. VMs are on other partitions) | 01:34 |
systemdlete | probably faster to stop crying about it and just re-do it. But before spending all that effort (and time), maybe there is a way to get my raid back, as it was. | 01:35 |
systemdlete | I even have backups, so it shouldn't be too painful if I do need to rebuild the partition. | 01:36 |
systemdlete | I can't believe I did that. I didn't even think to copy the partition before I started... doh! | 01:37 |
systemdlete | (I guess you could say systemdlete has deleted his system) | 01:43 |
DashiePie | you're just living up to your name | 02:23 |
DashiePie | what a chad | 02:23 |
gnarface | systemdlete: i thought there was some sort of mdraid repair tool but i don't know if it would help | 03:12 |
Ankokukishi | hello everyone. I have an issue that i cant figure out how to fix | 03:15 |
Ankokukishi | https://dpaste.org/knC6G | 03:16 |
Ankokukishi | for some reason my initramfs-tools is not responding | 03:16 |
Ankokukishi | ive tried --configure and -update-initramfs gives me an error that the command doesnt exist | 03:17 |
Ankokukishi | but if i try to install initramfs-tools, it says its installed | 03:17 |
Ankokukishi | im using refracta 10, but my repos are set to unstable | 03:19 |
rrq | is /boot large enough? | 03:20 |
gnarface | Ankokukishi: well, "-update-initramfs" isn't a command, it's actually "update-initramfs" but assuming that's what you meant to type, it's worth noting some jackass took /usr/sbin and /sbin out of root's default path upstream, so you'd actually have to call it as /usr/sbin/update-initramfs now, or add /usr/sbin back to root's path. i'm just guessing at the issue though... if you want me to actually look at that error use paste.debian.net or /msg it to | 03:21 |
Ankokukishi | yes i have my boot and home on two different drives | 03:21 |
gnarface | me directly here | 03:21 |
Ankokukishi | gnarface: yeah i meant to say update-initramfs | 03:23 |
rrq | it as a -v option .. might tell more | 03:23 |
Ankokukishi | says update-initramfs is not a command | 03:24 |
rrq | what's your $PATH? | 03:24 |
Ankokukishi | how do i check that? | 03:24 |
rrq | echo $PATH | 03:24 |
Ankokukishi | https://dpaste.org/Ew3o4 | 03:25 |
gnarface | you don't have to use a pastebin for one-line pastes | 03:27 |
gnarface | if you want to paste something that starts with a "/" precede it with a empty space | 03:27 |
Ankokukishi | okay | 03:27 |
Ankokukishi | i noticed theres no path to usr/sbin and /sbin | 03:28 |
gnarface | yep, that's probably why it says it's not there | 03:28 |
Ankokukishi | i mena /usr/sbin | 03:28 |
rrq | and it's nor root's path is it? | 03:28 |
gnarface | it's defined in /etc/login.defs | 03:29 |
Ankokukishi | lemme look in my root directory real fast | 03:29 |
gnarface | ENV_SUPATH | 03:29 |
gnarface | ^ look for this string | 03:30 |
fsmithred | did you use 'su' or 'su - ' to become root? | 03:30 |
rrq | be root, then make sure /usr/sbin is in PATH, then use update-initramfs | 03:30 |
gnarface | yea it won't work unless you're root even if it is in your path, to be clear | 03:30 |
fsmithred | actually, it shouldn't matter if you're using refracta, because I already fixed it. | 03:30 |
gnarface | oh, good to know | 03:30 |
fsmithred | that change happened about five seconds after I found it. | 03:31 |
Ankokukishi | but when i try to update, it gives me this error | 03:32 |
Ankokukishi | https://dpaste.org/zOGte | 03:32 |
fsmithred | I don't really understand the error. What was the command you ran? | 03:33 |
Ankokukishi | sudo apt upgrade | 03:33 |
Ankokukishi | Sub-process /usr/bin/dpkg returned an error code (1) | 03:35 |
fsmithred | you're using 5.17 kernel in beowulf? | 03:35 |
Ankokukishi | im in ceres | 03:35 |
fsmithred | oh, I thought you said refracta-10 | 03:35 |
fsmithred | which is beowulf | 03:35 |
Ankokukishi | originally installed beowulf | 03:36 |
fsmithred | ok | 03:36 |
Ankokukishi | then switched to unstable | 03:36 |
fsmithred | could be temporary breakage | 03:36 |
rrq | first problem is with /usr/share/initramfs-tools/hooks/live | 03:36 |
Ankokukishi | rrq: whats happening there? | 03:38 |
rrq | add "set -x" to it | 03:38 |
Ankokukishi | oh take off the x | 03:39 |
fsmithred | I don't think that script should do anything if you're not in a live session | 03:41 |
Ankokukishi | that fixed it | 03:41 |
fsmithred | what did you do? | 03:41 |
Ankokukishi | what rrq said | 03:42 |
fsmithred | what you think he said | 03:42 |
Ankokukishi | -x to the hooks/live file | 03:42 |
fsmithred | did you edit the contents of the file, or did you change the permissions on the file? | 03:42 |
Ankokukishi | just made it not executable | 03:42 |
Ankokukishi | chmod | 03:43 |
fsmithred | that's not what he suggested | 03:43 |
Ankokukishi | o9h | 03:43 |
fsmithred | if you look inside that file, about the third line down, you'll see 'set -e' | 03:43 |
rrq | mmm but it made the script execution align to your expecttion I suppose :) | 03:43 |
fsmithred | rrq was suggesting that you add 'set -x' to the file. That will make it spit out more information. | 03:43 |
Ankokukishi | oof. now i gotta make it executable again | 03:44 |
rrq | yes my idea was to get some details about where it failed | 03:45 |
Ankokukishi | oof now i cant set it back to executable for some reason | 03:47 |
rrq | but, if this is not to be a live system, then removing live-boot might be a solution as well | 03:47 |
Ankokukishi | how do i put it back to executable? just so it gets back to what i had before. It wont let me use chmod for some reason | 03:48 |
rrq | as root | 03:49 |
Ankokukishi | i did sudo chmod | 03:49 |
rrq | sudo chmod a+x /usr/share/initramfs-tools/hooks/live ? | 03:50 |
Ankokukishi | okay that worked | 03:51 |
Ankokukishi | and i also changed -e to -x | 03:51 |
fsmithred | well, now it won't bail out if there are errors | 03:51 |
rrq | better to make it both "-e -x" | 03:51 |
fsmithred | I think you want both | 03:52 |
rrq | the "-e" makes the script exit with failure on first error | 03:52 |
Ankokukishi | the error is gone now | 03:52 |
rrq | the "-x" makes it print the commands before executing them | 03:52 |
rrq | by remivng "-e" you made the script ignore its problem | 03:53 |
Ankokukishi | i put the -e back and added -x | 03:53 |
fsmithred | or it got installed when that script was non-executable | 03:53 |
fsmithred | you were getting that error on upgrade, right? | 03:54 |
Ankokukishi | yeah | 03:55 |
Ankokukishi | and i just ran it again | 03:55 |
Ankokukishi | and the error is gone | 03:55 |
fsmithred | and is initramfs-tools gone from the list of packages to be upgraded? | 03:55 |
Ankokukishi | yeah | 03:55 |
fsmithred | looks like I upgraded that package about a week ago. I didn't run into a problem. | 03:57 |
fsmithred | on daedalus | 03:57 |
Ankokukishi | hmmm i wonder if i may have done something when messing around in virtualbox | 03:58 |
Ankokukishi | and that may have messed up something | 03:58 |
Ankokukishi | still learning my way around vb | 03:58 |
fsmithred | error was in the host system or in the VM? | 03:58 |
Ankokukishi | host system | 03:59 |
systemdlete | gnarface: Are you referring to test-disk or testdisk? That's included in systemrescuecd, so I might try that. It claims to be able to recover lost raid info. | 09:03 |
systemdlete | hmmm. testdisk is available in the devuan repos... | 09:07 |
gnarface | systemdlete: i don't remember specifically sorry, i actually had the vague notion it had "mdraid" in the actual name | 09:35 |
gnarface | maybe it was just something you could do with mdadm | 09:37 |
systemdlete | I ran testdisk and came up with little. | 09:42 |
systemdlete | I think when the new raid device was created, it overwrote the raid superblocks. So whatever was there is probably gone now is what I am thinking. | 09:43 |
systemdlete | I did not follow the instructions for renaming raid device quite right. I should have written those down on a spare scrap --there's no shortage of throwaway mailers here, but I thought I could remember what I was doing. | 09:44 |
systemdlete | bad on me, that's all | 09:44 |
gnarface | does this help at all? https://www.woktron.com/secure/knowledgebase/196/How-to-recover-from-a-broken-RAID-array-with-MDADM.html | 09:45 |
systemdlete | the issue is not with the raid itself, but with the fs that was on it. The raid starts, but it cannot be mounted because the fs info is gone or damaged | 09:50 |
systemdlete | so the raid itself does not need recovery; it is the file system that was on it | 09:50 |
systemdlete | that needs recovery | 09:50 |
systemdlete | thanks for your help again | 09:52 |
systemdlete | I think I just dug a deep one for myself, that's all | 09:53 |
systemdlete | btw, hasn't mdraid been sort of defecated these days? | 09:54 |
gnarface | dunno honestly | 11:03 |
gnarface | i thought it was still what is used for software raid | 11:04 |
gnarface | i could be wrong | 11:04 |
systemdlete | I have been using mdadm for years. I was told long ago that mdraid was no longer preferred. | 12:00 |
gnarface | oh i see. i probably meant mdadm when i typed mdraid | 12:04 |
gnarface | i thought they were the same thing | 12:04 |
gnarface | but then again, maybe i remembered right and that's why you didn't see anything obvious with mdadm | 12:05 |
systemdlete | ok, off to start over again... | 12:20 |
systemdlete | bbl | 12:20 |
systemdlete | fsmithred: I am trying a refracta install of chimaera. When I get to the phase where it asks for the installation device, it does not list my (pre-existing) raid partition. In a shell, I can see the raid device is there and running. Maybe I have just forgotten what to do at this point. | 13:06 |
systemdlete | The listing of all the devices does show the desired partition I want, but the selection choices don't; it only shows individual /dev/xxx devices. | 13:07 |
fsmithred | systemdlete, you need to use the cli installer, not the gui | 13:18 |
fsmithred | and then you type in the device name | 13:19 |
fsmithred | https://dev1galaxy.org/viewtopic.php?pid=11437#p11437 | 13:21 |
systemdlete | what is the name of the cli installer? Is it refracta-cli? | 14:58 |
fsmithred | refractainstaller -d | 14:58 |
systemdlete | aha. | 14:58 |
systemdlete | ok, thanks | 14:58 |
fsmithred | (please use the debug option as shown) | 14:58 |
systemdlete | debug option? | 14:58 |
fsmithred | you'll get garbage output on the screen, but if there are problems, you'll have something to read. | 14:59 |
fsmithred | yeah, -d | 14:59 |
systemdlete | oh | 14:59 |
fsmithred | it enables 'set -x' | 14:59 |
systemdlete | got it | 14:59 |
fsmithred | so all the commands get duplicated on screen. I'm used to it and don't notice. | 14:59 |
systemdlete | any plans for a fix to the gui installer? | 14:59 |
fsmithred | not for that ability | 15:00 |
systemdlete | which ability? The one that would allow me to choose a pre-existing RAID? | 15:01 |
fsmithred | would have to change the way it sorts the partitions. | 15:01 |
fsmithred | yeah | 15:01 |
systemdlete | I'd be happy just to see it at all... | 15:01 |
fsmithred | I need to overhaul the installer some time | 15:01 |
systemdlete | I don't remember this issue when I installed refracta on my other box. It is true I had to shell out to set up the raid, but once I did that, I was able to select it. That is, iirc, which maybe I don't | 15:03 |
fsmithred | nope. | 15:04 |
systemdlete | I don't remember using the command line installer, but maybe I did. That was a few weeks ago. | 15:04 |
systemdlete | (memory is failing me a lot more than usual lately) | 15:04 |
systemdlete | bbl... | 15:05 |
fsmithred | install_dev=$(find /dev -mindepth 1 -maxdepth 1 | egrep "*[shv]d[a-z][1-99]|*nvme[0-9]n[0-9]p[1-99]|*mmcblk[0-9]p[1-99]" | 15:08 |
fsmithred | oops. | 15:09 |
fsmithred | I had a question. | 15:09 |
fsmithred | I know what a raid device name looks like, but can there be multiple partitions inside it without using lvm? | 15:11 |
djph | sure | 15:11 |
fsmithred | or would /dev/md0 be used as a single partition | 15:11 |
fsmithred | so what do the partition names look like? | 15:11 |
djph | no, md0 is hte mdadm-exposed block device | 15:11 |
fsmithred | ok | 15:11 |
djph | I'd expect it to be /dev/md0p1 or something like that | 15:12 |
fsmithred | I can do that | 15:12 |
djph | ... although I usually do hardware raid ... | 15:12 |
fsmithred | bbl | 15:15 |
djph | take care :) | 15:16 |
fsmithred | systemdlete, I think I have a fix for you | 18:28 |
systemdlete | fsmithred: ? | 20:04 |
systemdlete | you have an extra brain you can lend me for a while? | 20:05 |
fsmithred | not long | 20:05 |
systemdlete | (mine's not working too well. I just made another error... different one this time) | 20:05 |
fsmithred | what device names do your partitions get? | 20:05 |
systemdlete | uh... it varies, unfortunately | 20:05 |
fsmithred | something like /dev/md0p1 could work | 20:05 |
fsmithred | would be a simple edit in the gui installer script | 20:06 |
systemdlete | well, this system seems to like /dev/md125, /dev/md126, etc. Of course, I have my own names in /dev/md, but those are the ones that are inconsistently named | 20:06 |
systemdlete | fsmithred: I am actually ok with it as is. | 20:07 |
systemdlete | This is not one of my test boxes, so... | 20:07 |
fsmithred | ok. Did you see the line I posted just before you left? | 20:07 |
fsmithred | oh, don't mess around. | 20:07 |
systemdlete | the only message I see from you is "systemdlete, I think I have a fix for you" | 20:07 |
fsmithred | yeah, that was when you returned | 20:08 |
fsmithred | pm ok? | 20:08 |
systemdlete | no, I did not see any other messages. | 20:08 |
systemdlete | Sure pm is fine | 20:08 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!