Hi All,

I just upgraded from FC6 to F7 and all went flawlessly on my Dell laptop.
Now I have this message when I open any konsole:

---------------------------------
df: no file systems processed
---------------------------------
I get it once I have my Konsole open, and when I su to root, I get it again.

What is this and how may I get rid of it.

H

what is the output of `mount` and what does `parted /dev/sda` followed by `print` show?

In FC6, IDE hard drives were /dev/hda, hdb, hdc, etc.... in F7, with the new kernel & ATA stack, IDE and SATA drives are /dev/sda, sdb, sdc, etc... could be causing problems with df.

Hi,

The output of mount is:
----------------------------------
[hatim@localhost ~]$ mount
/dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/sda5 on /boot type ext3 (rw)
tmpfs on /dev/shm type tmpfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
[hatim@localhost ~]$ parted /dev/sda
bash: parted: command not found
[hatim@localhost ~]$
---------------------------------------
What command is this second one? I did not understand it.

H

OK!
I found it, it was in the /sbin/

-------------------------------------------
[root@localhost sbin]# ./parted /dev/sda print
Model: ATA Hitachi HTS54104 (scsi)
Disk /dev/sda: 40.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number Start End Size Type File system Flags
1 32.3kB 49.4MB 49.3MB primary fat16
2 49.4MB 19.9GB 19.8GB primary ntfs boot
4 19.9GB 35.7GB 15.9GB extended
5 19.9GB 20.0GB 107MB logical ext3
6 20.0GB 35.7GB 15.7GB logical lvm
3 35.7GB 40.0GB 4261MB primary fat32

Information: Don't forget to update /etc/fstab, if necessary.

[root@localhost sbin]#
-----------------------------------------------

Now what?

H

I found these, you should see if they apply to you as well:

https://bugzilla.redhat.com/bugzilla....cgi?id=239141
https://bugzilla.redhat.com/bugzilla....cgi?id=242853

You can use the SELinux troubleshooter to diagnose if it is an SELinux issue:

"sealert -b" is the same as clicking the Star that shows up in the notification area if you're running Gnome. It should open a browser that shows SELinux denials with new ones at the top. You should be able to see there if SELinux is preventing 'df' from doing something.

what do you mean by df --whatever that does not work?
I already do not know which file does not work?

H