Prev: Debian Install stalls at 5% (at least for 3 hours, don't know if it suffices to designate this state as `stall')
Next: Bug after unstable upgrade
From: Andrei Popescu on 1 Jul 2010 03:40
On Mi, 30 iun 10, 17:34:22, H.S. wrote:

> So now I know that my backups most probably are not trustworthy, the
> ones from the last four or so days. No problem. I do rolling backups
> using cron and rsync. But what I do now? Do I just delete the backups
> from the last four days and resume regular ones?

Don't you have some method of checking the integrity of you backups?
(http://www.taobackup.com/integrity.html)

> How risky is the
> partition even though the manufacturer's diagnostic utility reports no
> errors now.

It is considered that a modern drive developing bad sectors visible to
the system[1] is not to be trusted.

[1] drives are remapping bad sectors internally, until they run out of
spare sectors.

> Another thing, I get this when I log in to a console, what is it all about?
> #-------------------------------------------------------------#
> Last login: Wed Jun 30 17:23:40 EDT 2010 from localhost on pts/9
> /etc/update-motd.d/20-cpu-checker: line 3:
> /usr/lib/update-notifier/update-motd-cpu-checker: No such file or directory
> /etc/update-motd.d/20-cpu-checker: line 3: exec:
> /usr/lib/update-notifier/update-motd-cpu-checker: cannot execute: No
> such file
> or directory
> run-parts: /etc/update-motd.d/20-cpu-checker exited with return code 126
> /etc/update-motd.d/90-updates-available: line 3:
> /usr/lib/update-notifier/update-motd-updates-available: No such file or
> directory
> /etc/update-motd.d/90-updates-available: line 3: exec:
> /usr/lib/update-notifier/update-motd-updates-available: cannot execute:
> No such file or directory
> run-parts: /etc/update-motd.d/90-updates-available exited with return
> code 126
> /etc/update-motd.d/98-reboot-required: line 3:
> /usr/lib/update-notifier/update-motd-reboot-required: No such file or
> directory
> /etc/update-motd.d/98-reboot-required: line 3: exec:
> /usr/lib/update-notifier/update-motd-reboot-required: cannot execute: No
> such file or directory
> run-parts: /etc/update-motd.d/98-reboot-required exited with return code 126

This looks like filesystem corruption, did you fsck the drive/partition?

Regards,
Andrei
--
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
From: Andrei Popescu on 2 Jul 2010 03:40
On Jo, 01 iul 10, 18:42:26, H.S. wrote:
>
> Okay, did all these, but that set of file not found errors upon console
> login is still there.

They are probably gone. If you want to try to repair the system (versus
reinstalling from scratch) you can just reinstall each package
containing the missing files (dpkg -S or apt-file can help).

You might need the --force-confmiss option to dpkg.

Regards,
Andrei
--
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
From: lee on 2 Jul 2010 07:20
On Wed, Jun 30, 2010 at 05:34:22PM -0400, H.S. wrote:
>
> So now I know that my backups most probably are not trustworthy, the
> ones from the last four or so days. No problem. I do rolling backups
> using cron and rsync. But what I do now?

Now you buy at least two new disks, preferably some that are rated for 24/7,
set them up as a RAID-1 (or RAID-5) with mdadm and copy your data onto
the RAID as best as you can.

NEVER keep data on a single disk only.


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/20100702110941.GK8185(a)yun.yagibdah.de
 | 
Pages: 1
Prev: Debian Install stalls at 5% (at least for 3 hours, don't know if it suffices to designate this state as `stall')
Next: Bug after unstable upgrade