[digiKam-users] Long shot re Digikam impact on Drives

[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.

Thanks
Derek

--

[Gilles Caulier-4]

Hi,

Problem not know. HDD time life depend of a lots of factor, as temperature for ex.

Where is located the database files. At the same place ?

Gilles Caulier

2018-03-20 16:01 GMT+01:00 Derek Keats <[hidden email]>:

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.

Thanks
Derek

--

[woenx]

Just another user, but it seems unlikely that digikam had anything to do with
it. An improper shutdown or (I hope not) hardware issues are most likely the
cause.

Have you tried to recover the superblock?
https://linuxexpresso.wordpress.com/2010/03/31/repair-a-broken-ext4-superblock-in-ubuntu/



--
Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html

[Remco Viëtor]

On mardi 20 mars 2018 16:01:30 CET Derek Keats wrote:

> 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)
>

I don't see Digikam (or any other application) accessing the HDD directly,
that kind of thing is reserved for the system... Any chance it's an
intermittent fault on the motherboard connector or in the connection cable,
could you connect the drive to another port?

Remco

[Sveinn í Felli-2]

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.

Best regards,
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.
>
> Thanks
> Derek
>

[Derek Keats]

Thanks everyone. It was a long shot.

I have 7 hard drives. 

Three have failed, and only the ones that have photos on them. Two failed after < 2 months. 

The other 4 are used way more but are much older and never failed.

I was trying to figure out what the 3 had in common, so I thought it worth asking just in case.

I managed to fix this one, the other 2 are permed. 

Thanks
Derek

On Tue, Mar 20, 2018 at 5:09 PM, Gilles Caulier <[hidden email]> wrote:

Hi,

Problem not know. HDD time life depend of a lots of factor, as temperature for ex.

Where is located the database files. At the same place ?

Gilles Caulier

2018-03-20 16:01 GMT+01:00 Derek Keats <[hidden email]>:

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.

Thanks
Derek

--

--