Guys,

Attempting to update an arch chroot (only a couple days old), I have run into
the following error:

sudo mkarchroot -u $CHROOT/root
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
local is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...

Targets (12): dbus-core-1.6.0-4 e2fsprogs-1.42.4-1 filesystem-2012.6-4
hwids-20120611-1 iproute2-3.4.0-2
iputils-20101006-3 kmod-9-1 libsystemd-185-2 libusbx-1.0.12-1
linux-3.4.4-2 systemd-tools-185-2
xz-5.0.4-1

Total Installed Size: 71.36 MiB
Net Upgrade Size: 0.49 MiB

Proceed with installation? [Y/n]
(12/12) checking package integrity
[#######################################] 100%
(12/12) loading package files
[#######################################] 100%
(12/12) checking for file conflicts
[#######################################] 100%
error: cannot remove file '/sys/': Read-only file system
error: could not commit transaction
error: failed to commit transaction (transaction aborted)
Errors occurred, no packages were upgraded.

How do I fix this? Is this another filesystem update issue like with
filesystem-2012.6-2?

--
David C. Rankin, J.D.,P.E.

On Tue, Jun 26, 2012 at 10:02:07AM -0500, David C. Rankin wrote:
> Guys,
>
> Attempting to update an arch chroot (only a couple days old), I have run into
> the following error:
>
> sudo mkarchroot -u $CHROOT/root
> :: Synchronizing package databases...
> core is up to date
> extra is up to date
> community is up to date
> local is up to date
> :: Starting full system upgrade...
> resolving dependencies...
> looking for inter-conflicts...
>
> Targets (12): dbus-core-1.6.0-4 e2fsprogs-1.42.4-1 filesystem-2012.6-4
> hwids-20120611-1 iproute2-3.4.0-2
> iputils-20101006-3 kmod-9-1 libsystemd-185-2 libusbx-1.0.12-1
> linux-3.4.4-2 systemd-tools-185-2
> xz-5.0.4-1
>
> Total Installed Size: 71.36 MiB
> Net Upgrade Size: 0.49 MiB
>
> Proceed with installation? [Y/n]
> (12/12) checking package integrity
> [#######################################] 100%
> (12/12) loading package files
> [#######################################] 100%
> (12/12) checking for file conflicts
> [#######################################] 100%
> error: cannot remove file '/sys/': Read-only file system
> error: could not commit transaction
> error: failed to commit transaction (transaction aborted)
> Errors occurred, no packages were upgraded.
>
> How do I fix this? Is this another filesystem update issue like with
> filesystem-2012.6-2?
>

mount / -o rw -- that is, something seems to be going wrong with your fstab.

On 06/27/2012 07:30 AM, Martti Kühne wrote:


How do I fix this? Is this another filesystem update issue like with
filesystem-2012.6-2?



mount / -o rw -- that is, something seems to be going wrong with your fstab.



Thanks Martti,

I don't know what the deal is. / _is_ mounted rw:

15:33 archangel:~> mount
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
dev on /dev type devtmpfs
(rw,nosuid,relatime,size=4055320k,nr_inodes=101383 0,mode=755)

run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
/dev/mapper/nvidia_baaccajap5 on / type ext3 (rw,relatime,data=ordered)
none on /dev/pts type devpts (rw,relatime,mode=600,ptmxmode=000)
none on /dev/shm type tmpfs (rw,relatime)
binfmt on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
/dev/mapper/nvidia_baaccajap6 on /boot type ext3 (rw,relatime,data=ordered)
/dev/mapper/nvidia_baaccajap12 on /home type ext4 (rw,relatime,data=ordered)
/dev/mapper/nvidia_baaccajap9 on /var type ext3 (rw,relatime,data=ordered)
/dev/mapper/nvidia_baaccajap10 on /srv type ext3 (rw,relatime,data=ordered)
/dev/mapper/nvidia_baaccajap7 on /data type ext3 (rw,relatime,data=ordered)
/dev/mapper/nvidia_baaccajap11 on /home/david/pvt type ext4
(rw,relatime,data=ordered)

/dev/sde5 on /dat_e type ext3 (rw,relatime,data=ordered)
/dev/sdf5 on /dat_f type ext3 (rw,relatime,data=ordered)

But still, attempting to update the chroot fails. This has always worked in
the past. I have a disk that is getting flaky. Maybe this is just a hardware
issue.


--
David C. Rankin, J.D.,P.E.

On 06/27/2012 07:30 AM, Martti Kühne wrote:

>>
>> How do I fix this? Is this another filesystem update issue like with
>> filesystem-2012.6-2?
>>
>
> mount / -o rw -- that is, something seems to be going wrong with your fstab.
>

Hmm,

This might be a real problem with recent updates. Now both machines (i686 &
x86_64) are giving the same failure:

Key not changed so no update needed.
==> Importing owner trust values...
==> Updating trust database...
gpg: next trustdb check due at 2012-08-10
( 2/30) upgrading cronie
[#######################################] 100%
( 3/30) upgrading glibc
[#######################################] 100%
init: /dev/initctl: No such file or directory
Generating locales...
de_DE.UTF-8... done
en_US.UTF-8... done
Generation complete.
( 4/30) upgrading xz
[#######################################] 100%
( 5/30) installing libsystemd
[#######################################] 100%
( 6/30) upgrading kmod
[#######################################] 100%
( 7/30) upgrading hwids
[#######################################] 100%
( 8/30) upgrading systemd-tools
[#######################################] 100%
Failed to open /dev/kmsg for logging: No such file or directory
Initializing machine ID from D-Bus machine ID.
( 9/30) upgrading device-mapper
[#######################################] 100%
(10/30) upgrading cryptsetup
[#######################################] 100%
error: cannot remove file '/sys/': Read-only file system
error: could not commit transaction
error: failed to commit transaction (transaction aborted)
Errors occurred, no packages were upgraded.


--
David C. Rankin, J.D.,P.E.

On 06/29/2012 06:25 PM, David C. Rankin wrote:
...


error: cannot remove file '/sys/': Read-only file system
error: could not commit transaction
error: failed to commit transaction (transaction aborted)
Errors occurred, no packages were upgraded.




I may be off base but can you check if your / filesystem is full?

gene/

On 30/06/12 10:58, Genes MailLists wrote:
> On 06/29/2012 06:25 PM, David C. Rankin wrote:
> ...
>
>> error: cannot remove file '/sys/': Read-only file system
>> error: could not commit transaction
>> error: failed to commit transaction (transaction aborted)
>> Errors occurred, no packages were upgraded.
>>
>>
>
> I may be off base but can you check if your / filesystem is full?
>
> gene/
>
>


Just because the answers are getting more ridiculous....


Open /usr/sbin/mkarchroot and change:

mount -o remount,ro,bind "${working_dir}/sys"
to
mount -o remount,bind "${working_dir}/sys"


Allan

On 06/29/2012 08:07 PM, Allan McRae wrote:
> Just because the answers are getting more ridiculous....
>
>
> Open /usr/sbin/mkarchroot and change:
>
> mount -o remount,ro,bind "${working_dir}/sys"
> to
> mount -o remount,bind "${working_dir}/sys"
>
>
> Allan

Ooh, you're good

That was it -- works like a charm now.

... just how did the little ',ro' come to cause such a problem?

--
David C. Rankin, J.D.,P.E.

On 30/06/12 13:37, David C. Rankin wrote:
> On 06/29/2012 08:07 PM, Allan McRae wrote:
>> Just because the answers are getting more ridiculous....
>>
>>
>> Open /usr/sbin/mkarchroot and change:
>>
>> mount -o remount,ro,bind "${working_dir}/sys"
>> to
>> mount -o remount,bind "${working_dir}/sys"
>>
>>
>> Allan
>
> Ooh, you're good
>
> That was it -- works like a charm now.
>
> ... just how did the little ',ro' come to cause such a problem?
>

/sys is in the filesystem package. When pacman upgrades filesystem it
tries to remove /sys then reinstall it (not really, simplified...). It
sees /sys is read only and so it can not deal with that so bails. It is
a bug in pacman.

Allan