upgrade abortion

[Bret Busby]

I assume, but, do not know, that this will generate a new thread with the same
subject field, as each message that I send from this (the computer with the
aborted upgrade) computer, I have to send from alpine, as a new created message,
with the text of preceding messages, copied and pasted into it.

On 19/1/22 5:58 pm, Jared Norris wrote:

<snip>

> With regards to the issue, I believe if you can get the file system
> mounted correctly you may have a shot of resolving the install issues.
> I'm not sure what the drive location is but the tools I'd look into:
> * fdisk to make sure the drive is okay (failing drives can be mounted
> read only)
> * mount to see what options are selected against the drive in question
> when it was mounted
> * editing /etc/fstab if any of the mount options are incorrect
> 
> If you don't have any luck please post the outcome of your commands 
for
> further troubleshooting
>

"
Wed Jan 19 07:37:07 bret at bret-Aspire-5750G:~$df -h
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           1.6G  1.9M  1.6G   1% /run
/dev/sdb13       33G   16G   16G  52% /
tmpfs           7.8G   17M  7.8G   1% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           4.0M     0  4.0M   0% /sys/fs/cgroup
/dev/sdb14       59G   35G   22G  62% /home
tmpfs           1.6G  976K  1.6G   1% /run/user/1000
/dev/sda1       932G  526G  407G  57% /media/bret/Samsung_T5
/dev/sdb7        92G   82G  5.5G  94% /media/bret/Data01
/dev/sdb8        92G   60M   87G   1% /media/bret/Data02
/dev/sdb9        32G  3.7G   27G  13% /media/bret/Data03
/dev/sdb5        59G   20G   36G  36%
/media/bret/aa8395cd-35a1-4a59-9406-63713d026ec2
/dev/sdb11       59G   50G  6.3G  89%
/media/bret/4ebf5b87-0e07-4676-9ab4-beae27f6b38a
/dev/sdb12       32G   48M   30G   1% /media/bret/Data04
Wed Jan 19 18:06:49 bret at bret-Aspire-5750G:~$cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sdb13 during installation
UUID=46e5f7df-03b3-46f6-86a6-c150ca9c9588 /               ext4 errors=remount-ro
0       1
# /home was on /dev/sdb14 during installation
UUID=35f8bd21-99d3-4e8d-9ed6-d4a66bf3f035 /home           ext4 defaults        0
2
# swap was on /dev/sdb10 during installation
UUID=b1246745-829b-442f-9103-5aebdb6b950d none            swap    sw 0       0
# swap was on /dev/sdb6 during installation
UUID=ea619ba9-2406-4b81-b216-0f1f19d13946 none            swap    sw 0       0
Wed Jan 19 18:07:18 bret at bret-Aspire-5750G:~$
"

can fdisk be run (I assume that the syntax is "fdisk /dev/sdb13" ?) on the root
partition, while it is mounted / in use?

-- 
Bret Busby
Armadale
West Australia
(UTC+0800)
..............