[20:54] <adac> I try to install the grub again to my disks in a chrooted environment, following basically these commands here: https://blog.michael.franzl.name/2014/01/29/remote-server-hetzner-rebooting/ however for one disk I get the error grub-install: error: unable to identify a filesystem in hostdisk//dev/nvme0n1; safety check can't be performed
[20:55] <adac> the problem then here is that my machine wont boot anymore since that fails
[20:55] <adac> any ideas what I can do about this?
[20:58] <tomreyn> "hostdisk//dev/nvme0n1" is obviously wrong, and i've never seen this. how did you install?
[20:58] <tomreyn> and which version of ubuntu server is this?
[21:00] <adac> tomreyn, actually at the moment I'm on the rescue system of the provider and I have chrooted into my machine wichh is ubuntu  18.04
[21:00] <adac> This was a raid and I had to let change one disk
[21:01] <tomreyn> and this recue system is compatible to ubuntu 18.04 ?
[21:01] <tomreyn> oh you chrooted so you're using 18.04 tools
[21:01] <adac> tomreyn, good question. usually when this happened that the grub was missing, which happend more often before, this used to work
[21:02] <adac> tomreyn, how can I see if it is compatible?
[21:02] <tomreyn> there's no a simple check to tell
[21:03] <tomreyn> but if you chrooted to the existing ubuntu 18.04 installation with the same boot mode it usually boots in, and with all virtual file systems bind mounted into it, you should be able to recover it if the kernel of the recovery system is not extremely old
[21:04] <tomreyn> try this https://askubuntu.com/a/831241
[21:05] <tomreyn> you'll need to get your SW RAID ready  as the first step, though
[21:06] <tomreyn> disabling secure boot in the systems' bios and upgrading the bios can make things easier, especially if its old.
[21:07] <adac> tomreyn, actually back when this happened before on other machines after a disk swap, I did not had to get the SW raid ready before. I just went into the rescue system and re-installed grub
[21:07] <adac> not sure why this time it fails
[21:07] <tomreyn> journalctl -b | grep DMI:    tells you about board and bios version. hetzner provides bios upgrade tools on their network share, and you can access the system bios fro their KVM (which is free for 2 hours=
[21:08] <adac> journalctl -b
[21:08] <adac> -- Logs begin at Thu 2022-02-03 04:27:42 CET, end at Sun 2022-02-20 20:02:29 CET. --
[21:08] <adac> -- No entries --
[21:08] <adac> tomreyn, ok thanks
[21:09] <tomreyn> you must be working on the rescue system still
[21:09] <tomreyn> dmesg | grep DMI:   then
[21:09] <tomreyn> please use a pastebin to share multi-line outputs
[21:10] <adac> https://pastebin.com/HrBJXnYh
[21:11] <tomreyn> first line of this output is your mainboard + bios version
[21:12] <adac> tomreyn, ok I see. It might be worth upgrading then
[21:13] <tomreyn> you may want to check this with support, too.
[21:13] <adac> tomreyn, yes I will ask them. It is strange behaviour
[21:14] <tomreyn> that's a customized (for hetzner) gigabyte desktop board you have there
[21:24] <tomreyn> https://www.gigabyte.com/Motherboard/B360-HD3P-rev-10/support#support-dl-bios would be the closest, but the release date given for version F4 there does not match up with the build date of yours
[21:25] <adac> tomreyn, I think I could ask them that they would upgrade it for me
[21:28] <tomreyn> possibly. i don't know whether it's actually needed, just suggesting it generally.
[21:28] <tomreyn> it's old,though, they should probably do it without asking
[21:28] <adac> tomreyn, yes I see. Yeah they usually just do when there is a problem
[21:29] <adac> Im doing a backup in the rescue system of my virtual machine images first now
[21:29] <adac> then I need to see how to proceed
[21:32] <tomreyn> you said this problem occurred after / due to a disk swap. i'm assuming the disk that was swapped contained the (single copy of the) ESP, and you had a mirror md raid spun across other partitions on this and the other nvme storage (which you still have one leg of, just without the esp)
[21:33] <tomreyn> if you re-create an esp there and re-populate it, you could possibly boot from there also without the raid restored, but in failed state.
[21:35] <tomreyn> there are ways to keep a backup copy of the active ESP on another storage (such as the one which contains the other leg of a RAID-1), if you want to consider this in the future
[21:37] <adac> Yes that could be the reason
[21:38] <adac> what would that mean booting in failed state?
[21:38] <adac> usually the raid is off already since before the disk swap one has to remove the disk from the raid
[21:39] <adac> which I also did this time
[21:40] <adac> so back then I was always able to enter the rescue system, install the grub again, then reboot and it would boot
[21:40] <adac> afterwards i put the disk back into the raid
[21:42] <tomreyn> if this is a raid-1 array then it has to have a minimum nuumber of 2 devices. if you only have a total of two then removing one would bring the array into failed state, from what i rmember.
[21:43] <tomreyn> the difference between earlier recoveries of this type and now is probably that earlier, the disk that was affected was the one without the ESP on it, but this time it was the one with the ESP on it, so you lost that
[21:43] <tomreyn> i'm still guessing, though, don't actually know how you boot or manage the ESP
[21:44] <adac> tomreyn, https://pastebin.com/R7dNyAjA see that is that array you probably mean. That was right after i  removed nvme0n1 from the raid
[21:45] <adac> tomreyn, ok I see. How can I check if the ESP is actually there?
[21:45] <tomreyn> '(F)' means failed device
[21:46] <tomreyn> the _ in '[_U]' means you're missing the first leg of this two device array
[21:47] <adac> Yes exactly the one that I moved out of the raid
[21:47] <tomreyn> fdisk -l   should list all partitions and their flags, if there's an ESP there it should show
[21:51] <adac> tomreyn, actually thisis the situation: https://pastebin.com/CS5ECmfM
[21:51] <adac> searched for esp string. Not found
[21:53] <tomreyn> hmm, do you actually boot in efi mode, though?
[21:53] <tomreyn> those are mbr/dos partition tables
[21:55] <adac> tomreyn, I'm afraid I do not really know
[21:55] <tomreyn>  /dev/nvme1n1 contains a 512 MB partition, nvme1n1p2, this could be /boot, could also be ESP, but not on an mbr partitioned disk, so you probably boot in bios mode
[21:56] <tomreyn> is sda the recovery system?
[21:57] <adac> https://pastebin.com/n1GKYWkZ thisis the current situation in the rescue system after the steps in https://blog.michael.franzl.name/2014/01/29/remote-server-hetzner-rebooting/
[21:57] <adac> sda is an additional disk actually that was added
[21:58] <adac> since I run out of space for my logs
[22:02] <tomreyn> i see. i guess in your situation all you may need to do is to re-create the missing partitions on nvme0n1 to match those of nvme1n1 and then to install grub to both /dev/nvme0n1 and /dev/nvme1n1
[22:03] <tomreyn> and then, either before or after reboot, to resynch the raid by re-adding the nvme0n1 raid members
[22:03] <adac> tomreyn, Yes that sounds about right
[22:04] <adac> tomreyn, thank you so much man
[22:04] <tomreyn> you're welcome
[22:06] <tomreyn> this guide you're following is not bind mounting /dev/pts into the chroot. you may need to do that also
[22:07] <tomreyn> hmm, no, you probably wont need it
[22:10] <adac> I just finish the backup, just to be save. I have backups, but not up to date one of the whole virtual machines. then I will try to create these partitions
[22:11] <adac> can I somehow see the exact partitions of rhe working disk and maybe just use exactly thes?
[22:13] <adac> sfdisk -d /dev/nvme1n1 | sfdisk /dev/nvme0n1
[22:13] <adac> Copy over partition table from /dev/nvme1n1 to /dev/nvme0n1
[22:17] <tomreyn> i guess this can work. might fail for the last partition if that's larger on the existing disk than there is space available on the new one
[22:18] <adac> tomreyn, kk I will try afterwards
[22:19] <adac> I#m just wondering. this usually happened after the disk was changed and when i was already booted into the system
[22:19] <adac> then, before putting the disk into the raid, we copied over the partition tables with a script
[22:20] <adac> maybe on the other disks, they were already there
[22:20] <tomreyn> that seems unlikely, unless you had been using those disks before
[22:21] <adac> not sure tbh. I will finish the backup then lets try it out :D
[22:22] <adac> aaaaa these disk issues a are a nightmare!
[22:26] <tomreyn> good luck on that, i'll make that a fortunate outcome in my dreams.
[22:28] <adac> tomreyn, hehe thanks!! Have a good night!! :-)


