Thread: [Thinstation-general] ThinStation /mnt/nfs defaulting to vers=2
Brought to you by:
doncuppjr
From: Todd P. <pf...@rh...> - 2022-04-04 22:40:16
|
Hi ThinStation folks, I'm trying to use NFS for STORAGE_PATH in ThinStation-6. To support that, I've got these two lines in build.conf: module nfs package nfs and those seem to be sufficient to support an NFSv4 mount. I can do the intended NFS mount manually from the command line when the thinstation is booted and I've sshed in. The problem I have is that the /mnt/nfs entry in /etc/fstab is being generated like this: server:/thin /mnt/nfs nfs rsize=8192,wsize=8192,timeo=14,vers=2,intr 0 0 vers=2? Really? I don't recall using NFSv2 since the last millenium. Anyway, where do I change this? Is it a build.conf setting or a thinstation.conf.buildtime setting or do I have to find and modify some source file that should have been changed from vers=2 to vers=3 years ago. I'm netbooting so I could modify the initrd and make this change but I'd like to change the source that generates this fstab entry in initrd so that the change persists for future builds. In my case, I probably want vers=4 since ThinStation-6 seems to not support NFSv3 - this is output during build: Package : nfs Module: nfsv4 Package : nfs Module: nfsv3 Notice! Module nfsv3.ko not found for kernel 5.10.89TS Was this intentional, to remove NFSv3 support? As I wrote above, NFSv4 seems to be working fine manually. Thanks, Todd |
From: Todd P. <pf...@rh...> - 2022-04-04 22:47:10
|
Hi ThinStation folks, I'm running ThinStation-6, netbooting it via UEFI PXE, with the kernel and initrd loaded via HTTP. That's all working ok, albeit slower than I expected. The kernel vmlinuz file appears to load during boot in just a couple of seconds. After that the remainder of the boot process takes another minute or so, and for most of that time all I see on the screen are the pxe boot messages in the top-left of the screen: Fetching Netboot Image Loading kernel ... Loading initial ramdisk ... After about a minute I finally see the ThinStation yellow progress bar show up for a split-second and then it disappears and all I see is a black screen until the boot is completed and my desktop session is running. The initrd file is about 320MB so I wouldn't expect it to take more than a few seconds to load via http on a 1Gbps network. In fact, if I wget the same file from the running thinstation, it takes about 3 seconds. I also wouldn't expect the uncompressing of the initrd file and the remainder of the boot process to take as long as it is so I suspect something is going on that I can see because the boot process is mostly silent. What can I do to better visualize the boot process? I'm used to being able to press CTRL-ALT-Fn to get out of a linux graphical boot screen and see the kernel and init messages. I haven't found a way to do this with TS6 but maybe I'm missing something. Thanks, Todd |
From: Todd P. <pf...@rh...> - 2022-04-04 23:33:07
|
On Mon, 4 Apr 2022, Todd Pfaff wrote: > vers=2? I answered this question myself. The vers=2 comes from here under build: ./packages/netfiles/etc/init.d/filesystem-network: echo "$NET_NFS_SERVER /mnt/nfs nfs rsize=8192,wsize=8192,timeo=14,vers=2,intr 0 0" >> /etc/fstab So I can deal with that, but it'd be nice to see this changed in the package, unless some people really are still using NFSv2. My question about NFSv3 still stands. Thanks, Todd |
From: Don C. <don...@ya...> - 2022-04-05 14:03:59
|
I am not sure which boot loader you are using, but regardless, boot loaders often have to use interrupts to get things done. This makes them slower than a regular OS. I developed a technique for breaking the initrd up into two pieces. All the code required to boot is in the small piece about 29mb, and everything else in the second part. It's called fastboot. It's weird and makes things hard to debug, but it does speed up booting. You could add "vt.global_cursor_default=1 systemd.show_status=true rd.systemd.show_status=true" to your kernel cmd line. On Tuesday, April 5, 2022, 01:17:25 AM PDT, Todd Pfaff <pf...@rh...> wrote: Hi ThinStation folks, I'm running ThinStation-6, netbooting it via UEFI PXE, with the kernel and initrd loaded via HTTP. That's all working ok, albeit slower than I expected. The kernel vmlinuz file appears to load during boot in just a couple of seconds. After that the remainder of the boot process takes another minute or so, and for most of that time all I see on the screen are the pxe boot messages in the top-left of the screen: Fetching Netboot Image Loading kernel ... Loading initial ramdisk ... After about a minute I finally see the ThinStation yellow progress bar show up for a split-second and then it disappears and all I see is a black screen until the boot is completed and my desktop session is running. The initrd file is about 320MB so I wouldn't expect it to take more than a few seconds to load via http on a 1Gbps network. In fact, if I wget the same file from the running thinstation, it takes about 3 seconds. I also wouldn't expect the uncompressing of the initrd file and the remainder of the boot process to take as long as it is so I suspect something is going on that I can see because the boot process is mostly silent. What can I do to better visualize the boot process? I'm used to being able to press CTRL-ALT-Fn to get out of a linux graphical boot screen and see the kernel and init messages. I haven't found a way to do this with TS6 but maybe I'm missing something. Thanks, Todd _______________________________________________ Thinstation-general mailing list Thi...@li... https://lists.sourceforge.net/lists/listinfo/thinstation-general |
From: Todd P. <pf...@mc...> - 2022-04-05 16:25:57
|
Hi Don, Thanks for the response. I'll try the kernel cmd line options you suggested. The current hardware I'm testing is a new Dell Optiplex 3090 MFF, configured for UEFI PXE boot. I thought I was already using fastboot. However, now I'm not so sure. What files should I be able to see being requested from a client on my tftp or http servers? During the latest boot of my thinstation client I'm seeing this in my http access log: "GET /vmlinuz HTTP/1.1" 200 8256904 "-" "GRUB 2.03" "GET /initrd HTTP/1.1" 200 336131829 "-" "GRUB 2.03" "GET //thinstation.conf.network HTTP/1.1" 200 317 "-" "Wget" "GET //thinstation.hosts HTTP/1.1" 200 199 "-" "Wget" "GET //thinstation.conf.group-all HTTP/1.1" 200 - "-" "Wget" "GET //thinstation.conf-tc003 HTTP/1.1" 200 778 "-" "Wget" "GET //ssh_known_hosts HTTP/1.1" 404 213 "-" "Wget" Is that everything or should there be something else after initrd that I should see if fastboot is at play? I recalled seeing a lib.squash in the past, and found this in an earlier log entry before I made some changes yesterday: "GET /lib.squash HTTP/1.0" 200 315600896 "-" "Wget" Should I still be seeing this for every TS boot when fastboot is enabled, or am I conflating different mechanisms and this lib.squash has nothing to do with fastboot (in which case, when should I see lib.squash and when not)? I have this in my current build.conf: package overlayfs param fastboot and this for my current pxe boot grub2 menuentry: set http_host=192.168.1.1:8888 set http_path="" menuentry 'ThinStation' --class gnu-linux --class gnu --class os { echo 'Loading kernel ...' linuxefi (http,${http_host})${http_path}/vmlinuz console=tty0 LM=3 FASTBOOT_URL=http://${http_host}${http_path} echo 'Loading initial ramdisk ...' initrdefi (http,${http_host})${http_path}/initrd } Thanks, Todd On Tue, 5 Apr 2022, Don Cupp via Thinstation-general wrote: > I am not sure which boot loader you are using, but regardless, boot > loaders often have to use interrupts to get things done. This makes them > slower than a regular OS. I developed a technique for breaking the > initrd up into two pieces. All the code required to boot is in the small > piece about 29mb, and everything else in the second part. It's called > fastboot. It's weird and makes things hard to debug, but it does speed > up booting. > > You could add "vt.global_cursor_default=1 systemd.show_status=true > rd.systemd.show_status=true" to your kernel cmd line. > > > > > > > > > On Tuesday, April 5, 2022, 01:17:25 AM PDT, Todd Pfaff <pf...@rh...> wrote: > > > > > > Hi ThinStation folks, > > I'm running ThinStation-6, netbooting it via UEFI PXE, with the kernel and > initrd loaded via HTTP. That's all working ok, albeit slower than I > expected. > > The kernel vmlinuz file appears to load during boot in just a couple of > seconds. > > After that the remainder of the boot process takes another minute or so, > and for most of that time all I see on the screen are the pxe boot > messages in the top-left of the screen: > > Fetching Netboot Image > Loading kernel ... > Loading initial ramdisk ... > > > After about a minute I finally see the ThinStation yellow progress bar > show up for a split-second and then it disappears and all I see is a black > screen until the boot is completed and my desktop session is running. > > The initrd file is about 320MB so I wouldn't expect it to take more than a > few seconds to load via http on a 1Gbps network. In fact, if I wget the > same file from the running thinstation, it takes about 3 seconds. > > I also wouldn't expect the uncompressing of the initrd file and the > remainder of the boot process to take as long as it is so I suspect > something is going on that I can see because the boot process is mostly > silent. > > What can I do to better visualize the boot process? I'm used to being > able to press CTRL-ALT-Fn to get out of a linux graphical boot screen and > see the kernel and init messages. I haven't found a way to do this with > TS6 but maybe I'm missing something. > > > Thanks, > Todd > > > _______________________________________________ > Thinstation-general mailing list > Thi...@li... > https://lists.sourceforge.net/lists/listinfo/thinstation-general > > > _______________________________________________ > Thinstation-general mailing list > Thi...@li... > https://lists.sourceforge.net/lists/listinfo/thinstation-general |
From: Todd P. <pf...@rh...> - 2022-04-05 16:26:53
|
Doh! Now I see it. I must have inadvertently deleted "true" from my param fastboot line yesterday. I'll remove overlayfs, and test fastboot as true and lotsofmem. Thanks, Todd On Tue, 5 Apr 2022, Don Cupp wrote: > If fastboot is enabled, you will always transfer lib.squash. > It has two modes, true and lotsofmem. > Neither requires overlayfs > In true mode, the lib.squash archive is simply mounted in the right place, > and lots of new files are available. This uses the least amount of memory is > also the fastest booting, with a little per app launch lag. > In lotsofmem, the lib.squash archive is decompressed during boot. This uses > the most amount of memory, but still very little because it's linux. No per > app launch lag. > > |