Le mardi 08 août 2017 à 15:52 +0000, james a écrit :

Patrick Shanahan:

...

...

I have been using the Backups gui program that I believe is provided by MATE but I use KDE. The shortcut resides in the System option in the Menu. I had a TW install a few days back and this worked perfectly for me.

and that backup program is what?  perhaps duplicity?

The program is literally called Backups, I have not seen it in KDE but it shows up when I install some MATE stuff. It is a GUI program in the System folder in the Menu selection.

This is probably deja-dup. -- Frederic Crozat Enterprise Desktop Release Manager SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

* james [01-01-70 12:34]:

Patrick Shanahan:

...

...

I have been using the Backups gui program that I believe is provided by MATE but I use KDE. The shortcut resides in the System option in the Menu. I had a TW install a few days back and this worked perfectly for me.

and that backup program is what? perhaps duplicity?

The program is literally called Backups, I have not seen it in KDE but it shows up when I install some MATE stuff. It is a GUI program in the System folder in the Menu selection.

from the command-line: rpm -qf `which Backups` I cannot find an opensuse package providing "Backups". you are going to have to explain what this program is and where it comes from. I am using Tw and have for years and cannot find anything providing "Backups" for openSUSE. just might explain why you are getting errors.

...

...

I am again using TW, second install, both installs were upgrades. When I use this Backups program, it throws an external window showing this:

http://susepaste.org/72088551

...

what does (as root): zypper ver provide?

That says "unknown command"

sorry, should be: zypper ve

...

are you really getting disk errors, re subject, or just getting errors from program output?

This error above appears to be from the program.

-- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 2017-08-08 18:57, james wrote:

Patrick Shanahan:

...

* james <> [01-01-70 12:34]:

...

Patrick Shanahan:

from the command-line: rpm -qf `which Backups`

I cannot find an opensuse package providing "Backups". you are going to have to explain what this program is and where it comes from.

I am using Tw and have for years and cannot find anything providing "Backups" for openSUSE.

just might explain why you are getting errors.

sudo rpm -qf `which Backups` which: no Backups in (/home/katnip/bin:/usr/local/bin:/usr/bin:/bin) rpm: no arguments given for query -- now you're making me paranoid after seeing it in two installs.

When you are running it, open a terminal and run "ps afxu | less -S" and search the output for the program, probably near the bottom. Identify the actual command line. The menu entry for the program may be called "backup" and be different from the actual program name. cer@Telcontar:~> rpm -qa | grep -i backup storeBackup-3.5-7.1.noarch rdiff-backup-1.2.8-28.3.x86_64 cer@Telcontar:~> -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)

Carlos E. R.:

On 2017-08-08 20:23, Carlos E. R. wrote:

...

When you are running it, open a terminal and run "ps afxu | less -S" and search the output for the program, probably near the bottom. Identify the actual command line.

The menu entry for the program may be called "backup" and be different from the actual program name.

cer@Telcontar:~> rpm -qa | grep -i backup storeBackup-3.5-7.1.noarch rdiff-backup-1.2.8-28.3.x86_64 cer@Telcontar:~>

Your's will be "duplicity", from your posted error output.

I've pretty much given up, dd doesnt work either, neither ext drive. I'm resigned to it not working. :/ jim -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

* Carlos E. R. [08-08-17 15:29]:

On 2017-08-08 20:36, james wrote:

...

Carlos E. R.:

...

I've pretty much given up, dd doesnt work either, neither ext drive. I'm resigned to it not working. :/

What error gives 'dd'?

That drive is special:

I/O size (minimum/optimal): 4096 bytes / 33553920 bytes

and how are you invoking "dd"? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 2017-08-08 21:53, james wrote:

Patrick Shanahan:

...

* Carlos E. R. [08-08-17 15:29]:

...

On 2017-08-08 20:36, james wrote:

...

Carlos E. R.:

...

I've pretty much given up, dd doesnt work either, neither ext drive. I'm resigned to it not working. :/

What error gives 'dd'?

That drive is special:

I/O size (minimum/optimal): 4096 bytes / 33553920 bytes

and how are you invoking "dd"?

dd if=/dev/sda3 of=/dev/sdb1