[09:10] <caodepalha> Hi everyone
[09:10] <cfhowlett> caodepalha, greetings
[09:12] <caodepalha> I have a question here. I read in a book that it is advisable to remove the pusleaudio package in ubuntustudio. it read that both servers running at the same time jackd & pulseaudio) can cause problems. is this correct?
[09:22] <caodepalha> does anyone know anything about this?
[09:24] <XRS1> i havent had any problems
[09:37] <zequence> caodepalha: Not correct
[09:37] <zequence> caodepalha: What book was that?
[09:42] <caodepalha> let me check again
[09:42] <caodepalha> its a book called crafting digital media
[09:43] <caodepalha> Crafting digital media, Audacity, Blender,Drupal, GIMP, Scribus and other open source tools
[09:44] <cfhowlett> caodepalha, read it.  since published, it seems the pulse/jack conflicts have been ironed out.  and if YOU haven't experienced problems, why would you even consider it?
[09:44] <caodepalha> by Daniel James
[09:44] <caodepalha> i get a lot of xruns when recording
[09:45] <zequence> caodepalha: Is it a Ubuntu Studio install?
[09:45] <caodepalha> in the book it says it is related to the settings in jack and problems with pulse audio
[09:45] <caodepalha> yes it is ubuntu studio
[09:45] <zequence> the book is wrong
[09:45] <caodepalha> ok thank you
[09:45] <cfhowlett> "a lot"?   anyway, try it and compare.
[09:45] <zequence> jack settings, yes. but not because of pulseaudio
[09:45] <caodepalha> do you know what xruns are about?
[09:46] <zequence> xruns means that jack was not able to process the audio in time
[09:46] <zequence> theres another word for that: audio dropout
[09:46] <caodepalha> is that a problem when recording?
[09:46] <zequence> Yes, because you get click sounds
[09:46] <caodepalha> sorry i'm still a newbie
[09:46] <caodepalha> any tips on how to avoid that?
[09:46] <zequence> caodepalha: do this command: cat ~/.jackdrc
[09:46] <cfhowlett> caodepalha, FYI, the 12.04 kernel seemed to fix that issue
[09:47] <zequence> cfhowlett: Which issue is that?
[09:47] <cfhowlett> zequence, jack/pulse audio conflicts
[09:47] <zequence> cfhowlett: not related to the kernel
[09:47] <zequence> there was a bug in pulseaudio, which I fixed
[09:48] <zequence> had to do with pulseaudio not letting go of the audio device, when jack asked for it
[09:48] <zequence> jack1 is not able to grab the card at all
[09:48] <zequence> only jack2
[09:48] <cfhowlett> zequence, entirely possible/likely that I used the wrong term there ...
[09:48] <zequence> there was another problem with jack earlier, making it impossible to kill it sometimes
[09:48] <zequence> that was fixed too
[09:49] <zequence> neither problem was causing xruns
[09:49] <zequence> I didn't code the fix, but I pathched both packages, just to be clear
[09:50] <caodepalha> so should i run the: cat ~/.jackdrc ?
[09:51] <cfhowlett> zequence, you contributions are MUCH appreciated!
[09:51] <zequence> caodepalha: Yes. Paste the results here
[09:54] <cfhowlett> zequence, here's mine.  What's it all mean?   /usr/bin/jackd -p 128 -R -P 60 -T -d alsa -n 2 -r 48000 -p 1024 -d hw:0,0
[09:58] <zequence> "-p" stands for frames per period. It is quite low, so should give you ok latency, and hopefully no xruns
[09:58] <zequence> To see what the rest means, do: jackd -d alsa --help
[09:59] <vlt> holstein: I got the source from their website because I wanted to compile it on Debian. But I failed. So I downloaded their binary for Ubuntu and after hours of installing dependencies ... it kind of works.
[09:59] <zequence> Actually, some options are not alsa specific, so to see them, do: jackd --help
[09:59] <vlt> Except for freezing X for several minutes and OOMs .-/
[10:02] <caodepalha> ok these are the results: /usr/bin/jackd -p128 -dalsa -r192000 -p128 -n2 -Xseq -D -Chw:0 -Phw:0
[10:02] <caodepalha> do i need to start jack before running the command?
[10:04] <zequence> caodepalha: What you did was print out the contents of the file .jackdrc in your home folder
[10:04] <zequence> caodepalha: If you would start jack manually using a terminal, you could use a command like that. But, you don't need to
[10:04] <zequence> caodepalha: That command is how you have set up qjackctl
[10:04] <caodepalha> ok...
[10:05] <caodepalha> is it correct?
[10:05] <zequence> caodepalha: The reason why you are getting xruns is because you have a very low latency setting
[10:05] <caodepalha> ah ok. what can i change on jack setting then?
[10:05] <zequence> caodepalha: -p128 means 128 frames/period. Together with 192000 samplerate, that gives jack a very small amount of time to finish its processes
[10:06] <zequence> caodepalha: Use qjackct, and raise the frames/period, or use a lower samplerate. Do you need 192kHz=
[10:06] <zequence> ?
[10:06] <caodepalha> ok let me check!
[10:08] <zequence> caodepalha: Do you monitor yourself through the software? What do you use for recording? Ardour?
[10:08] <zequence> If you have a mixer for monitoring, you don't need low latency - unless of course you are playing a soft synth, or using some FX, like a virtual amp while recording
[10:08] <caodepalha> I use ardour
[10:09] <zequence> caodepalha: What sort of stuff do you record? Is it all line in, and no live FX from your computer?
[10:10] <caodepalha> I use ardour. I connect the electir guitar directly to the laptop input. my midi is connected directly to the laptop as well. when i record vocals i connect a condenser mic through a mixer and then onto the laptop
[10:10] <zequence> caodepalha: midi, as in midi cable, or the audio output from a keyboard?
[10:11] <caodepalha> i use electric guitars, acoustic guitars, a condenser mic and a shure sm58, a small beringer mixer and oxygen8
[10:11] <zequence> midi is not audio. It's a data control format. you can use it to control synthesizers
[10:11] <caodepalha> i connect oxygen8 via usb
[10:12] <caodepalha> yes
[10:12] <cfhowlett> caodepalha, yeesh.  that's kind of asking a lot.  you got a super duper system or something?  I used an interface when I recorded for my laptop.
[10:12] <zequence> ok, so do you use soft synthesizers? That would be the live FX I'm talking about
[10:12] <caodepalha> yes eventually i use amsynth and phasex
[10:13] <zequence> caodepalha: While you are not using any live processing, i.e. a soft synth, you can raise latency while recording
[10:13] <zequence> caodepalha: Raise frames/period to at least 1024
[10:13] <zequence> you can even use 2048
[10:14] <zequence> And use your mixer for monitoring for the external audio sources, as your guitars and vocals
[10:14] <zequence> When you record soft synths, you need to find out an optimal latency level. You might not need 192kHz. 48kHz is quite enough.
[10:15] <zequence> And while recording, don't mess with the computer. Just click record, and then use your keyboard
[10:15] <caodepalha> iḿ getting started on linux. i'm a total newbie.in the first experiences i made with ardour i dropped a few loops on it, then went to record some electric guitars
[10:16] <caodepalha> latter added some synths
[10:16] <caodepalha> and more guitars
[10:16] <zequence> caodepalha: What kind of audio card do you have?
[10:17] <caodepalha> you're saying i should raise the frames or use a lower sample rate right?
[10:17] <caodepalha> this is a laptop i got from a friend
[10:17] <caodepalha> how can i know about the soundcard? lol
[10:17] <zequence> caodepalha: Both would be good, actually
[10:17] <zequence> caodepalha: Oh, so it's the builtin audio device?
[10:18] <zequence> cat /proc/asound/cards
[10:18] <caodepalha> yes... for now it is. i'm planning on getting an external soundcard
[10:18] <zequence> ..for seing the audio devices
[10:18] <caodepalha>  0 [Intel          ]: HDA-Intel - HDA Intel
[10:18] <caodepalha>                       HDA Intel at 0x92400000 irq 43
[10:18] <cfhowlett> caodepalha, see presonus 1box/audiobox.  works with linux out of the box.
[10:18] <caodepalha> here it is
[10:18] <zequence> caodepalha: 128 frames/period might work if you use 48kHz samplerate. If that doesn't work, try 256 frames/period with 48kHz samplerate
[10:19] <caodepalha> ok!
[10:19] <zequence> caodepalha: If you still have a lot of xruns, come back
[10:20] <caodepalha> I cannot thank you enough! Its a bit of a learning curve to get around linux but i'm loving it. people are very helpfull. this is great! thanks alot
[10:22] <zequence> caodepalha: Have fun
[10:45] <caodepalha> this is what i've made with ardour so far: https://soundcloud.com/caodepalha/fairground-voodoo-mix-cheap
[10:53] <zequence> caodepalha: Nice stuff
[10:55] <zequence> caodepalha: There is actually one thing that could cause xruns, and that is the pulseaudio to jack module. It's a package called pulseaudio-module-jack. You can disable the module, either by uninstalling that package, and restarting pulseaudio (pulseaudio -k), or by disabling dbus support for jack in qjackctl -> Misc
[10:55] <zequence> The module acts as any other jack client
[10:55] <zequence> but, it can use a lot CPU power. If you don't need to listen to youtube while recording, you can just uninstall that package
[10:56] <caodepalha> i dont need to listen to youtube while recording
[10:57] <caodepalha> can it be unistalled in the software center?
[10:57] <caodepalha> uninstalled*
[10:58] <zequence> caodepalha: sudo apt-get remove pulseaudio-module-jack
[10:58] <zequence> caodepalha: or use synaptic. You can install synaptic from the software center
[10:58] <zequence> just remember to restart pulseaudio.  To restart pulseaudio, kill it: pulseaudio -k
[10:59] <caodepalha> jack is not started right now. can i perform those commands anyway?
[11:23] <caodepalha> ok i've just done those commands
[12:39] <mo> 0913
[12:39] <Guest6012> 0913
[22:16] <nimbiotics> After allowing some updates earlier today my soundcard started making funny noises as the volume level indicator showed up time after time. After rebooting, I am getting no more audio from my card, even though everythinh 'seems' normal. any ideas? TIA!
[22:18] <XRS1> Application Launcher -> Terminal Emulator -> alsamixer
[22:18] <XRS1> make sure its not muted, turned down and that the correct card is being used
[22:27] <nimbiotics> XRS1, Master level is at 57, but Headephone , does not show a value (zeroed?) How do I raise the volume lvel in alsamixer?
[22:31] <XRS1> use the tab key and the arrow keys to navigate


[16:30] <jodh> xnox: Still having problems with my ->valid branch but it's demonstrated that current upstream is still iterating through job_change_state() too many times; try applying http://paste.ubuntu.com/7588618/ and booting!
[16:32] <xnox> jodh: we don't gurantee clean process_data[process] at that point.
[16:32] <xnox> jodh: we only reset it to null after a job is starting from stopped.
[16:33] <jodh> xnox: the point is that we're calling job_process_data_new() multiple times for the *same* job process
[16:33] <xnox> true.
[16:34] <xnox> but old one might be invalid at that point already. hm, need to transverse through this again.