Can't log in as root on new Debian-5.15.158-oxnas install

I have been running Debian 10 for 5 years on a Pogoplug Pro and decided it was finally time to upgrade. So, I downloaded Debian-5.15.158-oxnas-tld-2-rootfs-bodhi.tar.bz2 from the link in the Linux Kernel 5.15.196 Oxnas (OX820) Pogo V3 package and Debian rootfs thread and loaded everything onto a new USB drive.

It boots up fine, but it won't let me log in as root with password "root". I've tried removing the encrypted password from /etc/shadow, but it won't accept a null password either. Also tried setting up SSH using the RSA keys and authorized_keys file from the Debian 10 install, but it rejects my key. Also tried adding a non-root user (copying /etc/passwd and /etc/shadow entries from the Debian 10 system and setup its home directory), but won't let that user log in either (tried with both a password and no password).

I've even tried logging in with telnet, but no joy there either.

Once I get logged in, I can install sudo, reset root password, etc., but I can't get logged in.

Anybody have any ideas? The default password IS "root", right?

rsantag,

> It boots up fine, but it won't let me log in as
> root with password "root".
> Anybody have any ideas? The default password IS
> "root", right?

Yes. Credential is root/root.

Connect serial console, restsart, and post the entire serial console log here.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

OK, it must be the way I'm creating the disk because I backed up my current Debian 10 disk to a tar file, partitioned a new disk, created file system, labeled it, then extracted the tar file onto the new disk, and when I boot with that disk I get the same "Access denied" error when I try to log in

tarfile was created like this:

mount /dev/sdb1 /mnt/sdb1
cd /mnt/sdb1
tar cvf /root/my_tarfile .
cd /root
umount /mnt/sdb1

and loaded to the new USB drive like this

parted /dev/sdb rm 1 (remove fat32 partition)
parted /dev/sdb mkpart primary 0G 61.5G
mke2fs -j /dev/sdb1
e2label /dev/sdb1 rootfs
mount /dev/sdb1 /mnt/sdb1
cd /mnt/sdb1
tar xvf /root/my_tarfile
cd /root
umount /mnt/sdb1

Am I missing something?

Next attempt, decided to try using Win32 Disk Imager to make a backup image of a working 32GB drive, write the image to a new 64GB drive, then expand the partition and file system to fill the disk with parted and resizefs. When I tried booting this one, same issue. It rejected my SSH key and said "Access denied" when I tried entering a password.

Except for the size difference, this has to be an exact copy of the 32GB drive that works, right? Is it possible it's something with this particular drive? It is a Sandisk Ultra Fit 64GB, which is the same as what I'm currently using, although probably a newer version.

FINALLY able to log in! I wrote Debian-5.15.158-oxnas-tld-2-rootfs-bodhi.tar.bz2 to a different USB drive, booted and was able to log in with root/root. For some reason it seems like the Sandisk Ultra Fit drive is the problem.

The Sandisk Ultra Fit that didn't work is a 64GB USB 3.2 Gen 1 drive. The one that works is a Sandisk Ultra Fit 128GB USB 3.1 Gen 1. So, something about USB 3.2 it apparently doesn't like. Has anybody else run across anything like this before?



Edited 1 time(s). Last edit at 01/16/2026 07:41PM by rsantag.

> The Sandisk Ultra Fit that didn't work is a 64GB
> USB 3.2 Gen 1 drive. The one that works is a
> Sandisk Ultra Fit 128GB USB 3.1 Gen 1. So,
> something about USB 3.2 it apparently doesn't
> like. Has anybody else run across anything like
> this before?

Yes. With this Pogo V3 Oxnas, the way to boot consistently is to use a USB 2.0 drive. And also attach it to the USB port next to the Ethernet port.

USB 3 drives are hit/miss. The old USB Ultra Fit seems to be OK. But the box USB controller is old, so it might have problem with newer USB 3.x drive, as you have found.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Thanks Bodhi. Yeah, I've run across some SD cards that won't boot in V4 Pogoplugs, so if it hadn't booted, that would have been my first thought. The fact that it actually came up and I just couldn't log in was what stumped me.