Debian User Forums

Actually, it says the opposite: echo repair > /sys/block/mdX/md/sync_action Only valid for parity raids - this will also check the integrity of the data as it reads it, and rewrite a corrupt stripe. It will terminate immediately without doing anything if the array is degraded, as it cannot recalcula...

Hi. Just a quick bump here.

I find it hard to believe that the benevolent maintainers at Debian would remove this utility without having something (better) to replace it... yet I cannot find any evidence of it. Surely they have something...

Anyone?

Thanks.

G

Yes, I saw that was some time ago... what was that then etch? lenny? I figured they would have it back in by now. Since it isn't there, is there something else that should be used to scrub a RAID6? Even the contemporary docs on mdadm say not to echo into proc for RAID6.... they still say that radi6c...

Hi. I have installed my first buster OS. It includes a large raid 6 volume (md raid). I have mdadm installed, but I cannot find the raid6check utility anywhere on the system. I've been googling, and I've been reviewing the man pages, and searching the system. I cannot find it anywhere for Buster. It...

What does 'aptitude -s full-upgrade' show? It shows that everything is up to date. What I wound up doing is doing a 'dpkg -l |awk '{print $2}' and dumping that to a file. I then did a little ad-hoc script to step through each with an 'aptitude -s -y reinstall', and dumped that output to a file. I t...

Maybe not so well. Check to see everything got upgraded - seems you might have a version mismatch between curl and the required libraries. Yeah... maybe not so well after all... Weird thing is, at boot, all my startup scripts say "OK"... and many of them are definitely not OK. I've been b...

Hi, I have updated from jessie to stretch today, and for the most part, it went pretty well. Since the upgrade, however, the one snag I was not able to fix was that of curl. When I run curl -V, I get: curl: symbol lookup error: /usr/lib/x86_64-linux-gnu/libcurl.so.4: undefined symbol: libssh2_scp_re...

Ok... just found this...

https://bugs.debian.org/cgi-bin/bugrepo ... bug=831007

However, it looks like it was demoted to "wishlist"... I don't understand that... it is pretty huge..

Hi. For years I have been backing up systems using tar and the -X (or --exclude) options. Now that I have upgraded some systems to Stretch, I find that it no longer works -- on any of these systems. Normall I'd do something like this: tar -cpjvf /mnt/smbmountedfolder/mysystem.tar.bzw ./* -X /etc/xcl...

is your /home on a different partition? If so then just install Stretch from scratch so to speak....Stretch scratch kinda sounds like an Ubuntu release... :lol: I find it difficult to fathom that your sources were not mangled prior to the upgrade attempt. It is rediculuosly easy to upgrade Debian (...

well, probably because the instructions came from someone called linuxbabe....geez..unofficial much better luck with this, I would bet: https://www.debian.org/releases/stable/i386/release-notes/ch-upgrading.en.html Thanks. The instructions do pretty much the same thing the "babe" suggests...

I pretty much followed this: https://www.linuxbabe.com/debian/upgrade-debian-8-jessie-to-debian-9-stretch deb http://ftp.us.debian.org/debian stable main contrib non-free deb-src http://ftp.us.debian.org/debian stable main contrib non-free deb http://ftp.debian.org/debian/ stretch-updates main contr...

Hi. I just updated to stretch today (from Jessie). Now my system will not start key services. I have RT installed on this system (its primary function), and no one can log in. I'm getting weird systemd errors at login, but they are not verbose, and I cannot find anymore information on this. I just s...

Hi. I've been trying to get this to work for hours now, and no matter what I try, it seems that my re-write attempts using Exim4 are thwarted. First, I am operating under the assumption that this is done in the /etc/exim4/conf.d/rewrite/31_exim4-config_rewriting file (though I have also tried using ...

OK... I noticed something. I had /usr/bin/qemu-x86_64... that isn't right... it exists, but that is not used to start the image. I'm supposed to use qemu-system-x86_64 . So, yes, it seems to start using just qemu. But now I have different error output: libxl: error: libxl_qmp.c:287:qmp_handle_error_...

Apparently it doesn't make any difference. I set this line in /etc/default/grub.conf: linux /vmlinuz-3.16.0-4-amd64 root=UUID=26ee948d-43a0-48d0-98ac-844ae56cba0c ro video=1024x768 init=/lib/sysvinit/init quiet I did notice, however, if I power up from a powered-off state (not a warm boot), that I d...

Sure:

ls -l /etc/systemd/system|grep default

I hear you. Switching to systemd is something I'd rather not do... but I'm trying :) It was true, Head_on_a_stick, it was set to graphical target, when I have no graphical environment set up on this system. So, I did as you suggested, but unfortunately, it didn't change anything. Here is what I did:...

I don't know if this is a really dumb solution to offer, but did the location of your binaries change? that's what your error output seems to suggest. -RJ Hi RJ, I don't see where you are getting that from: libxl: error: libxl_dm.c:1388:device_model_spawn_outcome: domain 21 device model: spawn fail...

Hello, I finally bit the bullet today, and upgraded my servers to Jessie. One of these servers is a Xen server. On this server I have 4 other debian systems installed as paravitual instances, and two windows machines as hvm (windows server 2003 and windows 7). I don't care that much about the server...