dd if=/dev/sda3 of=/dev/sdb1 bs=64K conv=noerror,sync

Why sync? It will go terribly slow in your situation. Try bs=32M or bigger. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)

Carlos E. R.:

On 2017-08-08 21:53, james wrote:

...

Patrick Shanahan:

...

* Carlos E. R. [08-08-17 15:29]:

Try bs=32M or bigger.

dd still hangs and does nothing

Carlos E. R.:

On 2017-08-08 22:24, james wrote:

...

Carlos E. R.:

...

On 2017-08-08 21:53, james wrote:

...

Patrick Shanahan:

...

* Carlos E. R. <> [08-08-17 15:29]:

...

Try bs=32M or bigger.

dd still hangs and does nothing

Sigh :-(

Anything in syslog?

http://susepaste.org/34545492 very very long -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Carlos E. R.:

On 2017-08-08 20:36, james wrote:

...

Carlos E. R.:

...

I've pretty much given up, dd doesnt work either, neither ext drive. I'm resigned to it not working. :/

What error gives 'dd'?

That drive is special:

I/O size (minimum/optimal): 4096 bytes / 33553920 bytes

just hangs forever, doesnt do anything -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Bengt Gördén:

Den 2017-08-08 kl. 21:49, skrev james:

...

...

...

just hangs forever, doesnt do anything

hw failure? Try put the drive on another USB-port (it's USB, right?). Check with lsusb -t to see your options. I had to move a USB-disk a year ago due to lack of power on that port. You can also check for hw failure on a disk with smartctl -a (as root). It'll give you a abundance of info.

smartctl -a /dev/sdb

To rule out software problem I'd try a live-disk of some sort and see if it works. My favorite is knoppix (I'm old, I know). If it works with that it's most likely something in opensuse.

http://susepaste.org/43553632 I also ran a 2 hour test this morning with GSmartControl with no errors on it. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 2017-08-08 22:47, james wrote:

http://susepaste.org/43553632

There are hardware errors logged in the last hour. What they mean I have no idea: 9 Power_On_Hours 0x0012 082 082 000 Old_age Always - 7970 ... Error 22 occurred at disk power-on lifetime: 7970 hours (332 days + 2 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 a0 60 fd 00 03 Error: ICRC, ABRT at LBA = 0x0300fd60 = 50396512 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 61 00 18 00 05 01 40 00 00:04:35.217 WRITE FPDMA QUEUED 61 00 10 00 01 01 40 00 00:04:35.217 WRITE FPDMA QUEUED 61 00 08 00 fd 00 40 00 00:04:35.217 WRITE FPDMA QUEUED 61 00 00 00 f9 00 40 00 00:04:35.213 WRITE FPDMA QUEUED 61 00 18 00 f5 00 40 00 00:04:34.481 WRITE FPDMA QUEUED -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)

On 2017-08-08 23:32, james wrote:

Carlos E. R.:

...

On 2017-08-08 22:47, james wrote:

...

http://susepaste.org/43553632

There are hardware errors logged in the last hour. What they mean I have no idea:

9 Power_On_Hours 0x0012 082 082 000 Old_age Always - 7970

...

Error 22 occurred at disk power-on lifetime: 7970 hours (332 days + 2 hours) When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 a0 60 fd 00 03 Error: ICRC, ABRT at LBA = 0x0300fd60 = 50396512

Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 61 00 18 00 05 01 40 00 00:04:35.217 WRITE FPDMA QUEUED 61 00 10 00 01 01 40 00 00:04:35.217 WRITE FPDMA QUEUED 61 00 08 00 fd 00 40 00 00:04:35.217 WRITE FPDMA QUEUED 61 00 00 00 f9 00 40 00 00:04:35.213 WRITE FPDMA QUEUED 61 00 18 00 f5 00 40 00 00:04:34.481 WRITE FPDMA QUEUED

Well, a few weeks ago, this worked great, i mean great. Today and the last few days, not at all. I am inclined to think it is not hardware since it passed GSmartControl with flying colors. I think something is wrong in the install. Something is missing or misconfigured. I probably either need to Download TW ISO and go clean install or try another distro. Not sure at this point.

No, the above are disk internal errors. Firmware, or you can say hardware errors. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)

