I just finished installing a new PSU and cpu cooler. When I booted it, for some reason SSH went from being enabled to disabled. When I enable it, it seems to constantly want to load from tower.local rather than the IP  (which I've always used). The tower.local shows the page larger for some reason so it's not my favorite.

 

After enabling SSH and logging in, I'm not able to run commands I had been running yesterday.

watch -n 0.5 nvidia-smi  (actually now working)

watch -n sensors

 

My first question is how a hardware mod could change ssh settings. I did move the USB boot drive to a different port but I wouldn't think that would be the culprit.

 

Next question is how to fix the issue of not being able to run watch -n sensors.

 

When I run it I get:

 

watch: failed to parse argument: 'sensors': invalid argument

tower-diagnostics-20241126-1342.zip

Odd. The machine name was changed from it's previous name to 'tower'. I assume this is default naming?

11 minutes ago, Pandemic said:

I assume this is default naming?

Yep, that suggests an issue with the flash or the /config/ident.cfg file

I wonder if an unplanned power down could have caused that in the course of testing the PSU.

 

Any idea why 'watch -n sensors' isn't working when it was previously?