Buster on LS220D only reboots back into installer? Did I miss a step?
Closed this issue · 6 comments
Hello there! What a fantastic project. I feel like I'm retaking ownership of my ageing Buffalo hardware!
The installer worked fine and it downloaded the additional installation files and rebooted. But now I can only get back into the NAS with the installer credentials:
ssh installer@192.168.1.97
The root and nas-user accounts I set up during the install don't appear to be accesible:
BusyBox v1.30.1 (Debian 1:1.30.1-6+b3) built-in shell (ash)
Enter 'help' for a list of built-in commands.
~ # cat /etc/passwd
root:*:0:0:root:/:/bin/sh
installer:x:0:0:installer:/:/bin/network-console
sshd:*:100:65534::/run/sshd:/bin/false
~ #
Should I have deleted the installer image from /boot before rebooting? I couldn't find anything in the instructions mentioning this, so I assumed the installer script removes the installer boot image or renames it before rebooting into the newly installed Linux kernel. That can't be the case though because there's no /boot folder visible from the installer kernel.
Good to hear from you!
It sounds like you didn't set up /boot properly in the partitioning menu. For the new boot files to be stored to the proper place /boot must:
From https://github.com/1000001101000/Debian_on_Buffalo/wiki/Running-the-installer:
- located on the first partition of the disk(s)
- either a regular partition or RAID1 array
- formatted as ext3
If you're not sure if you have the configuration correct you can post a screenshot of your partition screen and I can take a look before you commit to the next install attempt.
Hi. Ah okay. That's odd. I used the newbie guided partitioning option, which said it would set up the boot partition and then set the /home folder in the largest contiguous partition. I'll try again.
Hmm. It looks like after going through the installer process once already, it's changed things up a little.
Guided partitioning
Configure software RAID
Configure the Logical Volume Manager
Configure encrypted volumes
Configure iSCSI volumes
│
│ RAID1 device #0 - 1.0 GB Linux Software RAID Array
│ > #1 1.0 GB ext3
│ RAID1 device #1 - 5.1 GB Linux Software RAID Array
│ > #1 5.1 GB ext3
│ RAID1 device #101 - 3.0 TB Linux Software RAID Array
│ > #1 3.0 TB xfs
│ RAID1 device #2 - 1.0 GB Linux Software RAID Array
│ > #1 1.0 GB F swap swap
│ SCSI1 (0,0,0) (sda) - 3.0 TB ATA TOSHIBA DT01ACA3
│ > #1 1.0 GB ext3 primary
│ > 458.2 kB FREE SPACE
│ > #2 5.1 GB primary
│ > #3 393.7 kB primary
│ > #4 512.0 B primary
│ > #5 1.0 GB primary
│ > 65.0 kB FREE SPACE
│ > #6 3.0 TB primary
│ > #7 511.7 MB ext2
│ > #8 7.7 GB ext4
│ > #9 384.8 MB F swap swap
│ > 466.4 kB FREE SPACE
Any thoughts about what's happened here?
If you used any auto/guided partitioning options it will do some goofy stuff on your behalf. For these devices you need to manually specify things at this step.
That #9 being used for swap may be a problem, I would change it to "do not use".
if you set "RAID1 device #0 - 1.0 GB" as /boot and "RAID1 device #1 - 5.1 GB" as / you should be good to go.
/boot needs to be ext3
/ can be whatever you want, use ext4 if you're not sure.
Right. That makes sense and ... yes, that worked.
Many thanks.
I think the takeaway is "don't use the guided (newbie) partitioning option" because it won't correctly setup the / and /boot partitions before proceeding with the installation.
I think I concluded that I wasn't able to disable those options easily, if I remember I'll look again when I work on the bookworm installer.