fedora 21 freshh install. shutdown impossible?

[linforpros]

Hi,
I am getting the following message after shutdown -h now:
rm: cannot remove /lib/drauct/hooks/shutdown/30-dm-shutdown.sh: Read-only filesystem

Here is a picture of the error:



The system is:
Linux localhost.localdomain 3.17.7-300.fc21.x86_64

It is a server installation. Neither reboot, poweroff or shutdown work because of the above message which loops endlessly

I left the machine for some time issuing "reboot" and it did reboot but only after some 10 minutes, the text string being shown continuously - scrolling like crazy.

# dracut -f helped only once for one or two reboots.

The only google reference is here:
http://web.archiveorange.com/archive...KVVgT1Cbn43Aes

I made some attempts to recover more info via logs to no avail, though.

shutdown -h now > shutdown.txt left me with an empty file.
grep -i shutdown /var/log/* -R produced no trace of the text string when the system is trying to shut down and is mentioned above.

How to tackle this problem?



I have found this link: https://ask.fedoraproject.org/questi...e-side-effects

There it says that an USB peripherals may be the cause of the problem.
I switched ports for my Bluetooth Keyboard and the message disappeared.
I have since shutdown the system three times via BUTTON, command prompt and it did work. Unfortunately the forth time gave the same error.

Linforpros

[anubisg1]

I have the same problem.

i opened a bug report:

https://bugzilla.redhat.com/show_bug.cgi?id=1178497

i'm not sure how critical dracut is (i know it builds initramfs, but still) , but removing the package, allows me to turn off the system and avoid to corrupt my FS . it caused 3 times already too have an corrupted root file system

[linforpros]

Hi,
You may have misidentified the bug.
Note that doing:

systemctl reboot -f -f

helps for three shutdowns/reboot/poweroffs. Interesting. Could be an lvm bug.... I figure that from the link I quoted in my original post. A Colin Walters give a patch for an alleged lvm bug:

+# Work around anaconda/dracut/lvm bug
+sync
+sync
+sync
+systemctl reboot -f -f
+%end

LinforPros

[anubisg1]

what do you mean with miss identified the bug ?

i can't shutdown nor reboot my system because dracut spits that endless loop. that's what i have and reported.

[linforpros]

Hi anubisg1,
What I mean is that perhaps the bug should be reported as an lvm bug, not a dracut bug. I am not an expert, though. I continue to search the internet for solutions but there seems to be none so far.

there is a hint however that doing #dracut -f or systemctl reboot -f -f helps for about three reboots/shutdowns/poweroffs. It has something to do with a filesystem that becomes read-only after so many reboots. I don't know what to think about it. SquashFS or ConfigFS?

LinforPros

[linforpros]

Hi guys,

• I have installed a fresh fedora 21 via net-install iso - which gives me an up-to-date system.
• edited /etc/selinux/config to reboot into Permissive mode
• disabled NetworkManager because I need RDO-openstack installed

So far every reboot goes though fine, so does every shutdown, via BUTTON or command line.

• installed openstack (had to disable provision_demo, and fix mysqld.log permission to get going)

NOW, the ERROR message that I started with this post reappeared when I shutdown/poweroff the system:
rm: cannot remove /lib/drauct/hooks/shutdown/30-dm-shutdown.sh: Read-only filesystem

As you can peek on the screenshot I uploaded it stops at Shutdown.target:

• cannot create
• /oldsys/
• /oldsys/proc
• /oldsys/run
• /oldsys/dev

How to start dealing with it?

LinforPros