IRC chat logs for #ltsp on irc.freenode.net (webchat)


Channel log from 27 April 2020   (all times are UTC)

00:08brcisna has joined IRC (brcisna!d8187617@mail.eazylivin.net)
00:08
<brcisna>
Hello is there anyone online available for help? Thank You
00:09
<vagrantc>
brcisna: just describe your problem and wait a while for a response
00:09
!ask
00:09
<ltspbot>
ask: Don't ask to ask a question, simply ask it, and if someone knows the answer, they'll respond. Please hang around for at least a full hour after asking a question, as not everybody constantly monitors the channel.
00:13
<brcisna>
OK, i am using debian Bullseye which i know is not supported but a few days ago in 5 days time there were two kernel updates long story short at login the keyboard and mouse are both frozen i cannot do a ctl-alt-f2 for example,, and no inputs to login, i have talked with alkis on this, today,, i the kernels updated from 5.4.x to 5.5.x just for some
00:13
examples. when i loop mount the client squash image all that is in the boot directory is still the older 5.4.x initrd etc. shoudnt the sqush image be a mirror of the server boot directory?.
00:14
<vagrantc>
sounds like an update step was missed?
00:15
<brcisna>
..I might add.. the new 5.5.1 & the 5.5.2 usr/lib modules are in the new genreated client image but not in the boot directory. I am showing my stupidity i know..
00:15
<vagrantc>
ltsp image /
00:16
oh
00:16
<brcisna>
hi vagranttc i have run ltsp image /
00:16
multiple times,,,
00:16
<vagrantc>
is your /boot partition a separate partition?
00:17
although, if /lib/modules contains the right things ... that shouldn't matter
00:17
<brcisna>
oppsss i think you are right i think i had to do an extra command like this way back,,,how do i mount that i'm sorry,,i dont remember
00:17
<vagrantc>
you seem to use a lot of
00:17
"," when you type
00:18
does this show you the "/" partition or the "/boot" partition: df /boot
00:18
?
00:18
<brcisna>
i think initially i had to run an extra command to get the boot patition mounted
00:18
<vagrantc>
split /boot partition should be supported, but who knows
00:19
ummmm.
00:19
grep /boot /etc/fstab
00:19
if you have important system partitions not mounted ... that's pretty much a good way to shoot oneself in the foot :/
00:20
that sounds like your first problem
00:20
which is unrelated to ltsp
00:20
<brcisna>
/boot was on /dev/sda2 during installationUUID=f88944d6-dfa9-4fb7-a015-1b00a499196e /boot ext2 defaults 0 2
00:22
i'm sorry i meant to get the boot directory initially setup for ltsp
00:22
<vagrantc>
and is your /boot partition currently mounted?
00:22
you shouldn't unmount it normally
00:23
brcisna: did that first line have a "#" in front of it?
00:23
<brcisna>
mount yields - /dev/sda2 on /boot type ext2 (rw,relatime)binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime)
00:24
<vagrantc>
when asking for help from someone, please reply with the actual commands people ask you to run :P
00:24
<brcisna>
ok
00:25
<vagrantc>
what do you get with: ls -l /sbin /bin
00:25
wild guess here..
00:26
<brcisna>
ls -l /sbin /binlrwxrwxrwx 1 root root 7 Feb 20 13:28 /bin -> usr/binlrwxrwxrwx 1 root root 8 Feb 20 13:28 /sbin -> usr/sbin
00:26
<vagrantc>
and ls -l /lib/modules/
00:26
for some reason your cut-and-paste is not formatting things correctly :/
00:27
which leaves me wondering if i'm seeing what you're seeing
00:28
<brcisna>
ls -l /lib/modules/total 16drwxr-xr-x 2 root root 4096 Apr 25 10:12 5.3.0-2-amd64drwxr-xr-x 3 root root 4096 Apr 26 08:00 5.4.0-4-amd64drwxr-xr-x 3 root root 4096 Apr 15 07:57 5.5.0-1-amd64drwxr-xr-x 4 root root 4096 Apr 26 08:01 5.5.0-2-amd64
00:28
<vagrantc>
you've got a usrmerge system, though ... *hopefully* that isn't causing issues
00:28
uname -a
00:28
<brcisna>
uname -aLinux server1 5.5.0-2-amd64 #1 SMP Debian 5.5.17-1 (2020-04-15) x86_64 GNU/Linux
00:29
<vagrantc>
i'd uninstall your older kernels and rebuild the image ...
00:29
if the current kernel is running ok
00:29
<brcisna>
vangrantec i tried to copy/paste from terminal into gedit still weird formatting i apologize
00:29
<vagrantc>
why copy into gedit?
00:30
just copy directly into your irc client
00:30
<brcisna>
i thought maybe would straighten out formatting but obviously no change sorry
00:30
i was from terminal
00:30
<vagrantc>
so ... if you feel confident the current running kernel is working ok: sudo apt --purge linux-image-5.3 linux-image-5.4
00:31
also, do you have any packages that are not yet upgraded?
00:31
<brcisna>
i just run apt update apt upgrade nothing new as of a couple hours ago
00:32
<vagrantc>
ok
00:32
oops
00:32
sudo apt --purge autoremove linux-image-5.3 linux-image-5.4
00:32
oh!
00:32
nevermind...
00:33
that should leave two 5.5 kernels ...
00:33
may as well purge the old 5.5.x kernel too
00:33
<brcisna>
ok that is the two i currectly have in boot directory on the 'new' client image the server contains the 5.5-1 & 5,5-2
00:34
<vagrantc>
sudo apt --purge autoremove linux-image-5.3 linux-image-5.4 linux-image-5.5.0-1
00:34
sudo ltsp image /
00:34
does your /boot and /lib/modules contain the same versions?
00:35
with what you were saying about your /boot partition ... makes me worry you did a kernel upgrade without /boot mounted or something, and that might leave you in a very inconsistant state
00:35
<brcisna>
right now no,that is what i was trying to explain the 5.5.x has two in the usr/lib/modules but NO 5.5.x in boot directory
00:36
<vagrantc>
i'm just asking about the server, throw away your old broken ltsp image
00:36
<brcisna>
ok yes the 5.5.x is in both /boot & /usr/lib/modules
00:36
on server
00:37
<vagrantc>
and you've removed the old kernels?
00:37
so you have precisely one /boot/vmlinuz-5.5* and one /lib/modules/5.5.* ?
00:38
<brcisna>
ls -la /boottotal 134973drwxr-xr-x 5 root root 1024 Apr 25 10:13 .drwxr-xr-x 23 root root 4096 Apr 25 10:12 ..-rw-r--r-- 1 root root 225981 Mar 30 16:06 config-5.5.0-1-amd64-rw-r--r-- 1 root root 226399 Apr 14 21:37 config-5.5.0-2-amd64drwxr-xr-x 4 root root 1024 Apr 26 09:29 grub-rw-r--r-- 1 root root 58616722 Apr 15 07:58
00:38
initrd.img-5.5.0-1-amd64-rw-r--r-- 1 root root 58619309 Apr 25 10:13 initrd.img-5.5.0-2-amd64-rw-r--r-- 1 root root 119692 Feb 21 06:53 ldlinux.c32drwx------ 2 root root 12288 Feb 20 13:28 lost+found-rw-r--r-- 1 root root 42899 Feb 21 06:53 pxelinux.0drwxr-xr-x 2 root root 1024 Feb 21 06:53 pxelinux.cfg-rw-r--r-- 1 root root
00:38
4136684 Mar 30 16:06 System.map-5.5.0-1-amd64-rw-r--r-- 1 root root 4141267 Apr 14 21:37 System.map-5.5.0-2-amd64-rw-r--r-- 1 root root 5750512 Mar 30 16:06 vmlinuz-5.5.0-1-amd64-rw-r--r-- 1 root root 5762800 Apr 14 21:37 vmlinuz-5.5.0-2-amd64
00:39
ls -la /usr/lib/modules/total 32drwxr-xr-x 6 root root 4096 Apr 23 09:32 .drwxr-xr-x 164 root root 12288 Apr 25 10:12 ..drwxr-xr-x 2 root root 4096 Apr 25 10:12 5.3.0-2-amd64drwxr-xr-x 3 root root 4096 Apr 26 08:00 5.4.0-4-amd64drwxr-xr-x 3 root root 4096 Apr 15 07:57 5.5.0-1-amd64drwxr-xr-x 4 root root 4096 Apr 26 08:01
00:39
5.5.0-2-amd64
00:41
<vagrantc>
sounds like you haven't removed the old kernels?
00:41
and ...
00:41
!pastebin | echo brcisna
00:41
<ltspbot>
brcisna pastebin: see !paste
00:41
<vagrantc>
!paste | echo brcisna
00:41
<ltspbot>
brcisna paste: To avoid channel flooding, please upload text longer than 3 lines to http://paste.debian.net. Don't forget to paste the resulting URL here.
00:42
<brcisna>
ok i need to explain better when the two new kernels came in i got error /boot patition full, so had to do an autoremove
00:42
<vagrantc>
brcisna: please run: sudo apt --purge autoremove linux-image-5.5.0-1
00:42
how big is your /boot ?
00:42
df -h /boot
00:42
<brcisna>
and apt autoremoved two of the older kernels
00:45
<vagrantc>
so, have you removed all but the one running kernel?
00:45
let's try to get to a cleaner slate here...
00:45
<brcisna>
237 mb /boot
00:46
ok i only removed what apt autoremoved removed
00:46
<vagrantc>
oh ... i fear debian may default to a small /boot partition, doesn't it?
00:46
<brcisna>
i have not removed any since we started here
00:46
<vagrantc>
brcisna: please run: sudo apt --purge autoremove linux-image-5.5.0-1
00:46
<brcisna>
yes this is default
00:46
ok will do
00:47
<vagrantc>
i should get the bumped in newer versions of the installer ... i never use the default partition layout ... and forget about that bug
00:48
<brcisna>
Unable to locate package linux-image-5.5.0-1
00:49
<vagrantc>
dpkg -l linux-image-'*'
00:50
oh, maybe apt no longer does regexps implicitly ...
00:50
brcisna: please run: sudo apt --purge autoremove linux-image-5.5.0-1-amd64
00:51
<brcisna>
ok done
00:53
<vagrantc>
whew/
00:53
.
00:53
:)
00:53
ok ... now rebuild the image
00:53
sudo ltsp image /
00:54
<brcisna>
ok will do
00:54
<vagrantc>
if you get any warnings, please paste to a paste service, not directly to irc
00:55
<brcisna>
ok thanks will do
00:57
vagrantc while this image is building i might add i am on the client i named an old working image so if i reboot client after this image builds i may be gone until i do the renming on client image hope this makes sense.
00:57
ok image is rebuilt no errors
00:58
vagrantc i am curious after this rebuilds shouldnt the 5.5-2 be apperaing in the client image in /boot partition?
00:59
<vagrantc>
oh!
00:59
brcisna: yeah, let's check what's in the image
01:00
<brcisna>
i am sshd into server from client this messes something up?
01:00
<vagrantc>
you'll also need to update the initrd, i think... just to be sure
01:00
brcisna: it does make troubleshooting harder if it doesn't come back!
01:00
brcisna: sorry, should have asked more
01:01
brcisna: so, you still need to run: sudo ltsp initrd
01:01
just to be sure...
01:01
<brcisna>
ok will do
01:01
tahnk you
01:01
<vagrantc>
and ltsp ipxe
01:03
just to make sure i don't miss anyything, i usually do: sudo ltsp dnsmasq && sudo ltsp image / && sudo ltsp ipxe && sudo ltsp nfs && sudo ltsp initrd
01:03
<brcisna>
ok i run those commands
01:03
two commands
01:03
<vagrantc>
most of those commands are safe to re-run (although "ltsp image" is expensive)
01:03
<brcisna>
i run the two commands you wanted should i try a reboot?
01:04
<vagrantc>
let's hope for good things :)
01:04
<brcisna>
yes!!!
01:04
<vagrantc>
do you have a different client to try first?
01:04
<brcisna>
no i dont i can boot from hard disk if bombs and x2go to server in basement rename back to working image OK?
01:05
<vagrantc>
ok
01:05
<brcisna>
i know!! i can remote to server and try my vurtualbox image from here hang on please
01:05
<vagrantc>
we could also manually mount the image and check first?
01:05
<brcisna>
ok tell me how to mount image please
01:06
<vagrantc>
sudo mount -o loop /path/to/ltsp/x86_64.img /mnt
01:06
<brcisna>
vangrantc i had a mild brain anurism about 6 months ago so i am very slow i apologize
01:06
<vagrantc>
maybe the images are in /srv/ltsp/images ?
01:06
brcisna: sorry if i got impatient for a bit
01:06
<brcisna>
yes let me try and mount it will take me a bit i can do that i would like to see contents of /boot on client image
01:20
vangrantc looking at the client image the /boot dir containes the old 5.3.0-2 & 5.4.0-4 initrd system map vmlinuz NO 5.5.0-2
01:22
<vagrantc>
this seems highly improbable.
01:22
what's the output from "sudo ltsp image /"
01:22
?
01:24
<brcisna>
http://paste.debian.net/1143235/
01:24
running now
01:25
uh oh i did not umount that image?
01:31
<vagrantc>
unmount it...
01:31
<brcisna>
vagrantc i might add this setup is on a hardware dell perc raid dont know if that has any impact on this
01:32
ok unmounted
01:33
http://paste.debian.net/1143236/
01:33
full ltsp image /
01:33
output
01:34
<vagrantc>
hrm.
01:37
<brcisna>
kind of a crazy idea i wonder if i run the ltsp image / at server console with client booted?
01:37
without client booted?
01:38
vagrantc i am almost certain when i set this up initially alkis had me do an extra command before i run the ltsp image / command? that was a while back and several kernel updates in between just some extra info
01:38
i certainly cant remeber at all what is was.
01:39* vagrantc has an idea
01:40
<vagrantc>
it'll take me a moment to sort it out, though
01:41
<brcisna>
ok tahnk you for being so helpful
01:45
<vagrantc>
the NFS mount might be holding the inode open ...
01:45
if you remove the old image first ... it might crash your client
01:45
i was looking for a way to write the image to a new file to test that theory non-destructively
01:46
alternately ... just move the old image aside
01:46
<brcisna>
ok i now have the new image and the x86_64.img client still works as long as i dont reboot
01:47
i meant to say x86_64.img.old
01:48
you are saying shut off nfs?
01:49
<vagrantc>
no
01:49
ls /srv/ltsp/images
01:49
what's in there?
01:50
mount | grep loop
01:50
also ... to see if you still have it mounted anywhere
01:50
<brcisna>
x86_64.img x86_64.img.old
01:50
no it is not mounted at mount i checked
01:51
<vagrantc>
ok ... remove /srv/ltsp/images/x86_64.img
01:51
<brcisna>
ok
01:51
<vagrantc>
and now ...
01:51
and ... sudo ltsp image /
01:52
you're *sure* there's nothing mounted at /mnt ?
01:52
or mounted anywhere else?
01:52
and then the question is ... how are you sure? how can you make me sure? :)
01:53
<brcisna>
opps cant say for sure.shoud i disconnect the client do the sudo ltsp image / at console?
01:53
i deleted the /srv/ltsp/images/x86_64.img
01:54
that is whta has me pizzuled also my brain process now is very slow and muffled
01:55
let me check at mnt
01:55
<vagrantc>
mount | grep loop
01:56
mountpoint /mnt
01:56
mount | grep /mnt
01:57
df -h /mnt
01:57
no need to run them all ... all various ways to check :)
01:57
<brcisna>
http://paste.debian.net/1143238/
01:57
sudo mount
01:57
mount | grep /mnt
01:57
,,nothing returned
01:58
<vagrantc>
no need to run "sudo mount"
01:58
that's promising :)
01:58
mount will do
01:58
<brcisna>
mount | grep /mnt,,nothing returned
01:58
<vagrantc>
yup
01:59
how about "mount | grep loop" ?
01:59
<brcisna>
mount | grep loop nothing returned
02:00
<vagrantc>
yay
02:00
ok, i think we've determined that none of the images are mounted
02:00
and /srv/ltsp/images/x86_64.img is really gone?
02:02
<brcisna>
vagrantc this looks odd now the srv/ltsp/images keepmind i added the one directory images_BU just a while ago but have a look at the pastebin im going to send?
02:03
<vagrantc>
will look
02:04
<brcisna>
http://paste.debian.net/1143240/
02:05
<vagrantc>
i'd recommend moving the image_BU directory somewhere else ... say ... mv /srv/ltsp/images/image_BU /srv/ltsp/
02:05
<brcisna>
when i run that command just a few minutes ago the other two dirs did not show?
02:05
ok will do
02:06
done
02:07
<vagrantc>
ok ... now re-run ltsp image: sudo ltsp image /
02:07
and then we
02:07
we're either going to be happy or pulling out hair :)
02:07
<brcisna>
vagrantc i wanted to add, it seem when that ltsp image / command runs it gets about halfway done then it just is done boom! i know it always speeds up as the build progresses but now it almost seem too fast
02:08
ok i will rerun that command
02:08
<vagrantc>
some things are optimized a bit
02:09
if we don't return to a good image ... i'll see if i can reproduce the issue on a virtual machine
02:10
<brcisna>
vagrantc keep in mind this is debian bullseye i know it is not supported
02:10
i only installed it for a lot of multimedia updates
02:10
<vagrantc>
i'm the ltsp maintainer in Debian, so i'm vested in it working :)
02:10
<brcisna>
ok cross fingers
02:10
<vagrantc>
not that i've really used ltsp for years ...
02:11
<brcisna>
ok ltsp image / done you want me to put a paste bin so you can have a look see at the terminal output?
02:13
<vagrantc>
ok, so that produced /srv/ltsp/images/x86_64.img ?
02:15
<brcisna>
-rw-r--r-- 1 root root 4324155392 Apr 26 21:10 x86_64.img
02:16
should i try and loop mount it to look at /boot dir?
02:18
<vagrantc>
yes
02:18
#sudo mount -o loop /srv/ltsp/images/x86_64.img /mnt
02:19
first look at /mnt and make sure there's nothing there already
02:19
ls /mnt
02:19* vagrantc hopes this was just a fluke caused by weird issues with /boot
02:19
<vagrantc>
e.g. you're /boot full issue or whatever
02:20
if it doesn't fix it ... i have another idea what to look at
02:20
<brcisna>
ls /mnt nothing
02:20
<vagrantc>
and a bug to report upstream
02:20
:)
02:20
ok
02:23
<brcisna>
vagrantc the mounted image /boot still contains only the older kernel intrd system conig, no 5.5.0-2
02:24
you want me to do an ls -la of mounted boot or will that work
02:24
<vagrantc>
ok, next theory
02:24
sudo umount /boot
02:24
and *then* ... ls /boot
02:24
<brcisna>
ok
02:25
<vagrantc>
when you say "mounted image /boot" you mean /mnt/boot ?
02:26
<brcisna>
http://paste.debian.net/1143242/
02:26
yes /mnt/boot sorry
02:26
<vagrantc>
ok! my theory is confirmed.
02:26
partially, at least
02:26
<brcisna>
i run the two commands you mentioned then pastebin output
02:26
<vagrantc>
ok ...
02:26
sudo mv /boot/ /boot.evil
02:26
sudo mkdir -p /boot
02:27
sudo mount /boot
02:27
sudo umount /mnt # if you haven't already
02:27
sudo rm /srv/ltsp/images/x86_64.img
02:27
sudo ltsp image /
02:28
<brcisna>
vagrant you ment on server correct
02:28
<vagrantc>
i'm *hoping* that will produce an image with both a /boot with the correct files and /boot.evil with the old files
02:28
yes
02:28
on the server
02:28
<brcisna>
wehhwwwww...
02:29
those commands on server /boot yes??
02:29
<vagrantc>
yes
02:29
<brcisna>
ok hang on
02:29
<vagrantc>
what irc client are you using?
02:30
just curious due to the cut-and-paste issues
02:30
<brcisna>
whatever alkis sent me link for,web broweser chrome
02:30
<vagrantc>
ah, got it
02:30
<brcisna>
vagramtc i am showing my stupidity wont the server have a blank boot now?
02:31
<vagrantc>
it should when you've unmounted it!
02:31
not have old files leftoveer from some old installation
02:31
<brcisna>
yes but i mean how willt the server boot,,i am sorry for being so dense?
02:31
this is on server not client image
02:31
<vagrantc>
it's booting off of /dev/sda1 ... but you have leftover fiels installed on the lvm root
02:32
<brcisna>
oh ok,thank you
02:32
let me run those commands
02:32
<vagrantc>
let's double-check some things first
02:32
mountpoint /boot
02:33
make sure it's not a mountpoint
02:34
<brcisna>
the ltsp image / is running now OK?
02:35
<vagrantc>
and /boot is mounted with the new files? and /boot.evil contains the old files?
02:35
<brcisna>
let me look
02:36
wheewww yes! you had me worried the laest kernel stuff is in /boot on server
02:37
vgrant i just looked i dont see boot.evil?
02:37
<vagrantc>
ok ... then when it's done ... we'll mount the image at /mnt and check /mnt/boot
02:37
brcisna: you must have missed the commands?
02:38
<brcisna>
let me look i think i run that let me look in terminal
02:39
sudo mv /boot/ /boot.evil in terminal no errors
02:39
let me look again
02:40
ok refreshed i see boot.evil
02:40
<vagrantc>
https://paste.debian.net/1143245/
02:41
<brcisna>
i am using webmin in conjunction with sshing
02:41
<vagrantc>
by the end of that, /boot should just be new files, and /boot.evil should have the old files
02:41
ouch!
02:41* vagrantc woudl recommend sticking with ssh
02:41
<brcisna>
ok i will mount the new image correct?
02:41
<vagrantc>
sure
02:42
that last paste has all the commands in an order that should work, if you accidentally skipped a step
02:42
<brcisna>
could you do command for mount loop?
02:42
<vagrantc>
it's in there
02:42
<brcisna>
ok
02:42
<vagrantc>
sudo mount -o loop /srv/ltsp/images/x86_64.img /mnt
02:42
just to be sure :)
02:44
webmin was removed from debian in 2006 due to security issues ... how did you even install it?
02:44
<brcisna>
hhmm ls /mnt/boot is empty?
02:45
vagrantc the client image also contains the boot.evil dir? i guess is to be expected but / boot is totally empty
02:46
<vagrantc>
ok!
02:46
we have a genuine bug ... worse than i had hoped, but at least i understand what's going on more-or-less
02:47
brcisna: it's a little tricky, but if you could update your server to boot directly off of grub, that would workaround the problem
02:47
modern versions of grub are able to read lvm partitions
02:48
<brcisna>
vagrantc i think using the dell perc raid may be a part of this looking back
02:48
<vagrantc>
i don't recall off the top of my head what's needed and just how tricky that is
02:48
it's not impossible
02:49
<brcisna>
ok let me ask if i replace my good working client image back at /srv/ltsp/images/* my client will still boot , yes?
02:49
<vagrantc>
hope so
02:49
you might have to re-run the various ltsp commands
02:50
how much do you have invested in this installation?
02:50
<brcisna>
ok so you want me to do a search of old grub?
02:50
<vagrantc>
it might be easier to reinstall
02:50
i don't normally suggest that ... but there are enough weird issues
02:50
<brcisna>
i always that i was using grub to boot i see brub... at bootup.
02:50
grub
02:51
<vagrantc>
it shouldn't be terribly hard to switch to grub booting ... but that has a moderately high risk of making the system unbootable and i don't have more time to walk you through it
02:52
unbootable in the sense of requiring a recovery disk or something...
02:52
<brcisna>
i understand i appreciate all you have done
02:52
<vagrantc>
not permanently broken
02:52
er, grub with lvm support
02:52
i did it a while back on a machine i had partitioned similar to yours and it wasn't hard, but i don't know it well
02:52
<brcisna>
let me ask do you think i would be better off not using lvm?
02:53
<vagrantc>
if you reinstall without lvm, then there will be no separate boot partition ... for simplicity, yeah, that's a good way to go
02:53
and it works around this bug
02:53
<brcisna>
ok thank you that is what ill do.
02:54
ok thank you makes sense now, i am not very smart on this
02:54
<vagrantc>
brcisna: could you follow-up with a bug report ... the problem is it doesn't support a separate /boot partition
02:54
i had *thought* that was fixed ... but apparently needs more work
02:54
<brcisna>
ok i will explain as best i can
02:55
<vagrantc>
brcisna: you can even cut-and-paste my explanation :)
02:55
<brcisna>
you are saying the ltsp image / command?
02:55
to ltsp issues?
02:55
<vagrantc>
yeah, "ltsp image /" does not successfully detect that you have a boot partition and does not include it in the image
02:55
https://github.com/ltsp/ltsp/issues
02:56
<brcisna>
ok will do am hoping the client will boot after i place the image back
02:56
will do vagrant thank you much
02:56
<vagrantc>
good luck, gotta head out
02:56
<brcisna>
thanks a million good night
02:56
<vagrantc>
but if you reinstall, just go with "all files in one partition" if you're using debian-installer
02:57
i'm glad we at least figured out the nature of the problem
02:57
if not a perfect fix yet
02:57
alkisg: pinging you about this too ^^
02:57
<brcisna>
thanks a bunch again
02:58
will do installer
02:58
no lvm
02:58* vagrantc waves
02:58vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
02:58brcisna has left IRC (brcisna!d8187617@mail.eazylivin.net, Remote host closed the connection)
02:58
<alkisg>
Meh
02:59* alkisg got here 5 seconds too late :)
02:59
<alkisg>
!boot
02:59
<ltspbot>
I do not know about 'boot', but I do know about these similar topics: 'BOOTPROMPT_OPTS', 'boot-partition', 'bootfloppy', 'local-boot', 'panic-reboot'
02:59
<alkisg>
!boot-partition
02:59
<ltspbot>
boot-partition: If you're using a separate partition for /boot, you need to define it like e.g. "ltsp image /,,/boot,subdir=boot". See "man ltsp ipxe" for more on "advanced image sources".
02:59
<alkisg>
That's all that was missing there :)
03:00vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100e)
03:00
<alkisg>
!boot-partition | echo vagrantc
03:00
<ltspbot>
vagrantc boot-partition: If you're using a separate partition for /boot, you need to define it like e.g. "ltsp image /,,/boot,subdir=boot". See "man ltsp ipxe" for more on "advanced image sources".
03:01
<vagrantc>
https://github.com/ltsp/ltsp/issues/105
03:01
oh
03:01* alkisg comments in github about it, and heads back to bed :D
03:01
<vagrantc>
wow
03:01
heh
03:01
<alkisg>
;)
03:01* vagrantc waves again
03:01vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Client Quit)
03:02brcisna has joined IRC (brcisna!d8187617@mail.eazylivin.net)
03:02
<alkisg>
!boot-partition | echo brcisna
03:02
<ltspbot>
brcisna boot-partition: If you're using a separate partition for /boot, you need to define it like e.g. "ltsp image /,,/boot,subdir=boot". See "man ltsp ipxe" for more on "advanced image sources".
03:02* alkisg waves and heads back to bed...
03:03
<brcisna>
ltspbot thank you
03:03
<alkisg>
This is a bot
03:03
I invoked its notes to help you
03:03
ltspbot is not a person
03:03
<brcisna>
hi alkis let melook i appreciate the help
03:03
<alkisg>
Hi, I'm going back to bed, will be up in a couple of hours
03:03
:)
03:03
Do that ^ command though
03:03
<brcisna>
ok thank you much
03:05
!boot-partition | echo command not found
03:05
<ltspbot>
command not found boot-partition: If you're using a separate partition for /boot, you need to define it like e.g. "ltsp image /,,/boot,subdir=boot". See "man ltsp ipxe" for more on "advanced image sources".
03:06
<alkisg>
brcisna: just this:
03:06
ltsp image /,,/boot,subdir=boot
03:06
Run this on your server, then reboot client
03:06
<brcisna>
ok thank you i will try this get to bed
03:21brcisna has left IRC (brcisna!d8187617@mail.eazylivin.net, Remote host closed the connection)
05:01statler has joined IRC (statler!~Georg@p54897796.dip0.t-ipconnect.de)
05:20zerkalo has left IRC (zerkalo!myricae@gateway/shell/hashbang/x-ibcjafgahrzxjhij, Ping timeout: 265 seconds)
05:21zerkalo has joined IRC (zerkalo!myricae@gateway/shell/hashbang/x-yzvjyzlscxwsyfzj)
05:51statler has left IRC (statler!~Georg@p54897796.dip0.t-ipconnect.de, Quit: cu @ll)
07:00woernie has joined IRC (woernie!~werner@p5DDEC5BE.dip0.t-ipconnect.de)
07:30woernie has left IRC (woernie!~werner@p5DDEC5BE.dip0.t-ipconnect.de, Remote host closed the connection)
07:31woernie has joined IRC (woernie!~werner@p5DDEC5BE.dip0.t-ipconnect.de)
07:39
<Hyperbyte>
Good morning. :-) Is there anything I need to take into account when considering upgrading my fat client servers from 18.04 to 20.04?
07:39
<alkisg>
Only that it's a completely new LTSP so that you need to read the docs before installing
07:39
!install
07:39
<ltspbot>
install: To install LTSP: https://ltsp.org/docs/installation/
08:03RaphGro has joined IRC (RaphGro!~raphgro@fedora/raphgro)
08:04gdi2k has joined IRC (gdi2k!~gdi2k@58.69.160.27)
10:03nikoh77_ has joined IRC (nikoh77_!~nikoh77@93-55-122-94.ip263.fastwebnet.it)
10:24nikoh_77 has joined IRC (nikoh_77!~nikoh77@93-55-122-94.ip263.fastwebnet.it)
10:26nikoh77 has left IRC (nikoh77!~nikoh77@79.9.135.148, Ping timeout: 240 seconds)
10:43
<nikoh77_>
hi guys, I use ltsp5 for several years without problems, I would like to switch to the new version, is possible to upgrade without new/fresh install (without any risks)?
11:00gdi2k has left IRC (gdi2k!~gdi2k@58.69.160.27, Quit: Leaving)
11:02alkisg_web has joined IRC (alkisg_web!6db2c16e@109-178-193-110.pat.ren.cosmote.net)
11:05
<alkisg_web>
nikoh, you can upgrade ubuntu, but you need to remove the old ltsp and install the new one
11:05
!install
11:05
<ltspbot>
install: To install LTSP: https://ltsp.org/docs/installation/
11:07
<alkisg_web>
Also note that the new ltsp doesn't support thin clients
11:07
<nikoh77_>
ok, so i save my data and my os right?
11:07
<alkisg_web>
Yes you dont need to format
11:07
<nikoh77_>
ok
11:08
only fat clients?
11:08
<alkisg_web>
Yes, and remote desktop
11:10adrianor1 has joined IRC (adrianor1!~adrianorg@191.32.102.218)
11:14adrianorg has left IRC (adrianorg!~adrianorg@177.156.224.9, Ping timeout: 256 seconds)
11:21
<nikoh77_>
Remote desktop? VNC?
11:22
<alkisg_web>
Vnc, rdp,x2go, remote xorg,whatever you want to use
11:26
<nikoh77_>
ok.
11:26
just other question ;-)
11:27
do you know if there is a way to pxe booting from a mac?
11:28
<alkisg_web>
I don't use macs, from what i heard they use efi and intel cpus so it should be easy
11:29
Dont they have pxe boot in their uefi settings?
11:42woernie has left IRC (woernie!~werner@p5DDEC5BE.dip0.t-ipconnect.de, Ping timeout: 260 seconds)
11:42woernie has joined IRC (woernie!~werner@p5DDEC5BE.dip0.t-ipconnect.de)
11:44alkisg_web has left IRC (alkisg_web!6db2c16e@109-178-193-110.pat.ren.cosmote.net, Remote host closed the connection)
11:46
<nikoh77_>
alkisg: no
12:06
alkisg: ok, thanks, i would want upgrade in a few days..
12:06
see you soon ;-)
12:06
P.S. do you have a patreon account?
12:20
<alkisg>
nikoh77_: nah, just my paypal account, alkisg at gmail, thank you
12:21
LTSP doesn't receive contributions frequently, so it's not worth the hassle to get to patreon...
12:22
nikoh77_: https://wiki.fogproject.org/wiki/index.php/FOG_on_a_MAC does mention some ways to netboot macs...
12:26nikoh77_ has left IRC (nikoh77_!~nikoh77@93-55-122-94.ip263.fastwebnet.it, )
13:14danboid has joined IRC (danboid!~ISDADS\sg@cpc126962-macc4-2-0-cust227.1-3.cable.virginm.net)
13:18
<danboid>
What ports are required to be opened for LTSP to function over the net?
13:19
Is this list correct? https://help.ubuntu.com/community/UbuntuLTSP/LTSPFirewall
13:20
alkisg, ^^
13:28
<alkisg>
danboid: no
13:28
You need DHCP, TFTP, SSH, NFS
13:28
Well at least for the new LTSP...
13:29
<danboid>
Is this documented online somewhere? I did have a quick search before I asked :)
13:29
<alkisg>
No, but feel free to start a wiki page about it
13:29
<danboid>
alkisg, Actually I will if I ever get this new LTSP server
13:33
<alkisg>
It might be best to use a vpn like wireguard if you want it over unsafe net though
13:35GodFather has joined IRC (GodFather!~rcc@d53-64-7-141.nap.wideopenwest.com)
13:45
<danboid>
alkisg, Yes, of course
13:49
Have you used Wireguard much? I've yet to try it
13:49
I know Ubuntu 20.04 supports it now
13:50
Have you tried the Windows wireguard client?
13:56
<alkisg>
danboid: I've tested it in 20.04, but not in windows
13:56
It seemed rather simple and efficient
13:57
<danboid>
Good!
13:57
We would need the client to work well under Windows too if we were using wireguard
13:58
<alkisg>
Windows LTSP?
13:59
I meant, to use it for LTSP, not for Windows, but whatever suits you
13:59
<danboid>
Oh hold on
13:59
What am I thinking
13:59
How would wireguard help in booting a machine via PXE over the net?
14:00
You can't connect with wg to our network and then PXE boot the bare metal. VMs, fine
14:01
You were talking about PXE booting VMs right?
14:02
<alkisg>
danboid: using wireguard would allow you to open a single port in your firewall, and not expose all services to the whole internet
14:03
The client booting over WAN would stay the same
14:07GodFather has left IRC (GodFather!~rcc@d53-64-7-141.nap.wideopenwest.com, Ping timeout: 265 seconds)
14:17
<danboid>
So basically WAN booting of LTSP is only really safe and possible using VMs?
14:17
<alkisg>
Ehh no, that's completely unrelated to what I said
14:17
LTSP requires the services I mentioned, SSH, NFS, TFTP, DHCP
14:18
You may safely expose them over the internet, or you may not, depending on how you configure them
14:18
If you don't want to expose all of them, you create a VPN like wireguard, so all these services are encrypted and only the wireguard port is opened in your firewall
14:19
In all those, I didn't mention the word "VM". VMs are not related to these.
14:31alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
14:35alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
14:47GodFather has joined IRC (GodFather!~rcc@d53-64-7-141.nap.wideopenwest.com)
14:54GodFather has left IRC (GodFather!~rcc@d53-64-7-141.nap.wideopenwest.com, Ping timeout: 260 seconds)
14:58GodFather has joined IRC (GodFather!~rcc@d53-64-7-141.nap.wideopenwest.com)
15:03GodFather has left IRC (GodFather!~rcc@d53-64-7-141.nap.wideopenwest.com, Ping timeout: 260 seconds)
15:30danboid has left IRC (danboid!~ISDADS\sg@cpc126962-macc4-2-0-cust227.1-3.cable.virginm.net, Quit: Leaving)
16:14brcisna has joined IRC (brcisna!d8187617@mail.eazylivin.net)
16:21vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
16:22RaphGro has left IRC (RaphGro!~raphgro@fedora/raphgro, Ping timeout: 272 seconds)
16:23RaphGro has joined IRC (RaphGro!~raphgro@fedora/raphgro)
16:26hark has left IRC (hark!~hark@yavin.puscii.nl, *.net *.split)
16:32hark has joined IRC (hark!~hark@yavin.puscii.nl)
16:34brcisna has left IRC (brcisna!d8187617@mail.eazylivin.net, Ping timeout: 240 seconds)
17:13GodFather has joined IRC (GodFather!~rcc@d53-64-7-141.nap.wideopenwest.com)
17:26GodFather has left IRC (GodFather!~rcc@d53-64-7-141.nap.wideopenwest.com, *.net *.split)
17:26hark has left IRC (hark!~hark@yavin.puscii.nl, *.net *.split)
17:29GodFather has joined IRC (GodFather!~rcc@d53-64-7-141.nap.wideopenwest.com)
17:29hark has joined IRC (hark!~hark@yavin.puscii.nl)
18:09GodFather has left IRC (GodFather!~rcc@d53-64-7-141.nap.wideopenwest.com, Ping timeout: 264 seconds)
18:24RaphGro has left IRC (RaphGro!~raphgro@fedora/raphgro, Quit: Please remember your own message. It'll be read as soon as possible.)
18:27RaphGro has joined IRC (RaphGro!~raphgro@fedora/raphgro)
20:30samop has joined IRC (samop!5bf6e72e@91-246-231-46.dynamic.t-2.net)
20:30RaphGro has left IRC (RaphGro!~raphgro@fedora/raphgro, Quit: Please remember your own message. It'll be read as soon as possible.)
20:31samop is now known as samopeni
20:47RaphGro has joined IRC (RaphGro!~raphgro@fedora/raphgro)
20:58RaphGro has left IRC (RaphGro!~raphgro@fedora/raphgro, Quit: Please remember your own message. It'll be read as soon as possible.)
21:22sunweaver has left IRC (sunweaver!~sunweaver@fylgja.das-netzwerkteam.de, Ping timeout: 240 seconds)
21:22sunweaver has joined IRC (sunweaver!~sunweaver@fylgja.das-netzwerkteam.de)
21:25RaphGro has joined IRC (RaphGro!~raphgro@fedora/raphgro)
21:26RaphGro has left IRC (RaphGro!~raphgro@fedora/raphgro, Client Quit)