Update fails with the following message ; Cannot obtain lock: how do I report that as a bug ?

What is the output of:

sudo parted -l; lsb_release -a; uname -a

Thanks

The output of that command was:

Model: ATA Crucial_CT1050MX (scsi)
Disk /dev/sda: 1050GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number  Start   End     Size   Type      File system  Flags
1      1049kB  102GB   102GB  primary   ntfs         boot
2      102GB   103GB   545MB  primary   ntfs         msftres
3      103GB   209GB   106GB  primary   ext4
4      209GB   1050GB  841GB  extended
7      209GB   315GB   106GB  logical   ext4
5      315GB   796GB   481GB  logical   ntfs
6      796GB   1050GB  254GB  logical   ext4

Model: ATA ST3000DM008-2DM1 (scsi)
Disk /dev/sdb: 3001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system  Name        Flags
1      1049kB  3001GB  3001GB  ntfs         Seagete 3T  msftdata

No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 22.04.3 LTS
Release:        22.04
Codename:       jammy
Linux Studio-Main 5.15.0-83-lowlatency #92-Ubuntu SMP PREEMPT Fri Aug 18
13:09:41 UTC 2023 x86_64 x86_64 x86_6
4 GNU/Linux

On 10/8/23 00:36, actionparsnip wrote:
> Your question #708135 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/708135
>
> Status: Open => Needs information
>
> actionparsnip requested more information:
> What is the output of:
>
> sudo parted -l; lsb_release -a; uname -a
>
> Thanks
>

OK and the output of:

dh -Th

Thanks

Below is the  output of dh-Th

mark@Studio-Main:~$ dh -Th
Command 'dh' not found, but can be installed with:
sudo apt install debhelper
mark@Studio-Main:~$ sudo apt install debhelper
[sudo] password for mark:
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure
-a' to correct the problem.

I don't know if it matters there is an install of 20.04 that failed part
way through an upgrade to 22.04
it still boots wont update on one of the ext4 partitions of sda.

On 10/9/23 01:16, actionparsnip wrote:
> dh -Th

Sorry, my mistake

df -Th

new output:

mark@Studio-Main:~$ df -Th
Filesystem     Type     Size  Used Avail Use% Mounted on
tmpfs          tmpfs    3.2G  2.1M  3.2G   1% /run
/dev/sda6      ext4     233G   30G  192G  14% /
tmpfs          tmpfs     16G     0   16G   0% /dev/shm
tmpfs          tmpfs    5.0M  4.0K  5.0M   1% /run/lock
tmpfs          tmpfs     16G  4.0K   16G   1% /tmp
tmpfs          tmpfs    3.2G   60K  3.2G   1% /run/user/1000
/dev/sda3      ext4      97G   26G   67G  29% /media/mark/Ubuntu 1910
/dev/sda7      ext4      97G   90G  2.3G  98% /media/mark/Ubuntu 2004 LTS
/dev/sda1      fuseblk   96G   59G   38G  61% /media/mark/4F4C168914C337F4
/dev/sdb1      fuseblk  2.8T  578G  2.2T  21% /media/mark/Exchange 3

On 10/9/23 02:16, actionparsnip wrote:
> Your question #708135 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/708135
>
> Status: Open => Needs information
>
> actionparsnip requested more information:
> Sorry, my mistake
>
> df -Th
>

What is the full output that you receive for the commands

sudo dpkg --audit
sudo dpkg --configure -a

here is the output from both commands:

mark@Studio-Main:~$ sudo dpkg --audit
[sudo] password for mark:
Sorry, try again.
[sudo] password for mark:
The following packages are only half configured, probably due to problems
configuring them the first time.  The configuration should be retried using
dpkg --configure <package> or the configure menu option in dselect:
linux-image-5.15.0-86-lowlatency Signed kernel image lowlatency

mark@Studio-Main:~$ sudo dpkg --configure -a
Setting up linux-image-5.15.0-86-lowlatency (5.15.0-86.95) ...
Processing triggers for linux-image-5.15.0-86-lowlatency (5.15.0-86.95) ...
/etc/kernel/postinst.d/dkms:
* dkms: running auto installation service for kernel 5.15.0-86-lowlatency
   ...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.15.0-86-lowlatency
W: Possible missing firmware
/lib/firmware/amdgpu/yellow_carp_gpu_info.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vangogh_gpu_info.bin
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_rlc.bin
for module amdgpu
W: Possible missing firmware
/lib/firmware/amdgpu/cyan_skillfish_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_mec.bin
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_me.bin
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_pfp.bin
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_ce.bin
for module amdgpu
W: Possible missing firmware
/lib/firmware/amdgpu/cyan_skillfish_sdma1.bin for module amdgpu
W: Possible missing firmware
/lib/firmware/amdgpu/cyan_skillfish_sdma.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes.bin
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for
module amdgpu
/etc/kernel/postinst.d/zz-update-grub:
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.15.0-86-lowlatency
Found initrd image: /boot/initrd.img-5.15.0-86-lowlatency
Found linux image: /boot/vmlinuz-5.15.0-86-lowlatency
Found initrd image: /boot/initrd.img-5.15.0-86-lowlatency
Found linux image: /boot/vmlinuz-5.15.0-84-lowlatency
Found initrd image: /boot/initrd.img-5.15.0-84-lowlatency
Found linux image: /boot/vmlinuz-5.15.0-83-lowlatency
Found initrd image: /boot/initrd.img-5.15.0-83-lowlatency
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create
new boot entries.
Found Windows 10 on /dev/sda1
Found Ubuntu 19.10 (19.10) on /dev/sda3
Found Ubuntu 20.04.6 LTS (20.04) on /dev/sda7
done

dpkg configure finished thus time before it died at os-prober

On 10/9/23 05:41, Manfred Hampl wrote:
> sudo dpkg --audit

The problem now seems to have disappeared.

I am not sure what the problem was.
Errors like "<partition name> Input/output error" usually indicate a file system error on a partition, but your error message referred to the whole disk "/dev/sda". That might indicate that there was a problem on the partition table.

I just ran update and it went through like normal It appears my problem
might be solved. I don't what changed earlier today update would fail
with the same error message. I think your right the status should be
changed to answered.

On 10/9/23 05:41, Manfred Hampl wrote:
> sudo dpkg --audit

that seams to have solved the missing firmware issue. thanks For your help.