Package: debian-installer
Severity: normal
Tags: d-i
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
After a corrupted nvme drive which included my root filesystem as btrfs which
wouldn't repair, I had to re-install (I was on Buster, but have taken the
opportunity to upgrade to Bulleye).
This drive contains a partition which I had formatted as ext4 with no journal
(it is the data directory for a docker install of sql server, so was set that
way as btrds cow settings not appropriate for a database), although I had
forgotten it was ext4 with no journal, and could afford to recreate from
scratch.
So during installation it is reported by partman as ext2, but just failed to
mount. I assumed it was corrupted as was the rest of the ssd, so I told the
installer to reformat it.
I have a virtual box machine on another SSD, and that too was reported as ext2
but failed to mount. This drive is more important (it contains a windows 10
installation maintained over a large number of years) and so I just told the
installer to forget it.
Now I have a working system and come to mount it, I had incorrectly added it to
/etc/fstab as ext2 and it was failing to mount. However a manual mount without
specifying the file system type (sudo mount /dev/sdb1 /home/alan/vbox ) made it
work
But now I could examine the failure message and realise its an ext4 without
journal and that is why its not mounting /etc/fstab.
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 5.5.0-2-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