* james [08-08-17 21:26]: [...]

If you would like I can include as an attachment

***no*** post it on susepaste or dropbox or google or ....

the results of the GSmartControl test that contradicts what you say about the hardware. Also, the drive is 6 months old from Apple as is the cord. Got news for ya, Apple don't make junk that goes bad in 6 months.

anyone can have a production problem and sub-par/defects sneak out.

This worked fine in the last install which was just days or weeks ago. Now, it is crap.

shit happens

So, tell me more how this is on my end and worship this faulty software. I am about on the verge of leaving SUSE, I'm sure you'd miss me... tired of this blame game and offering little real help. IRC is about as useful as tits on a boar too.

grow up. your failure and/or inability to provide requested information and properly describe conditions to affect a solution are not on us. we routinely attach remote drives and boot from them and backup to them using openSUSE. I have a usb stick running Tw I use for trouble shooting windows computers and I can update it and add/subtract applications .... -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 2017-08-09 03:24, james wrote:

Carlos E. R.:

...

On 2017-08-08 23:32, james wrote:

...

Carlos E. R.:

...

On 2017-08-08 22:47, james wrote:

...

http://susepaste.org/43553632

There are hardware errors logged in the last hour. What they mean I have no idea:

9 Power_On_Hours 0x0012 082 082 000 Old_age Always - 7970

...

Error 22 occurred at disk power-on lifetime: 7970 hours (332 days + 2 hours) When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 a0 60 fd 00 03 Error: ICRC, ABRT at LBA = 0x0300fd60 = 50396512

Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 61 00 18 00 05 01 40 00 00:04:35.217 WRITE FPDMA QUEUED 61 00 10 00 01 01 40 00 00:04:35.217 WRITE FPDMA QUEUED 61 00 08 00 fd 00 40 00 00:04:35.217 WRITE FPDMA QUEUED 61 00 00 00 f9 00 40 00 00:04:35.213 WRITE FPDMA QUEUED 61 00 18 00 f5 00 40 00 00:04:34.481 WRITE FPDMA QUEUED

Well, a few weeks ago, this worked great, i mean great. Today and the last few days, not at all. I am inclined to think it is not hardware since it passed GSmartControl with flying colors. I think something is wrong in the install. Something is missing or misconfigured. I probably either need to Download TW ISO and go clean install or try another distro. Not sure at this point.

No, the above are disk internal errors. Firmware, or you can say hardware errors.

If you would like I can include as an attachment the results of the GSmartControl test that contradicts what you say about the hardware.

Doesn't matter. It is your own hardware which is reporting errors. That log above comes directly from inside the disk: smartctl just reads it, doesn't generate it. That doesn't mean that the error is fatal or permanent. I have disks that once had hardware errors and they are still working fine many years later. I don't know what that hardware error on your disk means. I just say that your disk reported errors about the time you were doing the backup and that could explain dd failing. Plus, your disk is not a normal disk. This line, which I have seen twice recently: I/O size (minimum/optimal): 4096 bytes / 33553920 bytes is very strange. The other chap can not boot from his disk, but he can read/write to it.

Also, the drive is 6 months old from Apple as is the cord. Got news for ya, Apple don't make junk that goes bad in 6 months. This worked fine in the last install which was just days or weeks ago. Now, it is crap. So, tell me more how this is on my end and worship this faulty software. I am about on the verge of leaving SUSE, I'm sure you'd miss me... tired of this blame game and offering little real help. IRC is about as useful as tits on a boar too.

This is absurd. It is not a question of who blames who. If you want to use Linux, you have to be prepared to work, and not surrender that easily. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)

Dne úterý 8. srpna 2017 18:19:00 CEST, james napsal(a):

Vojtěch Zeisek:

...

Dne úterý 8. srpna 2017 13:44:00 CEST, james napsal(a):

Duplicity requires several Python packages. If I remember correctly, I had to manually install python-paramiko, python-pycrypto, python-ecdsa, might be something else. After it duplicity worked correctly. I think, as it has many possibilities, it doesn't have these packages as required.

