[digiKam-users] Long shot re Digikam impact on Drives
Sveinn í Felli
sv1 at fellsnet.is
Tue Mar 20 16:04:50 GMT 2018
Twice I have run into this kind of a problem (not related to DigiKam):
First I slaughtered a couple of HDDs and could trace it to faulty
RAM-modules (got plenty of segfaults), the second was a broken e-PCI
socket (swapped the cable from the HDD to another socket) which cost me
another couple of HDDs.
But both were really due to lack of proper earthing of my house/street
(which was supposed to be via the once metallic geothermal water-pipes,
then a genius from the municipality replaced them with plastic tubes and
did not lay any copper earthing for replacement...) ;-(
Lost at least 3 motherboards and a bunch of other gear because of this.
Sveinn í Felli
Þann þri 20.mar 2018 15:01, skrifaði Derek Keats:
> Hi Folks,
> This is a long shot, but has anyone ever experienced Digikam having an
> impact on HDD life? I am on my third 4Tb hard drive in 3 months (Ubuntu
> 17.10, Gnome). The drive won't mount, and when I try to mount it, I get
> Error mounting system-managed device /dev/sdb: Command-line `mount
> "/photos/ exited with non-zero status 32: mount:P/photos: can't read
> superblock on /dev/sdb.
> (udisks-error-quark, 0)
> Is there any possibility at all that Digikam could cause this? The disk
> only has photos, and I only use Digikam to manage them.
> I don';t want to replace it if there is any possibility that this could be
> caused by Digikam. I know it is a long shot, but I have to ask.
More information about the Digikam-users