[F29] Ext4 file system inconsistencies
by Marco Guazzone
Hello,
I'm running an up-to-date Fedora 29 x86_64 (kernel 4.19.13-300.fc29.x86_64).
My ext4 file system got inconsistent twice in a week: the first time, the
'/home' partition; the last time, both '/root' and '/home' partitions.
I had to use a live distro to fix it with fsck.
I ran several disk test utilities to check for HW errors, including:
* HDDScan 4.0 (http://hddscan.com/): VERIFY, READ and BUTTERFLY tests
* Diagnostics tests from Dell's BIOS
* SMART self-test
All these tests succeded: no problem detected.
If I exclude HW errors, the only other option is a SW error (in the
kernel?).
Any idea?
Thank you for your help.
Marco
10 months, 1 week
tip: cd previous directory
by ToddAndMargo
Hi All,
I just discovered this. To cd back to the previous directory
cd -
What a time saver!
-T
10 months, 2 weeks
systemd-journald[585]: Failed to create new system journal: Input/output error
by Neal Becker
After attempting today's updates, the system is almost unusable. The
problems seem to be caused by journal. I see messages like the above.
I tried rm /var/log/journal/xxxx/* hoping it would clear up. But after
several reboots I still see such messages.
kde won't start at all. I'm using mate for now.
The update process seems to have crashed and not completed.
Ideas?
10 months, 2 weeks
Can't boot into emergency mode to perform lvresize
by cen
Hi
I want to decrease the size of my home partition and increase the root
partition using lvresize. if I understand correctly, I should boot into
emergency mode so home is not mounted. I followed the documentation,
adding systemd.unit=emergency.target to linux16 entry but system just
slowly loads and freezes at fedora logo. I left it for a few minutes,
nothing happens.
Best regards, cen
10 months, 2 weeks
mount exfat -
by Bob Goodwin
This is an updated Fedora29 workstation and I think I've installed
thetwo required exfat app's via dnf.
I would like to list the contents of a Western Digital MyBook external
drive that uses "exfat." Apparently it feels abused by the user when
unmounted.
[root@Box83 bobg]# mount -t exfat /dev/sdc1 /mnt/test -o nonempty
FUSE exfat 1.3.0
WARN: volume was not unmounted cleanly.
fuse: mountpoint is not empty
fuse: if you are sure this is safe, use the 'nonempty' mount option
Perhaps I am not entering the commend correctly?
[root@Box83 bobg]# mount -o nonempty -t exfat /dev/sdc1 /mnt/test
FUSE exfat 1.3.0
WARN: volume was not unmounted cleanly.
fuse: mountpoint is not empty
fuse: if you are sure this is safe, use the 'nonempty' mount option
What is wrong?
--
Bob Goodwin - Zuni, Virginia, USA
http://www.qrz.com/db/W2BOD
box83 FEDORA-29/64bit LINUX XFCE Fastmail POP3
10 months, 2 weeks
container / can't connect to localhost via Firefox - logs:
s6-supervise (child): fatal: unable to exec run: Permission denied
by arnaud gaboury
I am following this wiki[0] to run R Studio on my box. Below are the
commands I run
----------------------
# podman run -d -p 8787:8787 -e PASSWORD=XXX --name rstudio rocker/tidyverse
..........
Storing signatures
a72fac512b891c21f0654334a2032b0d67b87720cb986a092237ab272d245f8d
-----------------------------------
At this point, I am supposed to access the R studio app via my Firefox
browser on port 8787 on localhost, which I can't.
Debuging:
--------------------------------------------
- Is the container running?
# podman ls
CONTAINER ID IMAGE COMMAND CREATED
STATUS PORTS NAMES
a72fac512b89 docker.io/rocker/tidyverse:latest /init 2 minutes ago Up
2 minutes ago 0.0.0.0:8787->8787/tcp rstudio
-Is the 8787 port open?
# podman port a72fac512b89
8787/tcp -> 0.0.0.0:8787
# lsof -i -P -n | grep LISTEN
8:cupsd 984 root 8u IPv6 35102 0t0 TCP [::1]:631 (LISTEN)
9:cupsd 984 root 9u IPv4 35103 0t0 TCP 127.0.0.1:631
(LISTEN)
67:conmon 12891 root 5u IPv4 453576 0t0 TCP *:8787 (LISTEN)
- Can I ping localhost, 0.0.0.0, 127.0.0.1, yogabx (hostname), 192.168.1.92
(returned by ip -a)
YES
- Do I have any firewall/iptable running?
# systemctl status firewalld.service
● firewalld.service
Loaded: masked (Reason: Unit firewalld.service is masked.)
Active: inactive (dead)
NO iptables
# curl localhost:8787
curl: (7) Failed to connect to localhost port 8787: Connection refused
# podman logs a72fac512b89
[fix-attrs.d] applying owners & permissions fixes...
[fix-attrs.d] 00-runscripts: applying...
[fix-attrs.d] 00-runscripts: exited 0.
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] add: executing...
Nothing additional to add
[cont-init.d] add: exited 0.
[cont-init.d] userconf: executing...
[cont-init.d] userconf: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
s6-supervise (child): fatal: unable to exec run: Permission denied
s6-supervise rstudio: warning: unable to spawn ./run - waiting 10 seconds
s6-supervise (child): fatal: unable to exec run: Permission denied
s6-supervise rstudio: warning: unable to spawn ./run - waiting 10 seconds
..... and so on
----------------------------
Googling this issue (s6-supervise (child): fatal: unable to exec run:
Permission denied), I found a few reported issues like this one[1],[2]
I don't understand what is behind, so can anyone help me to solve this
issue (if I can).
Thank you
[0]https://github.com/rocker-org/rocker/wiki/Using-the-RStudio-image
[1]https://github.com/linuxserver/docker-plex/issues/76
[2]https://github.com/linuxserver/docker-sonarr/issues/28
10 months, 2 weeks
Web Content
by Antonio M
What is this process that makes my computer crazy?? How can I avoid it?
Antonio Montagnani
Linux Fedora 29 Workstation
da/from Gmail
10 months, 2 weeks
multi-line URIs
by Jon LaBadie
When selection a multi-line URI in a terminal window
I've noticed two behaviors. Some will ?ignore? the
extra lines and only select to the end of the first
line. Others will select the entire URI, typically
to an ending ">". Obviously I would prefer the latter.
Is this behavior terminal specific, i.e. gnome-terminal
vs mate-terminal vs xterm. Or is it a configuration
parameter that I've not found?
Jon
--
Jon H. LaBadie jonfu(a)jgcomp.com
10 months, 2 weeks
Dell T7500 won’t boot starting at 4.19.13 for fedora 29
by Nate Pearlstein
Dell T7500 won’t boot on 4.19.13 or later from fedora updates for F29. 4.19.10 works. 4.19.11 and 4.19.12 from Koji boot as well. No output after Probing EDD on vga console starting with 4.19.13 through the latest today, 4.9.15.
10 months, 2 weeks
