5

I have observed that if I use any of the following commands to reboot my RPi 2B:

$ sudo reboot
$ sudo shutdown -r now
$ sudo shutdown -Hr now

and then try to SSH into the Pi, I get a Connection Refused error. It pings normally, though. Then I have to go to the Pi, restart the power supply. Then I can SSH into it normally, after it boots up again.

How do I remotely restart the pi, while maintaining SSH access after it boots?

I didn't have this problem before. I have touched the /etc/fstab, the firewall, keep USB drives plugged in it and am running HAP-NodeJS on it currently. This loads up on startup (with cron). pkilling it (node, not cron) before reboot doesn't work.

Thanks in advance

P.S. Earlier, even restarting the power wasn't working. It turned out to that a drive in /etc/fstab that was set to auto was unplugged.

Now, every time I have to reboot it, I have to restart the power supply to use SSH, or start any program.

abilops
  • 61
  • 1
  • 1
  • 7

2 Answers2

1

My guess is the touch command you typed in is causing the problem. If you used the backstroke '\' in your touch command instead of the forwardstroke '/', you created an empty file in the main directory called 'etcfstab'. I'm not sure why this stops ssh'ing into the pi but it does. To fix this problem, power cycle the Pi. Then you should be able to ssh into the Pi. Use the 'ls' command to list the files and you should see 'etcfstab' in the list of files. To remove this file use the command 'rm etcfstab'. Then reboot and your ssh session should work. Hopes this helps.

Glenn
  • 21
  • 1
1

It turned out to be a problem in the /etc/fstab file. It had an entry for /dev/sda1 (vfat). I ran blkid and found that the device I wanted to mount was sdb1 and sda1 was formatted as ntfs. So I changed fstab and now everything is back to normal. I can reboot to my heart's content!

Thanks to Glenn for the last nudge to look at the fstab file.

abilops
  • 61
  • 1
  • 1
  • 7