I install as many as the ones you mentioned plus a few from some web sites and I still get this:

http://susepaste.org/89123762

This is weird. What is the complete command? Do all backed up files have names with only ASCII characters? -- Vojtěch Zeisek https://trapa.cz/

Dne úterý 8. srpna 2017 18:31:00 CEST, james napsal(a):

Vojtěch Zeisek:

...

Dne úterý 8. srpna 2017 18:19:00 CEST, james napsal(a):

...

Vojtěch Zeisek:

...

Dne úterý 8. srpna 2017 13:44:00 CEST, james napsal(a):

Duplicity requires several Python packages. If I remember correctly, I had to manually install python-paramiko, python-pycrypto, python-ecdsa, might be something else. After it duplicity worked correctly. I think, as it has many possibilities, it doesn't have these packages as required.

I install as many as the ones you mentioned plus a few from some web sites and I still get this:

http://susepaste.org/89123762

This is weird. What is the complete command? Do all backed up files have names with only ASCII characters?

It is just a GUI program. No commands that I'm currently aware of. The files I want are from my /home dir.

Sorry, I never used Déjà Dup https://wiki.gnome.org/action/show/Apps/DejaDup It is what You use, isn't it? I regularly use Duplicity (internally used by Déjà Dup), but I have no idea how Déjà Dup is working with it... :-( -- Vojtěch Zeisek https://trapa.cz/

Hello, Am Dienstag, 8. August 2017, 18:31:00 CEST schrieb james:

Vojtěch Zeisek:

...

Dne úterý 8. srpna 2017 18:19:00 CEST, james napsal(a):

...

Vojtěch Zeisek:

...

Dne úterý 8. srpna 2017 13:44:00 CEST, james napsal(a):

Duplicity requires several Python packages. If I remember correctly, I had to manually install python-paramiko, python-pycrypto, python-ecdsa, might be something else. After it duplicity worked correctly. I think, as it has many possibilities, it doesn't have these packages as required.

Did you ask/tell the package maintainer about these dependencies? They are not even listed as Recommends, so IMHO this might count as a bug.

...

...

I install as many as the ones you mentioned plus a few from some web sites and I still get this:

http://susepaste.org/89123762

This is weird. What is the complete command? Do all backed up files have names with only ASCII characters?

It is just a GUI program. No commands that I'm currently aware of. The files I want are from my /home dir.

Reading the backtrace indicates that Vojtěch's question points in the right direction - duplicity probably fails at a filename that is not valid utf-8. Unfortunately the error handler also breaks at the invalid utf-8 which makes debugging this harder :-( You can try comment out line 79 of /usr/lib64/python2.7/site-packages/ duplicity/util.py by prepending a # # e = unicode(e).encode('utf-8') This won't fix your problem, but with some luck you'll at least get a useful error message ;-) Please open a bugreport for duplicity - assuming that filenames are always valid utf-8 is quite optimistic. Handling them as binary is a better idea. Regards, Christian Boltz -- für die Bewertung des Risikos gilt Martins Hypothese: Das Risiko ist proportional zur Größe der Schlagzeile in der BILD-Zeitung. [Martin zu http://blog.koehntopp.de/archives/3211-Wieso-wir-uns-veroeffentlichen.html] -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 08-08-17 19:24, Christian Boltz wrote:

Hello,

Am Dienstag, 8. August 2017, 18:31:00 CEST schrieb james:

...

Vojtěch Zeisek:

...

Dne úterý 8. srpna 2017 18:19:00 CEST, james napsal(a):

...

Vojtěch Zeisek:

...

Dne úterý 8. srpna 2017 13:44:00 CEST, james napsal(a):

Duplicity requires several Python packages. If I remember correctly, I had to manually install python-paramiko, python-pycrypto, python-ecdsa, might be something else. After it duplicity worked correctly. I think, as it has many possibilities, it doesn't have these packages as required.

Did you ask/tell the package maintainer about these dependencies? They are not even listed as Recommends, so IMHO this might count as a bug.

There has been a bugreport on Duplicity dependencies earlier: https://bugzilla.opensuse.org/show_bug.cgi?id=1047137 Regards