On Mon, 2025-01-06 at 21:15 -0800, Samuel Sieb wrote: > On 1/6/25 3:40 PM, Charlie McVeigh via users wrote: > > I have a Fedora virtual machine running on VMware Fusion where > > VMware > > Fusion is running on my work MacBook Pro. > > > > I believe my problem is not related to VMware Fusion or the fact > > that I > > am running Fedora as a VM. Here is my issue: > > It's definitely a factor. > > > i) I upgraded my vm from Fedora 38 to Fedora 40 using the DNF > > System Plugin method > > ii) The upgrade was normal, and all packages downloaded, I > > rebooted, and the new Fedora 40 packages installed without > > complaint. > > iii) After the upgrade and rebooting into Fedora 40, I get > > the > > following error dialog after typing in my encrypted disk password. > > “The VMware Tools power-on script did not run successfully in this > > virtual machine” > > iv) If I press “Ok” to the message dialog the machine just > > hangs on > > the black Fedora logo screen. No mouse, no keyboard. > > Since you say it's a message dialog, I assume that's a message from > the > vmware host. > > > I can boot into my old Fedora 38 rescue partition from the boot > > menu. > > I can get to a shell. If I attempt any file operation, I get the > > message “No space left on device” > > What file operations on what directory? Can you see the files? > > > If I run a df -h command none of my disks indicate more than 65% > > usage. > > What does "mount" show? > > > Any thoughts on steps to troubleshoot? > > > > I do have some data on this VM that I need, and I neglected to back > > up > > the VM or take a snapshot before I did the upgrade. Since this is > > a > > work computer, USB thumb drives are prohibited and are disabled > > from > > functioning. I am stuck. > > You can try adding "single" to the kernel command line in grub. That > should get you a console login prompt. > Thanks for responding you ideas were helpful. I am able to boot into fedora 40 by adding "single" to the kernel command line in grub and get to a command line prompt. To answer your questions in order: 1) The “The VMware Tools power-on script did not run successfully in this virtual machine” dialog is absolutely being presented from the VMware Fusion application. It is *not* from the Fedora boot process at all. 2) Once on the command line I can perform most any and all file operations. A file operation will fail when attempting to write to the disk. for example "echo 1 > foo" will fail with a message "no space left on device" 3) using "df -h" i have the following root@fedora:~# df -h Filesystem Size Used Avail Use% Mounted on /dev/dm-0 19G 12G 6.5G 65% / devtmpfs 4.0M 0 4.0M 0% /dev tmpfs 3.9G 0 3.9G 0% /dev/shm efivarfs 256K 28K 229K 11% /sys/firmware/efi/efiv ars tmpfs 1.6G 9.0M 1.6G 1% /run /dev/dm-0 19G 12G 6.5G 65% /home tmpfs 3.9G 0 3.9G 0% /tmp /dev/nvme0n1p2 947M 418M 489M 47% /boot /dev/nvme0n1p1 599M 12M 588M 2% /boot/efi On further checking the "no space left on device" message is only happening on the file systems mounted on / and /home. I can create files on all of the other mount points using my "echo 1 >foo" command from above. The problems exits with the /dev/dm-0 disk. the mount command returns the following for those two mount points: /dev/mapper/luks-197957e4-4760--45e1-8e92-c6762103fc25 on / type btrfs (rw,relatime,seclabel,compresszstd:1,ssd,space_cache=v2,subvolid=257,su bvol=/root) /dev/mapper/luks-197957e4-4760--45e1-8e92-c6762103fc25 on /home type btrfs (rw,relatime,seclabel,compresszstd:1,ssd,space_cache=v2,subvolid=256,su bvol=/home) At this point I am not sure what to do to get / and /home healthy again. Thanks. Charlie McVeigh -- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
