-
-
Notifications
You must be signed in to change notification settings - Fork 188
Errors Running mkmbrdrv
This is a page for errors that I encountered enroute to my NoMachine Terminal Server setup as documented here.
Encountered this error; apparently the download link structure at NoMachine has changed.
Per Doncuppjr's suggestion, I downloaded the NX client manually, and copied it into /thinstation/downloads (I couldn't use wget for the very reason that the build script failed: no link). The problem package was in there, so I knew I was in the right place.
This time the script didn't try to download with wget, but I still got the same error message. I thought it might be still trying to unzip the (original) problem file, so I deleted that one.
Saving to: './wget_tmp/nomachine-enterprise-client_6.11.2_1_x86_64.tar.gz
Apparently the NX client version is hard coded in the script? After looking at /ts/build/packages/nx/build/install, and not seeing how to redirect it to the file I downloaded, I renamed the new download to match the failed download:
sudo cp nomachine-enterprise-client_7.6.2_4_x86_64.tar.gz nomachine-enterprise-client_6.11.2_1_x86_64.tar.gz
This time, success!
As was noted here, the file name comes from /build/build.urls, so I could edit the param nxurl, but since I can't feed it the correct download url anyway, it's just as simple to rename the manually downloaded file as I did above.
I got a number of errors running the mkmbrdrv command, including...
blockdev: ioctl error on BLKRRPART: Device or resource busy
mount: /tmp/mkmbrdrv.yH4: special device /dev/sdc1 does not exist.
In most cases, removing the USB drive, and reinserting it in a different slot did the trick. I did have one bad USB drive, so make sure you have several on hand. I don't know what caused the 'mount' error, because running the fdisk command again gave the same output. Below is the output after a successful write to the USB drive.