Anyone else’s 5070 soft “die” on ThinOS 9.1?

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #83159
    Avatarvfwdit
    Participant
    • Total Post: 23
    • Regular Joe
    • ★★

    We’ve had 3 units so far where the units will soft “die”.

    What I mean by this is that when you restart them, they’ll bring up the ThinOS desktop graphic and not do anything else.

    You can move your mouse to the left side and see the VDI menu and some options, but they’re all “locked” and, of course, you can’t unlock anything because passwords don’t work.

    When they soft die, the event log window and such doesn’t even pop up.  They literally just boot to the desktop graphic with nothing going on and access to that locked area on the left side.

    You don’t see the startup window or logs that happen usually, nor their attempt to check into WMS or anything.

    We can recover these units by pushing the image again VIA USB and then setting the WMS information again after they reboot.  Afterward, they’re functional, check in and so on like normal.  But yeah..  it’s annoying because now I feel I always have to have a spare unit ready to go in case another unit dies.

    Rebooting the “dead” unit does not resolve this issue.

    #83184
    Avatarvfwdit
    Participant
    • Total Post: 23
    • Regular Joe
    • ★★

    Well, I’m trying to post a YouTube video but it won’t post for some reason…

    Look on YouTube for the video ID: JDuzQcH_ZhU

    #83627
    ConfGenConfGen
    Keymaster
    • Total Post: 11270
    • Jedi Master
    • ★★★★★★★

    Never seen or heard of.
    Looks like the unit is moved in a different policy group with weird settings (although, I do not know how to achieve what you observe with a policy).

    CG

    #83832
    Avatarvfwdit
    Participant
    • Total Post: 23
    • Regular Joe
    • ★★

    It happened to a 4th unit yesterday, but this time it was a unit that is a Blast only Pentium unit.  (The one with 3 DisplayPort connectors.)

    Anyhow, I tried to USB Merlin to recover this machine and the flash took longer than usual.  Once it was done, I took the USB drive out and I attempted to restart the unit.  I was then greeted with this message:

    /etc/defaults/rc.conf: 745: Syntax error: “)” unexpected (expecting “fi”)
    Enter full pathname of shell or RETURN for /bin/sh:

    Basically the USB Merlin image on the site seemed to brick that machine.

    Upon further inspection of the USB Merlin image on the website for 9.1, the version posted for “ThinOS” and NOT “ThinOS PCoIP” actually contains the USB Merlin image for PCoIP.

    This seems to be another mistake from Dell.  They’ve put the USB Merlin image for ThinOS PCoIP 9.1 both for the PCoIP 5070 and the non PCoIP 5070.

    So, to recover this machine, I have to flash the ThinOS 8.6 USB Merlin image and upgrade it to 9.1 again because the ThinOS 9.1 Merlin image on the Dell support website is wrong.

    #87695
    Avatarbrian1020
    Participant
    • Total Post: 186
    • Jacked into The Matrix
    • ★★★★★★

    Try wiping the device in the Bios and then reimage from USB. I’ve had my 5070 and 5470 get in strange reboot loops when switching from WiFi disable on Enet up to Enet not detected WiFi enable would cause constant reboots even after resetting to factory. Resetting to factory and walking through the ThinOS 9.1 OOB setup if you would select WiFi for how your device connects to the internet as soon as you select the SSID and enter a password it would reboot, rinse and repeat.

    The only fix I found was a complete device wipe from the Bios where they make you confirm 4-5 times, “Are you sure you want to wipe?”  Re-enable boot from USB and turning off secure boot to image again to 8.6, upgrade to 9.1 and all problems and anomalies seem to go away for me after a full device wipe.

    Now if Dell could just make the USB Imaging Tool work with a current version of Windows or make it work from Ubuntu to actually make USB imaging sticks without a headache I would appreciate that. My current home version of Windows 10 is as up-to-date as you can get and USB Imaging tool never seems to work to make new imaging sticks.

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.