Thank you Jan, see comments below. On Tue, Mar 04, 2025 at 09:18:18AM +0100, Jan Stary wrote: > To be sure: this is not "near the end of sysupgrade" > - the isntaller hasn't evene started upgrading anything, > as your filesystems can't even be mounted. >
Very true Jan. > > On Mar 04 09:17:05, h...@stare.cz wrote: > > On Mar 04 20:57:04, avo...@xtra.co.nz wrote: > > > THE FOLLOWING FILE SYSTEM HAD AN UNEXPECTED INCONSISTENCY: > > > ffs: fa50b3edace170b1.e (/var) > > > Automatic file system check failed: help! > > > Enter pathname of shell or RETURN for sh: > > > > > > wrdl5# fsck -t ffs /dev/sd1e > > > ** /dev/rsd1e > > > > > > CANNOT READ: BLK 128 > > > CONTINUE? [Fyn] y > > > > > > THE FOLLOWING DISK SECTORS COULD NOT BE READ: 128, 129, 130, 131, > > > 132, 133, 134, 135, 136, 137, 138, 139, 140, 141, 142, 143, > > > /dev/rsd1e: CANNOT READ DISKLABEL > > > wrdl5# > > > > > > The laptop concerned is a Dell M6600 circa 2011 that I have > > > owned since it was new. All internal components are original > > > including the 2 750Gb spinning disks. > > > > > > Is the fsck failed partition recoverable, or should I assume > > > the sd1 disk is at end of (a long) life? > > > > Make sure to destroy that disk > > so that no-one will try to use it. > > > > Get a SSD; those are reasonably cheap now > > and the machine will be considerably faster. > > > > Better yet, replace both disks with SSDs. > > > > Then restore from backups, obviously. > > > > > > Jan > > > > > > > OpenBSD 7.6-current (GENERIC.MP) #523: Thu Jan 30 18:52:21 MST 2025 > > > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP < snip > AFAIK this laptop cannot be upgraded with M.2 NVMe SSD's. I have intended to get a new snappy arm64 or riscv64 laptop for months, but other than an unsupported Macbook M4 I have not found one. -- aer
