IRC channel logs

2021-08-16.log

back to list of logs

<dragestil>i'm trying out hurd for the first time. following the instructions at https://www.gnu.org/software/hurd/hurd/running/qemu.html except substituing kvm with `qemu-system-x86_64 -enable-kvm`, i got put in the maintenance shell right away, apparently because of root system is read-only. does anyone know how i can fix it?
<damo22>i386 not x86_64
<damo22>qemu-system-i386 -M q35,accel=kvm -m 4096 -net user,hostfwd=tcp::8888-:22 -net nic -curses
<damo22>and pass the hdd image
<dragestil>i don't have qemu-system-i386
<dragestil>let me see if i can get one
<damo22>it may still work with x86_64 actually
<dragestil>i got qemu-system-i386, and ran the command in the qemu link above, but got the same error. i'm going to try your command
<damo22>can you paste a screenshot of the terminal when it fails
<dragestil>will do once your command has finished running
<damo22>?
<damo22>my command is to launch qemu
<dragestil>i assume it is not a good idea to boot the same image simultaneously with two qemu commands
<damo22>correct
<dragestil>now i'm getting a different error: start ext2fs: ext2fs: device:hd0s2: No such device or address
<damo22>you need to pass the hdd image
<damo22>on the end of the command
<dragestil>yeah i did
<dragestil>this is what i ran: qemu-system-i386 -M q35,accel=kvm -m 4096 -net user,hostfwd=tcp::8888-:22 -net nic -curses debian-hurd-20210219.img
<damo22>hmm you can try my full command:
<damo22>qemu-system-i386 -M q35,accel=kvm -m 4096 -net user,hostfwd=tcp::8888-:22 -net nic -curses -drive id=udisk,file=debian-hurd-20210219.img,format=raw,if=none -device ide-hd,drive=udisk,bootindex=1
<dragestil>ok
<dragestil>is there a way to exit the ncurses qemu run
<damo22>shutdown
<dragestil>without killing the containing terminal
<dragestil>i can't type anything there
<damo22>ctrl-alt-d
<dragestil>i'll just kill the terminal emulator then
<dragestil>ok
<dragestil>nope
<dragestil>no response
<damo22>ok
<damo22>strange
<dragestil>anyway, i killed the terminal emulator
<dragestil>i ran your full command and it seems to be stuck at the same place
<dragestil>would you like me to paste the whole screen
<damo22>stuck where
<damo22>yes
<damo22>can you pastebin it
<damo22>it should be text based using curses
<dragestil>yeah, one moment as i have to remove all the leading spaces
<dragestil> https://paste.debian.net/hidden/377df3e5/
<damo22>yeah looks like the config is incorrect and should be pointing to sd0s2
<damo22>instead of hd0s2
<dragestil>ok. https://paste.debian.net/hidden/40cc9637/
<dragestil>this is the result when i run the original command from the qemu page on hurd wiki, with an extra curses
<dragestil>looks like the issue is related to hd0s2 in this case too
<dragestil>original command with s/kvm/qemu-system-x86_64 -enable-kvm/ though i386 produces the same result iirc
<damo22>does grub appear at boot?
<dragestil>yes when running without -curses
<damo22>you can edit the config and root=/dev/sd0s2
<damo22>instead of hd0s2
<dragestil>in grub?
<damo22>hyes
<dragestil>ok let me try that
<dragestil>i replaced one occurrence of hd0s2 by sd0s2. now it complains "device:sd0s2: No such device or address". I'll try again to see whether i should prepend a /dev in the config
<dragestil>the part where i edited says "root=device:hd0s2"
<dragestil>changing it to root=device:/dev/sd0s2 result in the same error, I'll try root=/dev/sd0s2
<damo22>oh
<damo22>device:sd0s2
<damo22>just change h -> s
<dragestil>now it's showing a different error "ext2fs: /dev/sd0s2: gratuitous error"
<damo22>sorry
<dragestil>yes that's what i did in the first try
<dragestil>but i got the "device:sd0s2: No such device or address"
<dragestil>after just changing h->s
<damo22>oh ok
<damo22>it worked with h->s
<damo22>but your filesystem needs checking
<dragestil>why do you think it worked with h->s?
<damo22>did you get a root shell
<dragestil>no
<dragestil>when just doing h->s i got the same error as in https://paste.debian.net/hidden/377df3e5/
<dragestil>except h->s
<damo22> https://paste.debian.net/hidden/40cc9637/ well this shows that it was possible to boot but you needed to e2fsck the /dev/hd0s2
<dragestil>so shall i run `e2fsck /dev/hd0s2` in the maintenance shell?
<dragestil>is it possible that the image i downloaded is corrupt?
<damo22>its not corrupt, it just needs checking, ext2 is fragile
<damo22>it can happen easily if you dont clean shutdown and umount
<dragestil>ok
<dragestil>fixed one inode
<dragestil>yes, now it's working - i got to the login
<dragestil>thanks a lot
<damo22>yw
<dragestil>strange the -curses produce different errors from when you run without -curses
<damo22>you can run update-grub as root
<dragestil>why and what does that do
<dragestil>looks like the debian-hurd image does not have a gui
<dragestil>oh it does
<dragestil>i just needed to run startx
<damo22>it should update the grub config so you dont have to edit grub anually every boot
<dragestil>oh ok
<dragestil>well the problem was the file system fsck anyway
<damo22>ok
***roptat_ is now known as Guest5707
***Guest5707 is now known as roptat
***john__ is now known as gaqwas