On Wed, Oct 23, 2013 at 10:42:18AM +0200, Veljko wrote:
On Tue, Oct 22, 2013 at 12:24:42PM -0700, Gregory Nowak wrote:
On Tue, Oct 22, 2013 at 08:59:05AM +0200, Veljko wrote:
Do you guys have any advice for this? Should I first run dd on those
drives.
They are part of RAID, so it
Veljko wrote:
On Wed, Oct 23, 2013 at 10:42:18AM +0200, Veljko wrote:
On Tue, Oct 22, 2013 at 12:24:42PM -0700, Gregory Nowak wrote:
On Tue, Oct 22, 2013 at 08:59:05AM +0200, Veljko wrote:
Do you guys have any advice for this? Should I first run dd on those drives.
They are part of RAID, so
On Fri, Oct 25, 2013 at 08:51:22AM -0400, Miles Fidelman wrote:
Can't speak for the Seagates, but the WD Red series does seem
optimized for RAID (google TLER for background). It makes a huge
difference when you near end-of-life for the drives.
Thanks Miles, I'll probably go with WD Red.
On 23 Oct 2013, at 00:52, Celejar cele...@gmail.com wrote:
rdiff-backup is buggy (at least, it has at least one serious reported
bug, known for years but not even acknowledged by upstream), untouched
for years and apparently abandoned:
On Tue, Oct 22, 2013 at 12:24:42PM -0700, Gregory Nowak wrote:
On Tue, Oct 22, 2013 at 08:59:05AM +0200, Veljko wrote:
Do you guys have any advice for this? Should I first run dd on those drives.
They are part of RAID, so it should be difficult to read data from one drive
alone, but what is
On Tue, Oct 22, 2013 at 10:01:07PM +0100, Jonathan Dowland wrote:
is rsnapshot doing something different to usual: have you got a lot
more files in your backup? is it now having to delete old snapshots,
whereas before it hadn't hit some critical threshold? I found it to
scale very poorly when
On Wed, 23 Oct 2013 08:45:49 +0100
Jonathan Dowland j...@debian.org wrote:
On 23 Oct 2013, at 00:52, Celejar cele...@gmail.com wrote:
rdiff-backup is buggy (at least, it has at least one serious reported
bug, known for years but not even acknowledged by upstream), untouched
for years
Veljko wrote:
I'll try with their live CD on Monday when I get back to office. I'll also
try
with replacing SATA cables, just to be sure that they are not faulty and
responsible for performance degradation.
I run SeaTools and it turns out that only sdc drive passed the test. All other
drives
On Tue, Oct 22, 2013 at 08:59:05AM +0200, Veljko wrote:
Do you guys have any advice for this? Should I first run dd on those drives.
They are part of RAID, so it should be difficult to read data from one drive
alone, but what is the best way to be sure? And obviously, I'll have to return
more
is rsnapshot doing something different to usual: have you got a lot
more files in your backup? is it now having to delete old snapshots,
whereas before it hadn't hit some critical threshold? I found it to
scale very poorly when I was using it. rdiff-backup is almost a
drop-in replacement and
On Tue, 22 Oct 2013 22:01:07 +0100
Jonathan Dowland j...@debian.org wrote:
is rsnapshot doing something different to usual: have you got a lot
more files in your backup? is it now having to delete old snapshots,
whereas before it hadn't hit some critical threshold? I found it to
scale very
On Tue, 2013-10-22 at 19:52 -0400, Celejar wrote:
http://lists.debian.org/debian-user/2012/10/msg00182.html
At least it's better to backup more files than wanted, as to miss files
that are needed :D.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of
On Wed, 23 Oct 2013 02:40:27 +0200
Ralf Mardorf ralf.mard...@alice-dsl.net wrote:
On Tue, 2013-10-22 at 19:52 -0400, Celejar wrote:
http://lists.debian.org/debian-user/2012/10/msg00182.html
At least it's better to backup more files than wanted, as to miss files
that are needed :D.
Fair
On Fri, Oct 18, 2013 at 12:40:49PM -0400, mfidelman wrote:
I'm using Seagate ST3000DM001-9YN166 drives, not enterprise-class drives.
Ok... seagate probably writes error codes in that field. Try googling the
model number and smart, or raw_read_error. That might help you track things
down.
On Fri, Oct 18, 2013 at 07:31:55PM +0200, Andre Majorel wrote:
I've found, at least for the WD drives I use in my servers -
anything other than a 0 raw-read-error count is a sign of
near-term disk failure.
This is highly manufacturer dependent. In my experience, with
Seagate drives, it's
On Fri, Oct 18, 2013 at 06:50:11PM -0400, Miles Fidelman wrote:
Gregory Nowak wrote:
According to the above, I would say only sda and sdb are bad, sda
being the worst of the two. I stand to be corrected as always.
Yeah - that's what it looks like to me as well (having gotten back
to a
Veljko wrote:
On Fri, Oct 18, 2013 at 06:50:11PM -0400, Miles Fidelman wrote:
Gregory Nowak wrote:
According to the above, I would say only sda and sdb are bad, sda
being the worst of the two. I stand to be corrected as always.
Yeah - that's what it looks like to me as well (having gotten
On 19/10/13 11:36, Veljko wrote:
On Fri, Oct 18, 2013 at 07:31:55PM +0200, Andre Majorel wrote:
This is highly manufacturer dependent. In my experience, with
Seagate drives, it's normal to have Raw_Read_Error_Rate in the
tens or hundreds of millions.
Thanks for pointing this out. It does
Veljko wrote:
Hello,
I have 4 HDDs in software RAID10 for my backup server. I had help on this list
when I started to configure it and everything was working great for a year.
Last few days I noticed some load issues. During backup rotation of rsnapshot
load would go very high. I watched iotop
Hello Miles,
On Fri, Oct 18, 2013 at 11:43:59AM -0400, Miles Fidelman wrote:
Do a smartctl -A /dev/sd[abcd] - look for non-zero raw read errors
and reallocated sector counts. I've found, at least for the WD
drives I use in my servers - anything other than a 0 raw-read-error
count is a sign
Sent from my Verizon Wireless 4G LTE Smartphone
Original message
From: Veljko velj...@gmail.com
Date: 10/18/2013 12:26 PM (GMT-05:00)
To: debian-user@lists.debian.org
Subject: Re: Dying hard drive?
Hello Miles,
On Fri, Oct 18, 2013 at 11:43:59AM -0400, Miles Fidelman
On 2013-10-18 11:43 -0400, Miles Fidelman wrote:
Do a smartctl -A /dev/sd[abcd] - look for non-zero raw read errors
and reallocated sector counts.
And Current_Pending_Sector !
I've found, at least for the WD drives I use in my servers -
anything other than a 0 raw-read-error count is a sign
On Fri, Oct 18, 2013 at 06:26:38PM +0200, Veljko wrote:
IIUIC, this is output I should be looking:
sda:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED
WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 095 094 006Pre-fail Always
-
Gregory Nowak wrote:
On Fri, Oct 18, 2013 at 06:26:38PM +0200, Veljko wrote:
IIUIC, this is output I should be looking:
sda:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED
WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 095 094 006Pre-fail
On Sat, Dec 01, 2012 at 08:04:52PM +1300, Chris Bannister wrote:
Have a look at the /etc/inittab file.
I have:
# less /etc/inittab
[...]
# What to do when CTRL-ALT-DEL is pressed.
ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now
I'm fairly sure that X eats CTRL-ALT-DEL and init doesn't
On Du, 02 dec 12, 09:33:28, Jon Dowland wrote:
On Sat, Dec 01, 2012 at 08:04:52PM +1300, Chris Bannister wrote:
Have a look at the /etc/inittab file.
I have:
# less /etc/inittab
[...]
# What to do when CTRL-ALT-DEL is pressed.
ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now
I'm
On 12/1/12, Chris Bannister cbannis...@slingshot.co.nz wrote:
On Fri, Nov 30, 2012 at 01:38:33PM -0600, Nelson Green wrote:
with XScreenSaver. Under the old system I could hit Ctrl+Del+Alt and that
would invoke the screensaver and lock the screen. That functionality is
missing now.
get the
On Sat, Dec 01, 2012 at 09:53:30PM +1100, Zenaan Harkness wrote:
Does
Main Menu - Settings - Keyboard - Application Shortcuts
not work for Ctrl-Alt-Del?
No. Not everyone has Main Menu - Settings - etc. but everyone has an
/etc/inittab file.
--
If you're not careful, the newspapers will
I do appreciate the help, but we'll let Dell take care of this.
Just wanted to update anyone that might be interested. I was able to convince
Dell that the hard drive was bad after jumping through their hoops (in
their defence, I understand their position of not wanting to spend money on
On Fri, Nov 30, 2012 at 01:38:33PM -0600, Nelson Green wrote:
with XScreenSaver. Under the old system I could hit Ctrl+Del+Alt and that
would invoke the screensaver and lock the screen. That functionality is
missing now.
Ctrl+Alt+Del is supposed to be the three finger salute! :)
get the same
Date: Wed, 28 Nov 2012 00:24:13 +0100
From: pas...@plouf.fr.eu.org
To: debian-user@lists.debian.org
Subject: Re: Dying hard drive?
Jon Dowland a écrit :
On Tue, Nov 27, 2012 at 02:50:39PM -0600, Nelson Green wrote:
197 Current_Pending_Sector
First and foremost, double check that your SATA cables are properly
secure.
Install smartctl and run smartctl -a /dev/$disk0 (where $disk0
is e.g. sda); check to see if any of the various SMART attributes
indicate a problem.
Run a short, then a long SMART self test
smartctl -t short
First and foremost, double check that your SATA cables are properly
secure.
Yes, they are firmly seated. Good catch though.
Install smartctl
This is part of the smartmontools package. Took me a sec to find it, and I
mention it for anyone else following this.
and run smartctl -a /dev/$disk0
Hello,
Nelson Green a écrit :
and run smartctl -a /dev/$disk0 (where $disk0
is e.g. sda); check to see if any of the various SMART attributes
indicate a problem.
Run a short, then a long SMART self test
smartctl -t short /dev/$disk0
smartctl -t long /dev/$disk0
[...]
I did the short
Hello,
Nelson Green a écrit :
and run smartctl -a /dev/$disk0 (where $disk0
is e.g. sda); check to see if any of the various SMART attributes
indicate a problem.
Run a short, then a long SMART self test
smartctl -t short /dev/$disk0
smartctl -t long /dev/$disk0
[...]
I did
On Tue, Nov 27, 2012 at 02:50:39PM -0600, Nelson Green wrote:
197 Current_Pending_Sector 0x0032 200 200 000 Old_age
Always - 12
I think this is bad.
Num Test_Description Status Remaining LifeTime(hours)
LBA_of_first_error
# 1 Short offline
I think this is bad.
Num Test_DescriptionStatus Remaining LifeTime(hours)
LBA_of_first_error
# 1 Short offline Completed: read failure 90% 2718
529598095
# 2 Short offline Completed: read failure 90% 2718
Jon Dowland a écrit :
On Tue, Nov 27, 2012 at 02:50:39PM -0600, Nelson Green wrote:
197 Current_Pending_Sector 0x0032 200 200 000Old_age Always
- 12
I think this is bad.
Yes, but that can often be corrected using the embedded reallocation
mechanism. By corrected I
38 matches
Mail list logo
