| conifer | gnarface: I didn't manage to make firetools work, but thank you for your assistance! | 01:17 |
|---|---|---|
| conifer | I'm still a bit baffled why is "su -" preferred, it seems to make other things break | 01:20 |
| conifer | anyway, thanks once again, fsmithred & gnarface! | 01:22 |
| fsmithred | conifer, there's some info in the release notes about su | 01:22 |
| fsmithred | if you add that line I suggested, it will act like it used to | 01:23 |
| fsmithred | echo 'ALWAYS_SET_PATH yes' >> /etc/default/su | 01:23 |
| conifer | I mean, I find having it keep the user's path useful most of the time | 01:23 |
| fsmithred | see 'man su' | 01:23 |
| fsmithred | you need games for root? | 01:23 |
| fsmithred | I like getting root's path without changing directory | 01:24 |
| conifer | and with su - e.g. synaptic don't run | 01:24 |
| fsmithred | and occasionally I want to run a graphical app as root | 01:24 |
| fsmithred | so I just use 'su' like I have been for a long time | 01:24 |
| conifer | I don't need root for games, mostly chown or chmod on files I copied from pen-drive etc. | 01:26 |
| fsmithred | those aren't in any sbin, so either way to get su should work | 01:27 |
| fsmithred | but for commands in /sbin /usr/sbin or /usr/local/sbin you need to use 'su -' or do something else to fix root's path. | 01:28 |
| fsmithred | either the line I suggested or export the full path from root's .bashrc | 01:28 |
| conifer | so if I set the ALWAYS_SET_PATH then both su and su - act the same way/ | 01:29 |
| conifer | ? | 01:29 |
| fsmithred | both will give you root's path | 01:29 |
| fsmithred | PATH | 01:29 |
| conifer | ok | 01:29 |
| fsmithred | but 'su -' will change directory to /root | 01:29 |
| fsmithred | just su will keep you in whatever directory you're in | 01:30 |
| conifer | I think I'd rather have an option to choose one or the other | 01:30 |
| fsmithred | choose one of the other of what? | 01:30 |
| conifer | user or root path | 01:30 |
| fsmithred | what's in the user's path that you need? | 01:31 |
| conifer | just convenience of usually working on files in user dir | 01:31 |
| fsmithred | you get that with su | 01:32 |
| fsmithred | don't change directory | 01:32 |
| fsmithred | echo $PATH | 01:32 |
| fsmithred | do that as user, and as root both ways | 01:32 |
| fsmithred | and note the differences | 01:33 |
| fsmithred | the PATH variable is the path the shell takes to find any commands you run | 01:33 |
| fsmithred | pwd | 01:34 |
| fsmithred | that's the command to Print Working Directory | 01:34 |
| fsmithred | it'll tell you where you are | 01:34 |
| fsmithred | I think maybe you were confusing those | 01:35 |
| conifer | I can see user has games in $PATH and not has sbins | 01:36 |
| conifer | but for both su and su - it looks the same | 01:37 |
| fsmithred | yeah, you need the sbins to do certain things | 01:37 |
| fsmithred | oh, you added the line in /etc/default/su? | 01:37 |
| conifer | I don't even have this file, but now you made me wonder if I haven't fixed it somewhere in the past | 01:38 |
| fsmithred | look in /root/.bashrc | 01:39 |
| fsmithred | export PATH=whatever... | 01:39 |
| conifer | yes, it's there | 01:41 |
| conifer | is this fine or not recommended? | 01:41 |
| fsmithred | it's ok. I've done it like that before I knew about /etc/default/su | 01:42 |
| fsmithred | ok, this current system I'm on is like that, and it's my main system | 01:42 |
| fsmithred | works for me just like debian has worked for the last 12 years | 01:43 |
| fsmithred | (and devuan for the last 5) | 01:43 |
| conifer | anyway, when I do su - I can't run synaptic, while with su it runs | 01:45 |
| fsmithred | right, because su - gives you root's environment, which doesn't include user's desktop | 01:46 |
| fsmithred | depending on what's installed, you might be able to run synaptic-pkexec as user | 01:47 |
| fsmithred | did you do a full desktop install, or something lightweight? | 01:47 |
| conifer | it says "Probably you're running Synaptic on Wayland with root permission" - is this a generic error message? | 01:49 |
| fsmithred | I've seen that one | 01:49 |
| conifer | I'm not even sure I was using wayland | 01:49 |
| fsmithred | you're probably not | 01:49 |
| fsmithred | again, what did you install? | 01:50 |
| fsmithred | xfce? jwm? | 01:50 |
| conifer | yoe, a full install I guess | 01:50 |
| fsmithred | ok | 01:50 |
| fsmithred | you tried synaptic-pkexec as user, right? Not root. | 01:51 |
| conifer | mate first, it somehow broke (but I'm a jinxed kind of person, so I'm used to it) so I switched to xfce | 01:51 |
| fsmithred | make sure you have policykit-1-gnome elogind libpam-elogind | 01:52 |
| fsmithred | before you do that... | 01:52 |
| fsmithred | check to see if consolekit is installed. If so, there's more to do first. | 01:52 |
| fsmithred | or do nothing and don't use pkexec. | 01:53 |
| conifer | you mean my error message about wayland? it's when I try to run synaptic with su - | 01:56 |
| conifer | I don't have consolekit but I have everything else | 01:56 |
| conifer | synaptic-pkexec as user shows gui asking for root pass | 01:57 |
| fsmithred | try it | 01:59 |
| fsmithred | that's what it should do if you select it from the apps menu, too | 01:59 |
| conifer | yes, it works fine, it's just that I picked a long and secure root password, and having to type it in again and again makes me cry :P | 02:01 |
| conifer | so when I have a su console open I'd rather run synaptic there if I need it | 02:01 |
| conifer | I guess I should've made my life easier with a simpler password | 02:03 |
| conifer | thank you again for your time and help | 02:04 |
| conifer | I need a rest, spend too much time in front of the screen already | 02:04 |
| fsmithred | yw | 02:04 |
| systemdlete | I've installed an alternate video card on the machine having the (very recent) video hiccups that was freezing my system. It's been running an hour or so without incident, so maybe this is a (temporary) fix at least. | 04:15 |
| systemdlete | It's an NVIDIA card and seems to play quite well with the rest of the system. So I will leave this in until another problem arises. At least this looks like it could be a data point to compare with, help to figure out what is going on. | 04:16 |
| DHE | nvidia cards are known to have performance stutters when using the GPU for computation, like OpenCL/CUDA. could that be related? | 04:20 |
| mason | DHE: Last one was a Radeon. | 04:33 |
| systemdlete | So far, so good, with the nvidia card. DHE: Thanks for the heads-up. I appreciate knowing that. | 05:52 |
| systemdlete | I am not expert in video cards, or video drivers. I understand a bit about how they work. I just figured, switching out to a different card, which uses some different drivers might help to bisect the problem a little. But please advise me if you think of more things I could do to get at the root. | 05:54 |
| systemdlete | I also should report that, from time to time over the past year or so, I've noticed that some of the components on the mb (Asus M5A7L/USB3?) have been... idk, kind of flakey. One time, the USB3 ports in the back were tempermental, but now they are working fine. More recently, a few days ago, the onboard ethernet was being flakey. I had to reset and jiggle the clip a while and since then, it's worked fine. Then this issue | 05:58 |
| systemdlete | with the video began yesterday (onboard radeon). | 05:58 |
| systemdlete | I wonder if the many kernel updates over these months may have addressed whatever software bugs may have existed, or if the hardware itself kind of "fluctuates" in stability. | 05:59 |
| systemdlete | In my experience, though, mb usually go suddenly and completely. Dead. I've never witnessed slow erosion of stability or utility of various components. I have many old mainboards here, most dead. Not sure why I keep them actually. | 06:01 |
| systemdlete | Probably I've been through 10-15 mb's in the past 25 years or so. The newer ones seem to last longer. | 06:01 |
| gnarface | systemdlete: i dunno, i've seen weird stuff happen, but if it's an old machine don't rule out the possibility that all weird and unpredictable hardware misbehavior could be a failing power supply | 06:44 |
| gnarface | systemdlete: things can behave all kinds of weirdly when they're not receiving spec power | 06:45 |
| systemdlete | gnarface: This machine is hooked up to a UPS, which theoretically at least, should be supplying steady 120 power. | 08:22 |
| systemdlete | (I think) | 08:23 |
| systemdlete | And this PS is fairly new, maybe a year old. | 08:23 |
| ShorTie | doesn't mean it can not go bad, or flakey | 09:17 |
| Junicchi | openrc vs sysvinit | 10:09 |
| Junicchi | which one is better? which one i should use? | 10:09 |
| Junicchi | i've been using sysvinit for about 4 months | 10:09 |
| Junicchi | never tried openrc b4 | 10:09 |
| gnarface | Junicchi: you probably don't have a good enough reason to switch based just on that info | 10:42 |
| gnarface | if it's working fine for you there's no reason to change it | 10:42 |
| gnarface | if you're curious what openrc does, that might be good enough reason, but just know there's more risk if you don't know what you're changing from to begin with | 10:43 |
| Junicchi | there are a lot reasons to switching openrc like it's speed at the first hand | 10:48 |
| Junicchi | am i the only one or devuan.org is down btw? | 10:48 |
| fsmithred | devuan.org is getting some work done on it | 10:49 |
| Junicchi | i'm unlucky as always | 10:50 |
| Junicchi | or it's the site | 10:50 |
| fsmithred | I don't see a speed difference with openrc. Boot times are the same (not using a stopwatch.) | 10:50 |
| fsmithred | runit seems to boot faster, but I agree that unless you have a good reason to change, stick with sysvinit. | 10:51 |
| fsmithred | do you write your own init scripts for anything? | 10:51 |
| fsmithred | devuan.org is working here | 10:52 |
| unixbsd | since 2-3 weeks, the deboostrap method does not longer work | 11:39 |
| unixbsd | the only way I can debootstrap is via using the DVD. | 11:39 |
| brocashelm | ceres users: if you have mdadm installed, don't use version 4.1-9 (breaks update-initramfs/initramfs-tools) | 12:32 |
| brocashelm | rolled back to 4.1-8 for now | 12:32 |
| fsmithred | brocashelm, does it cause problems even if you are not using raid? | 14:11 |
| brocashelm | it causes problems during upgrade attempts and just hangs on an unfinished upgrade. it did forewarn me with a bug report | 14:12 |
| brocashelm | so i pinned the package and upgraded the other packages in the pool | 14:13 |
| fsmithred | thanks. I'm in my ceres VM now. I'll try an upgrade. | 14:15 |
| brocashelm | >b3 - #974829 - 4.1-9 tries to copy non-existing /usr/bin/rm (proper location is /bin/rm) (Fixed: mdadm/4.1-10) | 14:16 |
| fsmithred | creating a symlink to fix that does not help | 14:31 |
| premoboss | hello, i ma trying to speed up the boot process ont a arm board, and i do the usual: recompile linux to get it lighter, eliminate unecessary service and so on. I will like to know tow muc time it is necessary to exegute /etc/rc.local and i add onto it the command "uptime > /dev/shm/record", but when i go to read the file, it report "0 min" but i need to know whow much seconds also. there is a place onto /proc or /sys that i can fin "milliseconds from | 18:25 |
| premoboss | start"? | 18:25 |
| fsmithred | bootlogd might do what you want. I don't remember how, but there's a way to get the data into a chart. | 18:26 |
| premoboss | fsmithred, if i cannot read directly from som place from virtual filesystems, i istall and try that, thanks. | 18:29 |
| premoboss | fsmithred, it is faster to add "cat /proc/update > /dev/shm/text.txt" into /etc/rc.local. I tell you just in case. | 19:10 |
| rkta | I installed gcc, but man gcc gives No manual entry for gcc man 7 undocumented says No manual entry for undocumented in section 7 What am I doing wrong? Where do I find documentation for this? | 19:45 |
| floofywolf | apt-get install gcc-doc | 19:48 |
| rkta | No candidate version found for gcc-doc | 19:49 |
| floofywolf | that's odd. | 19:51 |
| cronolio | https://github.com/gcc-mirror/gcc/tree/master/gcc/doc | 19:53 |
| floofywolf | googling suggests debian had to remove them due to licensing issues. | 19:53 |
| hagbard_ | its in non-free | 19:53 |
| rkta | Oh come on debian... | 19:53 |
| rkta | I have non-free in sources.list | 19:54 |
| floofywolf | looks like it's in contrib, and only in backports. | 19:55 |
| rkta | I can ssh to another box and read it there, but this is again a point where wonder why should I stick with debian... | 19:55 |
| * rkta is disappointed | 19:56 | |
| hagbard_ | i hve it in devuan unstable | 19:56 |
| hagbard_ | and testing | 19:56 |
| rkta | I'm on beowulf | 19:57 |
| floofywolf | apparantly the GFDL, which the gcc docs are licensed under, is not compatible with digital rights management software. which is a good thing, because DRM is evil. apparantly debian does not want to abide by this restriction. | 19:57 |
| floofywolf | and thus purged gfdl docs. | 19:57 |
| floofywolf | if you add beowulf-backports contrib you should be able to get it | 19:58 |
| rkta | I do get the point, and I'm all for it, but as a user this sucks | 19:58 |
| floofywolf | deb http://deb.devuan.org/merged beowulf-backports main contrib non-free | 19:59 |
| rkta | Atleast provide some dummy man pages explaining it and point me to a solution | 19:59 |
| floofywolf | I don't know if I get the point. I consider a license being incompatible with DRM to be a good thing, and the solution would be to eliminate the DRM crap, not eliminate the docs. | 19:59 |
| rkta | floofywolf: This, don't eliminate the docs... | 20:00 |
| floofywolf | but, debian has been increasingly going to shit lately, so it's not surprising. this is why devuan exists, after all. | 20:01 |
| rkta | Then, devuan, fix this sh*t. Give me hint. I know licenses are crap and painful. And about debian, there is a reason, why I'm here ;) | 20:03 |
| rkta | Adding contrib solved it. | 20:04 |
| floofywolf | devuan needs more developers to start fixing shit like that. shall I sign you up? :) | 20:04 |
| rkta | I'm using it for 3 weeks or so and I volunteered to test the new installer when it arrives. So, if I'm happy I will stay and contribute. :) | 20:06 |
| floofywolf | yay! | 20:06 |
| rkta | I'm really pissed about the way things evolved the last years! </rant> | 20:08 |
| floofywolf | bbl, going to replace a bad cooling fan on the inverter for my solar system | 20:11 |
| DonkeyHotei | how many planets does it have? :P | 20:12 |
| onefang | It's an inverted solar system, it has -8.5 planets. B-) | 20:18 |
| Wafficus | I just added a new USB A to B cable for my audio interface, but I believe my .asoundrc remains the same. I'm having difficulty hearing any audio except the mic input for the Scarlett Focusrite Audio interface (2nd gen) device I have | 20:25 |
| Wafficus | when I play a sound via mpv, I get the following output: | 20:25 |
| Wafficus | https://termbin.com/x7ch | 20:25 |
| Wafficus | the only thing I have present in my ~/.asoundrc is: defaults.pcm.card 1 | 20:26 |
| Wafficus | I'm not sure why I don't hear anything in Firefox or in mpv | 20:26 |
| fsmithred | are you sure Scarlett is card 1? | 20:28 |
| fsmithred | aplay -l | 20:28 |
| Wafficus | one sec will try that | 20:32 |
| Wafficus | it is card 2: USB [Scarlett Solo USB], device 0: USB Audio [USB Audio] | 20:33 |
| Wafficus | under that section it says: Subdevices: 1/1 Subdevice #0: subdevice #0 | 20:34 |
| Wafficus | so should I somehow make it be card 2 instead of card1? | 20:36 |
| Wafficus | yep that worked, will add that to my asound config dotfiles folder in its own separate fodler | 20:37 |
| Wafficus | though | 20:37 |
| fsmithred | yeah, if it's showing up as card 2, change it to card 2 in .asoundrc | 20:37 |
| Wafficus | I do get the popping sound when a YouTube video starts | 20:37 |
| Wafficus | is there anyway to remove that? | 20:37 |
| fsmithred | not aware of that problem | 20:38 |
| Wafficus | apparently it might be due to power saving | 20:39 |
| Wafficus | https://www.youtube.com/watch?v=Pdmy8dMWitg | 20:39 |
| Wafficus | will check that out | 20:39 |
| n4dir | If i start jack and do stuff with vcvRack, then close Rack, the stop jack, mocp can't connect to alsa anymore. | 20:42 |
| n4dir | As root i can start mocp | 20:42 |
| mason | Wafficus: Some sound cards are just poorly supported under Linux. I had to get a little USB DAC for one system where there was just no answer. | 20:42 |
| n4dir | i also can use mpv as user. | 20:42 |
| n4dir | what a confusion | 20:42 |
| Wafficus | mason: gotcha, yeah | 20:44 |
| Wafficus | the fact that it works makes me happy to say the least | 20:44 |
| mason | Oh, I guess it didn't qualify as a DAC...? Anyway, this thing: https://www.newegg.com/syba-sd-cm-uaud-usb-to-audio/p/N82E16812186035 | 20:44 |
| Wafficus | because even Focusrite themselves would refuse to support it | 20:44 |
| Wafficus | so its all good | 20:44 |
| Wafficus | My other SSD drive is in "read-only" mode, and I can't boot into Devuan | 21:41 |
| Wafficus | I was installing something in Emerge within a Gentoo VM, and then the entire ssd wouldn't allow me to write to it | 21:41 |
| Wafficus | is there anything I can do to troubleshoot or fix it, or is the SSD just kaput? | 21:42 |
| gnarface | Wafficus: probably just kaput, but if not, hdparm probably can unset the write-lock | 21:44 |
| Wafficus | like | 21:45 |
| Wafficus | as in destroyed? | 21:45 |
| gnarface | Wafficus: make sure you know the difference between a write-lock ore a filesystem corruption (in the latter case you could fix it by just writing zeroes) | 21:45 |
| Wafficus | I gotcha, yeah I have no idea what I'm dealing with | 21:45 |
| Wafficus | should I just remount it or something? | 21:46 |
| gnarface | Wafficus: if it's just a filesystem corruption but you can read everything, then i'd back it all up with tar to another disk while you write zeroes to this one with dd | 21:46 |
| gnarface | Wafficus: trying a remount is worth it but the least likely to work | 21:47 |
| Wafficus | yeah I can't even boot into it to back it up though | 21:47 |
| fsmithred | boot live and run fsck? | 21:47 |
| gnarface | Wafficus: also though, some manufacturers have proprietary diagnostic tools, and they're worth trying for recovery too. actually if it's samsung, probably try that first. | 21:47 |
| gnarface | Wafficus: yea, boot a live cd | 21:47 |
| Wafficus | I think its not Samsung but "CT" | 21:47 |
| Wafficus | after I run fsck in a live mode scenario | 21:48 |
| Wafficus | what else do I have to do | 21:48 |
| Wafficus | just follow the prompts? | 21:48 |
| gnarface | yea it might just fix everything | 21:48 |
| fsmithred | y | 21:48 |
| Wafficus | ok, I'll try that | 21:48 |
| Wafficus | gotta go get my usb stick containing Devuan one sec | 21:49 |
| Wafficus | back | 21:55 |
| Wafficus | so yeah I tried using Devuan's Rescue Mode | 21:55 |
| Wafficus | I tried mounting sda2 (the affected drive) but that failed | 21:55 |
| Wafficus | sda1, aka the one I'm on right now is totally fine, aka the 1 TB HDD | 21:55 |
| Wafficus | the affected drive, sda2, a 2TB SSD has the read-only issue | 21:55 |
| Wafficus | I tried using a shell command using a non-root file system aka the installer itself, but that didn't let me run fsck either | 21:56 |
| Wafficus | is there anything I can do while logged into the unaffected drive, sda1, or I need to somehow just overhaul the SSD anyway as a final attempt? | 21:58 |
| Wafficus | I ask because the only thing I had on there honestly was a Gentoo VM in virt-manager as it was purely being used as a VM box to house multiple VM's | 21:59 |
| Wafficus | should I just try running the Devuan installer to overhaul everything on the sda2 drive at this point? | 21:59 |
| fsmithred | you got a shell in the installer iso and could not run fsck? Note: it should not be mounted for that. | 22:06 |
| Wafficus | yeah | 22:08 |
| Wafficus | it couldn't run fsck | 22:08 |
| Wafficus | this was in "Rescue" Mode though | 22:08 |
| fsmithred | do you have a live-iso you could boot? | 22:09 |
| Wafficus | I was just using the min install Devuan iso | 22:09 |
| Wafficus | but I guess I could overwrite it with Devuan live-iso | 22:10 |
| Wafficus | I want this one right? | 22:12 |
| Wafficus | https://www.devuan.org/os/documentation/install-guides/beowulf/live-gui | 22:12 |
| fsmithred | only if you want to install from the live. But before that you want to boot the live system and run fsck. | 22:13 |
| fsmithred | desktop-live iso is what you want | 22:14 |
| gnarface | Wafficus: to be clear, you found the fsck command but ran it and it failed, complaining about not being able to write to the drive? | 22:15 |
| gnarface | Wafficus: or you just couldn't find the fsck command? | 22:15 |
| fsmithred | no fsck on the installer isos | 22:15 |
| gnarface | Wafficus: to backup the drive if you can't mount it, try using dd to copy a disk image | 22:16 |
| gnarface | Wafficus: dd if=/dev/sda of=./sda_disk_image_backup.img | 22:16 |
| gnarface | Wafficus: (if it gets through that, the resulting image will not have any hardware components that can refuse administrator override of write-locks) | 22:17 |
| gnarface | Wafficus: (so you MIGHT be able to mark the .img "read-write" and then fsck it successfully where you couldn't on the physical disk) | 22:18 |
| gnarface | Wafficus: (and incidentally, if that dd fails as root with a read-error, the disk is 100% borked) | 22:19 |
| Wafficus | so | 22:26 |
| Wafficus | sda2 is the affected rive | 22:26 |
| Wafficus | *drive | 22:26 |
| Wafficus | so the modified command is: | 22:26 |
| Wafficus | "dd if=/dev/sda2 of=./sda_disk_image-backup.img" right? | 22:27 |
| Wafficus | also, keep in mind | 22:27 |
| Wafficus | this current drive is actually LESS in size than the other one | 22:27 |
| Wafficus | so this drive aka sda1, that works, is a 1TB HDD | 22:27 |
| Wafficus | while the affected drive is sda2, a 2TB SSD | 22:27 |
| Wafficus | its possible to backup the .img file on a drive with less space? | 22:28 |
| fsmithred | not unless you compress it | 22:28 |
| Wafficus | if I wanted to nuke it though | 22:28 |
| fsmithred | better to use a bigger space, I think | 22:28 |
| Wafficus | can I just run the installer for Devuan instead for sda2? | 22:28 |
| Wafficus | *re-run | 22:28 |
| fsmithred | and better to use a separate drive if possible | 22:28 |
| fsmithred | you don't need to back it up? | 22:28 |
| Wafficus | not really | 22:29 |
| Wafficus | I've only had it for VMs | 22:29 |
| Wafficus | the only thing I really worked on was that Gentoo VM | 22:29 |
| Wafficus | so I don't mind re-doing it completely | 22:29 |
| fsmithred | anything anywhere on the entire drive that needs to be saved? | 22:29 |
| Wafficus | I wrote everything down that I needed | 22:29 |
| Wafficus | yeah no, I don't use that only for sandboxing VMs | 22:29 |
| fsmithred | nuke it | 22:29 |
| Wafficus | ok cool | 22:29 |
| fsmithred | start over is easiest | 22:29 |
| Wafficus | so dd the drive first right? | 22:30 |
| fsmithred | I would still do some diagnostics if possible | 22:30 |
| fsmithred | dd why? | 22:30 |
| Wafficus | to fill it with zeroes no? | 22:30 |
| fsmithred | I might do a few megabytes at the beginning | 22:30 |
| fsmithred | would not bother with the whole drive. Was there lvm on it? | 22:30 |
| Wafficus | no | 22:31 |
| Debluk | Hi, I just tried Devuan for the first time and I installed some packages from the repository. When I installed the package `cockpit`, I noticed that the man page references to systemd and that there is no init script to start it. Do I have to write my own script or I am missing something here? I started it manually and it seems to work generally. Thanks! | 22:31 |
| Wafficus | I think I did the setup where you basically just mount the whole drive, and let Devuan figure out the partitions | 22:32 |
| gnarface | Debluk: i don't actually know, (because i'm not familiar at all with that package,) but possibly, and it wouldn't have been unhead-of even before systemd. look in /usr/share/doc/cockpit/ to see if they left you any examples. | 22:33 |
| fsmithred | Wafficus, I would keep the number of partitions low. | 22:33 |
| fsmithred | Maybe one partition and swap, and probably a separate partition for /home | 22:33 |
| fsmithred | don't let the installer make a bunch of partitions. It's likely to screw up the sizes. | 22:34 |
| Wafficus | yeah I'll try redoing it | 22:35 |
| Wafficus | one sec | 22:35 |
| Wafficus | will be back | 22:35 |
| fsmithred | Debluk, hey, I looked up that package and I saw something familiar | 22:36 |
| fsmithred | 389-ds | 22:37 |
| fsmithred | saw that yesterday | 22:37 |
| fsmithred | someone is attempting to build 389-ds-base for unstable | 22:37 |
| fsmithred | so we're on it. Looks like we forked the package, so it will have init scripts again. | 22:38 |
| fsmithred | you might grab the scripts from an older version of the package. | 22:38 |
| Debluk | thanks, I'll have a look. | 22:39 |
| Wafficus | back | 22:44 |
| Wafficus | yikes, yeah tried to overwrite sdb aka sda2 or whatever | 22:44 |
| Wafficus | input/output error received | 22:44 |
| fsmithred | not a good sign | 22:44 |
| Wafficus | not sure if I need to just take apart the computer, open it up, try to replug the ssd back in or something, and then see what to do | 22:44 |
| fsmithred | probably not | 22:46 |
| gnarface | Wafficus: try the manufacturer's diagnostic tool | 22:47 |
| gnarface | Wafficus: sounds like it might be borked | 22:47 |
| Wafficus | its a "Crucial" SSD if that makes a difference | 22:47 |
| fsmithred | oh | 22:47 |
| Wafficus | idk if they have a linux utility for it though | 22:47 |
| fsmithred | mx or bx? | 22:47 |
| fsmithred | I have a bx, never checked for utility. Someone recently told me there's no heat sink in it. | 22:48 |
| gnarface | Wafficus: doesn't really tell me much, but i did just find out that Samsung disks are allergic to my AMD motherboard, and i need to disable NCQ for them from the kernel-command-line, or they periodically throw bus errors | 22:48 |
| gnarface | Wafficus: i thought it was particular to Samsung, but if there | 22:49 |
| Wafficus | it was this one https://www.newegg.com/crucial-mx500-2tb/p/N82E16820156175?Item=N82E16820156175 | 22:49 |
| gnarface | Wafficus: ... but if there's a particular type of errors in dmesg afterwards, they'll be the smoking gun | 22:49 |
| Wafficus | it is this one rather * MX500 | 22:49 |
| Wafficus | what errors do I need to look out for when I attempt to boot into that sda2 drive? | 22:49 |
| gnarface | just look in dmesg | 22:50 |
| Wafficus | I ask because it keeps spouting these read permissions stuff | 22:50 |
| Wafficus | it can't even boot into it | 22:50 |
| gnarface | write errors and bus resets | 22:50 |
| gnarface | hmm | 22:50 |
| Wafficus | like its hard to describe | 22:50 |
| Wafficus | like it keeps trying to access the drive | 22:50 |
| gnarface | it did used to work? | 22:50 |
| gnarface | or is this new? | 22:50 |
| Wafficus | yeah just today | 22:50 |
| Wafficus | until that Gentoo compilation thing in a VM | 22:50 |
| gnarface | hrmmmm.... | 22:50 |
| Wafficus | after that happened, then even in Gentoo vm it complained of a similar read-only issue | 22:51 |
| Wafficus | and then I tried to take a screenshot and realized the whole damn drive was screwed | 22:51 |
| Wafficus | because I couldn't even save to the same disk because it was complaining about some read-only thing | 22:51 |
| gnarface | what does "hdparm -r /dev/sda" say? | 22:52 |
| Wafficus | /dev/sda: | 22:52 |
| Wafficus | readonly = 0 (off) | 22:52 |
| gnarface | promising, actaully... (incidentally, that's he drive i was wishing i'd gotten instead of this Samsung one as soon as i found out about the drive controller incompatibility) | 22:53 |
| gnarface | you don't care what's on it, and you're not booted into it right now, right? | 22:53 |
| Wafficus | that's correct | 22:53 |
| Wafficus | I'm on my "Desktop" sorta drive | 22:53 |
| Wafficus | the "just works drive" | 22:53 |
| gnarface | dd if=/dev/zero of=/dev/sda | 22:53 |
| Wafficus | with Openbox and stuff | 22:53 |
| Wafficus | hold on | 22:53 |
| Wafficus | sda1 is good | 22:54 |
| Wafficus | sda2 is bad | 22:54 |
| gnarface | they're one device | 22:54 |
| Wafficus | I don't want sda to be 'dd' 'd either | 22:54 |
| Wafficus | ah gotcha | 22:54 |
| gnarface | they're two partitions on the same physical drive | 22:54 |
| Wafficus | what will that command do above though? | 22:54 |
| Wafficus | sdb is the bad one | 22:54 |
| Wafficus | sda is the one I wanna keep | 22:54 |
| gnarface | oh, my bad | 22:55 |
| Wafficus | no worries | 22:55 |
| Wafficus | just wanted to confirm lol | 22:55 |
| gnarface | well just change sda for sdb in my example then | 22:55 |
| Wafficus | before I nuke the good one | 22:55 |
| Wafficus | ok gotcha | 22:55 |
| gnarface | and yes, it would work on an individual partition too | 22:55 |
| Wafficus | dd: writing to '/dev/sdb': Input/output error | 22:55 |
| gnarface | well wait | 22:55 |
| gnarface | what does "hdparm -r /dev/sdb" say? | 22:56 |
| gnarface | since i got that wrong too | 22:56 |
| Wafficus | /dev/sdb: | 22:56 |
| Wafficus | readonly = 0 (off) | 22:56 |
| gnarface | same | 22:56 |
| gnarface | hmm | 22:56 |
| gnarface | and you're sure that's the one? | 22:57 |
| Wafficus | yeah | 22:57 |
| Wafficus | lsblk shows its the 2 tb drive | 22:57 |
| Wafficus | aka sdb is the 2 tb one | 22:57 |
| Wafficus | aka 1.8T disk | 22:57 |
| gnarface | https://www.crucial.com/support/ssd-support/mx500-support | 22:58 |
| gnarface | check for firmware update | 22:58 |
| gnarface | just shooting in the dark now | 22:58 |
| gnarface | it's behaving like it is definitely fried, but hdparm would be expected to return "readonly = 1" when exhibiting this behavior for hardware failure reasons | 22:58 |
| gnarface | so we can't rule out a weirder glitch yet | 22:59 |
| gnarface | but keep in mind i've got 0 first-hand experience with these drives and i was recently thrown for an unexpected loop by an SSD too | 22:59 |
| Wafficus | ah the firmware seems Windows specific | 22:59 |
| Wafficus | *update | 22:59 |
| gnarface | if it's anything like Samsung's, that's just a blatant lie | 23:00 |
| gnarface | if it's like samsung's it's a bootable iso that doesn't care what OS you write it from | 23:00 |
| Wafficus | yeah but it seems like drivers that you have to install ON Windows itself | 23:01 |
| Wafficus | hard to describe | 23:01 |
| gnarface | (i booted Samsung's with unetbootin from usb but my drive was already up-to-date it turned out) | 23:01 |
| Wafficus | but its a Windows specific installer | 23:01 |
| gnarface | no, ignore those too | 23:01 |
| Wafficus | https://www.crucial.com/support/ssd-support/mx500-support | 23:01 |
| gnarface | oh, this just says "firmware update not avalable at this time" sorry | 23:01 |
| gnarface | hopefully they release one | 23:02 |
| gnarface | i would consider trying to RMA it | 23:02 |
| gnarface | i still can't be 100% sure it's not fixable, but at this point it's given us enough trouble i think the worst their support staff could do is ask you to install windows on it to prove it | 23:02 |
| gnarface | https://content.crucial.com/content/dam/crucial/ssd-products/ssd-family/documents/crucial-firmware-update-generic/crucial-firmware-update-all-en.pdf?cm_mc_uid=25826339150916034627060&cm_mc_sid_50330000%7cwww.crucial.com=63704521605477478988 | 23:03 |
| gnarface | this pdf says it's either-or | 23:03 |
| gnarface | you can either use their "executive" windows software suite to update the drive, or you can boot the bootable ISO instead | 23:03 |
| gnarface | but there's no bootable ISO released for this drive yet | 23:03 |
| Wafficus | I bought this back on 10/5/2019' | 23:04 |
| gnarface | which suggests it's bleeding-edge hardware they haven't even patched the firmware on | 23:04 |
| gnarface | oh | 23:04 |
| Wafficus | so I don't know if I could actually take it back | 23:04 |
| Wafficus | rather return it | 23:04 |
| Wafficus | on Newegg * | 23:04 |
| Wafficus | :/ | 23:04 |
| gnarface | yea being over a year old totally nukes that theory actually | 23:04 |
| gnarface | for some reason i thought you meant you'd purchased it yesterday | 23:04 |
| Wafficus | nah, I've had it for just a year | 23:05 |
| Wafficus | :/ | 23:05 |
| Wafficus | never had a drive fail this easily | 23:05 |
| Wafficus | kind of sad, idk | 23:05 |
| Wafficus | ffn thing was like $220 too | 23:05 |
| Wafficus | stupid SSD meme | 23:05 |
| gnarface | well the windows executive suite might have some sort of diagnostic tool that would at least let you be 100% sure, but maybe actually can fix it | 23:05 |
| gnarface | if you're not opposed to installing windows to use it, it's worth a try | 23:05 |
| gnarface | kinda your last resort at this point | 23:05 |
| gnarface | oh | 23:06 |
| gnarface | well | 23:06 |
| fsmithred | smartmontools maybe show something? | 23:06 |
| gnarface | i should mention that's assuming it's not the actual port on the motherboard | 23:06 |
| gnarface | Wafficus: keep in mind it could be the physical port or drive controller too... you tried it in another sata port just to be sure, right? | 23:07 |
| gnarface | Wafficus: we're fairly certain it's hardware failure now but we don't know for sure it's the drive yet. | 23:07 |
| gnarface | smartmontools certainly is worth a look | 23:07 |
| Wafficus | on 'apt' right? | 23:08 |
| fsmithred | apt install smartmontools | 23:09 |
| fsmithred | smartctl -a /dev/sdb | 23:09 |
| Wafficus | damn just because it was after 1 year, Newegg won't return it | 23:09 |
| Wafficus | ah that blows so much | 23:09 |
| Wafficus | never buying an SSD again | 23:09 |
| Wafficus | anyway | 23:09 |
| Wafficus | yeah I'll try that | 23:09 |
| fsmithred | probably should apt update first | 23:10 |
| gnarface | Wafficus: well, for the future, if you have to (you probably will eventually, because eventually there won't be other drive types) f2fs is supposed to be made to not kill SSDs | 23:10 |
| gnarface | Wafficus: i have a feeling that in about 13 months i'm going to be uttering the same curses though | 23:10 |
| gnarface | Wafficus: that drive was the one supposedly known for resilience. i got the one known for "speed" .... | 23:11 |
| Wafficus | I install smartmontools | 23:12 |
| Wafficus | but smartctl command doesn't exist | 23:12 |
| fsmithred | oh | 23:12 |
| Wafficus | yeah I can still contact the manufacturer thankfully though | 23:12 |
| fsmithred | su - | 23:12 |
| Wafficus | so I'll reach out tomorrow | 23:12 |
| fsmithred | to get root 'su -' | 23:12 |
| fsmithred | then it'll be in your path | 23:12 |
| fsmithred | or call it as /usr/sbin/smartctl | 23:12 |
| Wafficus | https://termbin.com/y5tw | 23:13 |
| fsmithred | nothing there I recognize as terminal | 23:15 |
| fsmithred | it says it passed, there are no reallocated sectors | 23:16 |
| fsmithred | I suppose you could run a test | 23:16 |
| * gnarface is starting to wonder if it's not the cable or the SATA port actually, and the drive is fine | 23:16 | |
| gnarface | Wafficus: were you able to try the SSD plugged physically into something else? | 23:17 |
| gnarface | Wafficus: that's a necessary step to fully deduce this issue | 23:17 |
| gnarface | it's more rare, but i've seen it more than once, the onboard harddrive controller, or even just one single port on it, goes bad | 23:18 |
| gnarface | it can happen | 23:18 |
| Wafficus | hmm | 23:18 |
| Wafficus | well | 23:18 |
| gnarface | often doesn't leave any visible physical evidence | 23:18 |
| Wafficus | this is the only desktop I have | 23:18 |
| gnarface | does it have more sata ports? | 23:18 |
| Wafficus | yeah a ton more | 23:18 |
| Wafficus | like 6 total I think | 23:18 |
| Wafficus | on this motheboard | 23:18 |
| Wafficus | *motherboard | 23:18 |
| Wafficus | its been a while | 23:18 |
| gnarface | try it, and if some are on a different controller (they'll be a different color probably) then try those too | 23:19 |
| Wafficus | Ive played around with my Thinkpad for the last two years more than I've ever used this desktop to eb honest | 23:19 |
| fsmithred | put sdb onto sda's cable and sata port, boot the installer iso and see if you can partition the drive | 23:19 |
| Wafficus | hmm... well | 23:19 |
| Wafficus | I'll try the third port | 23:19 |
| Wafficus | I don't wanna mess up this one to be honest | 23:19 |
| Wafficus | but yeah I do like the idea | 23:19 |
| fsmithred | rule out bad cable and bad sata port | 23:19 |
| Wafficus | true | 23:19 |
| Wafficus | hmm kinda scared | 23:20 |
| Wafficus | though I guess I'll back up my stuff | 23:20 |
| Wafficus | I'll try this next weekend to be honest | 23:20 |
| Wafficus | cause I wanna backup the music stuff on here first | 23:20 |
| fsmithred | if you un-plug sda, it can't be harmed | 23:20 |
| Wafficus | and then i'll do it | 23:20 |
| gnarface | uh, to be clear, do this while the machine is powered down | 23:23 |
| gnarface | SATA hotplug isn't as universally implemented as people think | 23:23 |
| gnarface | manufacturers often only enable it for external ports | 23:23 |
| fsmithred | huh. Where your smart output has 'Unknown_Attribute', my BX500 has actual names for things. | 23:23 |
| gnarface | hmmm, suspicious | 23:24 |
| fsmithred | the MX supports more tests | 23:25 |
| fsmithred | I don't think either one has error correction, but I do have a line labeled as Error_Correction_Count | 23:26 |
| fsmithred | value is 0 | 23:26 |
| Wafficus | gotcha | 23:30 |
| Wafficus | well, i'll try reseating the cables and see if that fixes it | 23:31 |
| Wafficus | will be back | 23:31 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!