Can list and see files/dirs in Console, but missing dirs/files if listing via SFTP client

First off I’m a linux newb, trying to follow instructions found on the 'net. So bear with me if I’m missing the obvious.

I’m trying to troubleshoot a droplet that won’t load due to a kernel panic. Screenshot -

So I can log on using recovery image, mount the disk image and chroot into the system.

Now if I cd into /boot/ I can see a list of images and other files/dir. If I do the same for the /var/ I can see the www directory listed

BUT if I log on using a SFTP client (SmartFTP & Winscp), using the provided temp root password, I can not see the same list in /boot/, nor can I see the /www dir in /var/.

Opening a terminal window from within those clients also fails to see these directories and/or files.

Screenshot of /boot/ in DO console -

same dir but using sftp client

/var/ in console

/var/ from sftp client

So can someone point out what I’m doing wrong here and how to fix the issue of the missing dir/files in sftp. cheers Steve

Show comments

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

This comment has been deleted

To elaborate, when following the instructions found here

I keep getting the following error about canonical path not found “overlay”

plus the final command given in those instructions “sudo reboot” doesn’t work either.

It’s very difficult if not impossible for a novice like myself to repair a borked droplet when DO own recovery instructions don’t work. And still, over 24 hrs later, no response from Support. Very frustrating

Hi Alex, No the issue still remains, and I haven’t heard back from DO support as of yet.

There is no Grub menu that I can see, or if there is, I don’t know how to access it.

For what it’s worth this droplet uses Grub2, and internal kernel management, which from my reading, means the options are different from pre-Grub2. Am I right?

I can logon via recovery iso, as I did that to mount & check the file system, but cannot follow the the instructions on how to replace the faulty kernel. It’s very gobbledygook to me. I tried, but the recovery iso terminal just hangs.

I’d appreciate any step by step help you could offer, as I’ve been offline for over 24hr now. I must say, I’m a little disappointed in Support not responding as of yet.