Mounting internal disk spins up connected external USB disks
by Wolfgang Pfeiffer
Mounting an internally installed disk on a laptop spins up all
disks connected to this machine via USB. And I try to prevent these
externally connected disks to spin up.
The behaviour, IIRC, started a few months ago on the previous F27 and
continues now on F28. Before that I don't remember this behaviour to
have happened.
I thought it was some smartd issue, and stopped this service
("/usr/bin/systemctl stop smartd.service") - to no avail: mounting the
internal disk still spins up the external ones.
The internal disk is identified by "smartctl -d test /dev/sda" like
so:
[ ... ]
/dev/sda: Device of type 'scsi' [SCSI] detected
/dev/sda [SAT]: Device open changed type from 'scsi' to 'sat'
/dev/sda [SAT]: Device of type 'sat' [ATA] opened
(On a side note: I'm astonished that a smartctl simple info flag is
changing some device type like shown above)
External disks are identified by a smartctl test like so:
One:
"[USB Sunplus]: Device of type 'usbsunplus' [ATA] detected"
the other one:
"[SAT]: Device of type 'sat' [ATA] detected"
Anyone an idea about where to start investigating this issue? Where
could such behaviour possibly be set up?
Thanks in anticipation.
Wolfgang
5 years, 1 month
Scanning problem with HP4620.
by Ger van Dijck
Hi all,
After an update to Fedora29 I can print but not scan anymore with a HP
officejet 4620 in WLAN.
When running HP-check I get two messages : cups required incompat : cups
may nt be installed or running .
cups is installed and running.
python3-notify2 needs to be
installed : Question where can I "find it"
Has anyone the same experience ?
Regards,
Ger van Dijck.
--
Using Opera's mail client: http://www.opera.com/mail/
5 years, 1 month
F29 support for Intel Rapid Storage Technology (RST)
by dsavage＠peaknet.net
Does Fedora 29 support the Intel RST (Rapid Storage Technology) chip for
hardware RAID? My new ThinkPad P72 came with an RST chip set up with two
2TB PCIe M.2 SSDs in a RAID1 config. The Fedora-29-MATE-Compiz spin DVD
doesn't "see" it. Nor does Clonezilla.
There's a BIOS mode setting for the Intel RST: "RST" mode for RAID, and
"AHCI" mode for separate SATA drives. Changing that setting to AHCI will
probably break the RAID1 array and render the P72 unbootable. I don't know
if that would a destructive, irreversible change, or if changing the mode
setting back to RST would restore everything.
I've only tried the MATE spin. One purpose of this question is to find out
if the full installation DVD supports the Intel RST chip.
--Doc
Robert G. (Doc) Savage
Fairview Heights, IL
"Perfection is the enemy of good enough."
-- Admiral of the Fleet Sergei G. Gorshkov
5 years, 2 months
flatpak log entries?
by Tom Horsley
Why do I have 47 bazillion lines of this sort of stuff in my logs:
Jan 30 19:55:13 tomh polkitd[1151]: Registered Authentication Agent for unix-process:4457:4527106 (system bus name :1.3718 [flatpak --installations], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Jan 30 19:55:13 tomh polkitd[1151]: Unregistered Authentication Agent for unix-process:4457:4527106 (system bus name :1.3718, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
5 years, 2 months
Shredding a removable drive (OT)
by Jonathan Ryshpan
I'm using shred on some 2Tb USB disk drive that I plan to give away.
So far it has taken 8 hours to shred 50% of the drive, which implies
that it will take about 16 hours to shred the whole drive. I have
another 2 drives to go.
Is there a quicker way to protect my data when I give the drives away,
other than smashing the drives to bits?
Thanks - jon
5 years, 2 months
getting rid of every trace of docker from fedora 29 for
re-install?
by Robert P. J. Day
as part of an intro tutorial i'm writing, i want to provide a recipe
for installing docker-ce on fedora 29 from absolute scratch, and part
of that will involve how to first get rid of every trace of any old
docker- or container-related stuff.
if one has no interest in preserving old containers, i'm proposing
running (as sudo, naturally):
$ dnf remove "*docker*"
$ rm -rf /var/lib/{containerd,docker,docker-engine}
i'm fairly sure that's overkill, but the point is to simulate truly
starting from scratch. the above *seems* to work, is there any reason
it would cause problems before i kick in with installing the proper
yum repo file and running:
$ dnf install docker-ce
thoughts?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca/dokuwiki
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
5 years, 2 months
After an update, VM's no longer have Internet access
by Patrick O'Callaghan
I updated my system this morning. Updated packages included a new
kernel and some SElinux stuff among other things (the complete list is
attached). I now find that neither of my QEMU/KVM guests (one Fedora,
one Windows 10) have Internet access, though they do have access to my
host. They were both working perfectly before the update. Nothing else
in my system has changed (in particular, I haven't touched the Firewall
rules and the last updates to NetworkManager or Qemu were several days
ago).
I rebooted to the previous kernel - no difference.
I set SElinux to permissive and rebooted the Fedora guest - no
difference.
Before trying to downgrade the entire update, is there anything else I
can do?
poc
5 years, 2 months
[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
5 years, 2 months
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
5 years, 2 months
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?
5 years, 2 months
