Test the PBA results scroll too fast and most exit display to be out of view.

[xwcgilmore]

Hi,
Following instructions to Test the PBA . "Enter the command linuxpba and use a pass-phrase of debug. "
Results of this Test with much verbose data, scroll very fast and almost entirely exit the top of my 4K display so that I can not see the results/ expected output except for last device sdb.
I have 4 Samsung SSD - 980, 970, and 2 Samsung 870. These are in order : nvme0, nvme1, sda and sdb
I have tried shift+PageUp, but that does not take me beyond the last device (fourth device) results sdb.
Out of desperation , I sort of captured the console output with my phone and see all of the devices and what appears to say
"Is Opal Not Locked", but this occurs in about 1 second and I am uncertain without a normal console output.
I have no idea how to get to see the results and fear any similar commands may do the same.

[don-dolarson]

Try with command below and put the password after it when cursor is blinking. Worked for me.

linuxpba | less| grep Drive

If that doesn't work. Remove the | less. All drive lines should appear at the bottom of the screen.

[xwcgilmore]

Try with command below and put the password after it when cursor is blinking. Worked for me.

linuxpba | less| grep Drive

If that doesn't work. Remove the | less. All drive lines should appear at the bottom of the screen.

Tried "linuxpba | less| grep Drive" and "linuxpba | grep Drive" and "Drive" as sda1 and sda. Still get the rapid scrolling. On my 4K
monitor, the SEDutil terminal begins in the top 20 % of display. I believe I had in the past tried to pipe "|" with less and as well to redirect ">" to USB stick file - all without success. So, my thought is to insert a delay routine into the code and compile from source . Thanks for your response .

[gohrner]

@don-dolarson: Are you sure you mean

linuxpba | less| grep Drive

in this order, not

linuxpba | grep Drive | less

?

@xwcgilmore: You may also be able to use the console scrollback buffer, using Shift-PageUp.

However I wonder why you're getting much output with this command, I'm only getting a few lines similar to the ones shown as an example in the sedutil wiki page.
What is it outputting in your case?

[don-dolarson]

Yes in this order. Strange but it is how I got all "Drive" output at the bottom of my screen otherwise the output just scrolled itself down to the bottom (30-40 big font lines) with "Drive" lines between all of them without need of the debug password and an auto reboot. linuxpba | tee works as well.

I think it's because of the buggy rescue image, or different drive.
Shift+FN+PgUp couldn't scroll through all of them to the top page.

[xwcgilmore]

@don-dolarson

Yes in this order. Strange but it is how I got all "Drive" output at the bottom of my screen otherwise the output just scrolled itself down to the bottom (30-40 big font lines) with "Drive" lines between all of them without need of the debug password and an auto reboot. linuxpba | tee works as well.

I think it's because of the buggy rescue image, or different drive. Shift+FN+PgUp couldn't scroll through all of them to the top page.

"| tee" worked for me! As was in your case Shift+FN+PgUp - couldn't scroll all the way up , too many lines. Thanks for the suggestion. See my attached image. Extremely verbose output prior to getting what is stated in user guide should be displayed.

[xwcgilmore]

@gohrner

@don-dolarson: Are you sure you mean

linuxpba | less| grep Drive

in this order, not

linuxpba | grep Drive | less

?

@xwcgilmore: You may also be able to use the console scrollback buffer, using Shift-PageUp.

However I wonder why you're getting much output with this command, I'm only getting a few lines similar to the ones shown as an example in the sedutil wiki page. What is it outputting in your case?

Verbose output example.

[xwcgilmore]

@don-dolarson: Are you sure you mean

linuxpba | less| grep Drive

in this order, not

linuxpba | grep Drive | less

?

@xwcgilmore: You may also be able to use the console scrollback buffer, using Shift-PageUp.

However I wonder why you're getting much output with this command, I'm only getting a few lines similar to the ones shown as an example in the sedutil wiki page. What is it outputting in your case?

Please see images for extreme verbose output. Not as shown in SEDutil instructions.

[don-dolarson]

Strange this problem exists in this build, Chubby fork but not in the ladar fork which imo is the most stable.