Project

General

Profile

Actions

Bug #12974

closed

Typing anything into 1100/2100 recovery installer causes process to stop

Added by Ryan Coleman about 2 years ago. Updated 12 months ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Installer
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Release Notes:
Default
Affected Plus Version:
22.01
Affected Architecture:
SG-1100, SG-2100

Description

During the installation process the user is prompted to select a filesystem or type enter to install with ZFS.

However typing "enter" causes the installer to exit and reboot.

Select the file system to install (UFS/ZFS) or type enter to install with ZFS:

Suggest changing the language to reflect pressing enter rather than typing it.


Files

install_log.txt (792 Bytes) install_log.txt Ryan Coleman, 03/22/2022 01:46 PM
Actions #1

Updated by Kris Phillips almost 2 years ago

I'm not able to reproduce this. What serial emulator are you using? Have you tried Putty or Screen? I've seen this with certain macOS serial emulators before, but it works fine with others.

Actions #2

Updated by Ryan Coleman almost 2 years ago

Kris Phillips wrote in #note-1:

I'm not able to reproduce this. What serial emulator are you using? Have you tried Putty or Screen? I've seen this with certain macOS serial emulators before, but it works fine with others.

Every emulative path capable in Linux.

Follow the instructions and enter "enter" (as shown in the attached log) and it fails.
Enter anything NOT the {enter key}, ufs or zfs and it stops. It doesn't reject the entry, it exits.

Actions #3

Updated by Kris Phillips almost 2 years ago

Ryan Coleman wrote in #note-2:

Kris Phillips wrote in #note-1:

I'm not able to reproduce this. What serial emulator are you using? Have you tried Putty or Screen? I've seen this with certain macOS serial emulators before, but it works fine with others.

Every emulative path capable in Linux.

Follow the instructions and enter "enter" (as shown in the attached log) and it fails.
Enter anything NOT the {enter key}, ufs or zfs and it stops. It doesn't reject the entry, it exits.

Ryan,

I just went through a reinstall with a customer on an 1100 and hit "Enter" instead of typing something in and it defaults to ZFS and the mmcsd0. Can you provide a screencast recording or something showing what you're running into? I'm very interested in what's causing this in your case.

Actions #4

Updated by Ryan Coleman almost 2 years ago

Kris Phillips wrote in #note-3:

Ryan Coleman wrote in #note-2:

Kris Phillips wrote in #note-1:

I'm not able to reproduce this. What serial emulator are you using? Have you tried Putty or Screen? I've seen this with certain macOS serial emulators before, but it works fine with others.

Every emulative path capable in Linux.

Follow the instructions and enter "enter" (as shown in the attached log) and it fails.
Enter anything NOT the {enter key}, ufs or zfs and it stops. It doesn't reject the entry, it exits.

Ryan,

I just went through a reinstall with a customer on an 1100 and hit "Enter" instead of typing something in and it defaults to ZFS and the mmcsd0. Can you provide a screencast recording or something showing what you're running into? I'm very interested in what's causing this in your case.

Type "enter", rather than pressing the key, and it will fail.

If you get someone who reads the instructions literally they will type the letters E N T E and R in succession and press the key [enter] and it will shut down the installation on them.

This is issue has two parts:
1) The phrasing is wrong if the intention is to enter "A" or "B" or press a specific key.
2) It doesn't validate a bad input and completely fails.

Item 1 alone is an easy fix but it might be worthwhile to just kick it back to that prompt (if possible) when you enter something that is not valid.

Actions #5

Updated by Kris Phillips almost 2 years ago

Ryan Coleman wrote in #note-4:

Kris Phillips wrote in #note-3:

Ryan Coleman wrote in #note-2:

Kris Phillips wrote in #note-1:

I'm not able to reproduce this. What serial emulator are you using? Have you tried Putty or Screen? I've seen this with certain macOS serial emulators before, but it works fine with others.

Every emulative path capable in Linux.

Follow the instructions and enter "enter" (as shown in the attached log) and it fails.
Enter anything NOT the {enter key}, ufs or zfs and it stops. It doesn't reject the entry, it exits.

Ryan,

I just went through a reinstall with a customer on an 1100 and hit "Enter" instead of typing something in and it defaults to ZFS and the mmcsd0. Can you provide a screencast recording or something showing what you're running into? I'm very interested in what's causing this in your case.

Type "enter", rather than pressing the key, and it will fail.

If you get someone who reads the instructions literally they will type the letters E N T E and R in succession and press the key [enter] and it will shut down the installation on them.

This is issue has two parts:
1) The phrasing is wrong if the intention is to enter "A" or "B" or press a specific key.
2) It doesn't validate a bad input and completely fails.

Item 1 alone is an easy fix but it might be worthwhile to just kick it back to that prompt (if possible) when you enter something that is not valid.

Ryan,

I get what you're saying now. The wording could certainly be better here like "press enter" instead. That said, I don't think I've ever seen anyone take this literally like that.

Actions #6

Updated by Marcos M almost 2 years ago

The wording has been addressed with NG 7431. This issue can be left open to track the behavior issue itself, as it should likely re-prompt rather than exit.

Actions #7

Updated by Ryan Coleman almost 2 years ago

Marcos Mendoza wrote in #note-6:

The wording has been addressed with NG 7431. This issue can be left open to track the behavior issue itself, as it should likely re-prompt rather than exit.

Confirmed this has been address and works as programmed -- it will reboot the device on a bad entry. Any entry that is invalid fires a reboot.

Actions #8

Updated by Ryan Coleman about 1 year ago

  • Status changed from New to Closed

This should be closed. Updating to reflect.

Actions #9

Updated by Jim Pingle 12 months ago

  • Target version deleted (Plus-Next)
Actions

Also available in: Atom PDF