pastebin.com/f5a5c595a
i just started badblocks -w
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1266236447.26031.8.ca...@ubuntu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vadkan Jozsef wrote:
> We have a samsung hdd, that keeps falling out of raid, but there are no
> bad blocks on it, according to "badblocks" prog.
>
> we would like to return it [warranty], but it would be better to find
> e.g
> Date: Wed, 10 Feb 2010 00:39:35 -0600
> From: s...@hardwarefreak.com
> To: debian-user@lists.debian.org
> Subject: Re: how to find bad blocks
>
> Vadkan Jozsef put forth on 2/9/2010 11:44 AM:
> > Besides the badblocks app?
> >
> > We have a samsung hdd,
Vadkan Jozsef put forth on 2/9/2010 11:44 AM:
> Besides the badblocks app?
>
> We have a samsung hdd, that keeps falling out of raid, but there are no
> bad blocks on it, according to "badblocks" prog.
This is probably because there are no bad blocks on it.
> w
I don't think you can trust programs
such as badblocks or ddrescue to accurately map bad "blocks" on the drive.
Since a logical device like /dev/sda1 would represent more than one physical
disk badblocks might be able to tell you that the array is failing or degraded,
but mapping
On Tue, 09 Feb 2010 18:44:02 +0100, Vadkan Jozsef wrote:
> Besides the badblocks app?
>
> We have a samsung hdd, that keeps falling out of raid, but there are no
> bad blocks on it, according to "badblocks" prog.
>
> we would like to return it [warranty], but it w
#include
* James Zuelow [Tue, Feb 09 2010, 08:58:15AM]:
> Can you get SMART data from it?
>
> I don't think you can list the bad blocks that the drive is re-mapping, but
> you can certainly get the number of times the drive has had to do that.
>
> The manpage for sm
Hi,
On Tue, 09 Feb 2010 18:44:02 +0100
Vadkan Jozsef wrote:
> We have a samsung hdd, that keeps falling out of raid, but there are no
> bad blocks on it, according to "badblocks" prog.
Did you use the write scan? (parameter -w for destructive write, -n for
non-destructive writ
On 10-02-09 12:44:02, Vadkan Jozsef wrote:
> Besides the badblocks app?
>
> We have a samsung hdd, that keeps falling out of raid, but there are
> no bad blocks on it, according to "badblocks" prog.
>
> we would like to return it [warranty], but it would be better to
> -Original Message-
> From: Vadkan Jozsef [mailto:jozsi.avad...@gmail.com]
> Sent: Tuesday, 09 February, 2010 08:44
> To: Debian User Mailing list
> Subject: how to find bad blocks
>
> Besides the badblocks app?
>
> We have a samsung hdd, that keeps fallin
Besides the badblocks app?
We have a samsung hdd, that keeps falling out of raid, but there are no
bad blocks on it, according to "badblocks" prog.
we would like to return it [warranty], but it would be better to find
e.g. bad blocks on it..:\ :D
thank you!
--
To UNSUBSCRIBE, email
On Sat, 07 Nov 2009 17:43 -0800, whollyg...@letterboxes.org wrote:
> Anybody know what's going on or can help debug
> this at least?
>
> Running squeeze I am having trouble reformatting a
>
> * 64MB memory stick and a
> * 160GB 2.5" HD in a USB linked
> external enclosure
>
> using "m
whollyg...@letterboxes.org wrote:
On Sun, 08 Nov 2009 09:46 +, "John Allen"
wrote:
whollyg...@letterboxes.org wrote:
Anybody know what's going on or can help debug
this at least?
Running squeeze I am having trouble reformatting a
* 64MB memory stick and a
* 160GB 2.5" HD in
On Sun, 08 Nov 2009 09:46 +, "John Allen"
wrote:
> whollyg...@letterboxes.org wrote:
> > Anybody know what's going on or can help debug
> > this at least?
> >
> > Running squeeze I am having trouble reformatting a
> >
> > * 64MB memory stick and a
> > * 160GB 2.5" HD in a USB linked
> >
I can report the same happens on Lenny with the latest amd64 kernel.
In both cases the process hung while checking for
bad blocks. ps shows the process to be in
uninteruptible sleep. man ps says that it is
probably related to IO.
I eventually got the memory stick to finish but
the external HD
Anybody know what's going on or can help debug
this at least?
Running squeeze I am having trouble reformatting a
* 64MB memory stick and a
* 160GB 2.5" HD in a USB linked
external enclosure
using "mkdosfs -c /dev/sd{ag}1".
In both cases the process hung while che
, but it is still
running. What should I do, just quit it?
~$ /sbin/mke2fs -c /dev/sda1
sda??? Is your boot disk hda?
Is it plugged into a USB 1.1 port?
Also, I wouldn't be surprised if "check bad blocks" weren't
inordinately slow even on internal disks.
mke2fs 1
On 2009-08-09 05:25, hce wrote:
Thanks Sven. Will it be any problem if I quit it by pressing Ctr-c? If
I understand it correctly, the mke2fs -c is only check the bad block,
not write or format the disk, right?
No problem.
--
Scooty Puff, Sr
The Doom-Bringer
--
To UNSUBSCRIBE, email to debia
Thanks Sven. Will it be any problem if I quit it by pressing Ctr-c? If
I understand it correctly, the mke2fs -c is only check the bad block,
not write or format the disk, right?
By the way, it has not reached the maximum blocks yet, but it seems it
need to run another 3 days to finishe it. I canno
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632,
> 2654208,
> 4096000, 7962624, 11239424, 2048, 23887872, 71663616, 78675968,
> 10240, 214990848
>
> Checking for bad blocks (read-only test):25582272/ 244190007
Assuming bad bloc
On 2009-08-09 11:51 +0200, hce wrote:
> Hi,
>
> I have beening running following command to check an external USB 1 TB
> disk for more than 15 hours. I am not clear if the right corner of
> 244190007 is the maxinum blocks it should check or not. If it is, it
> seems that it has already exceeded th
,
10240, 214990848
Checking for bad blocks (read-only test):25582272/ 244190007
Thank you.
Kind Regards,
Jupiter
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
2009/6/17 Tzafrir Cohen
> On Wed, Jun 17, 2009 at 10:03:52AM +0800, Umarzuki Mochlis wrote:
> > I need to copy files from a ntfs formatted hd to a ntfs hd. What tool
> should
> > i use?
> >
> > Note: I only need to copy files and directories, not making disk image
>
> If you have a problem readin
On Wed, Jun 17, 2009 at 10:03:52AM +0800, Umarzuki Mochlis wrote:
> I need to copy files from a ntfs formatted hd to a ntfs hd. What tool should
> i use?
>
> Note: I only need to copy files and directories, not making disk image
If you have a problem reading from the disk itself, consider startin
On Wed, Jun 17, 2009 at 10:03:52AM +0800, Umarzuki Mochlis wrote:
> I need to copy files from a ntfs formatted hd to a ntfs hd. What tool should
> i use?
>
> Note: I only need to copy files and directories, not making disk image
Hi,
You can use ntfs-3g. First, install it by running "aptitude in
I need to copy files from a ntfs formatted hd to a ntfs hd. What tool should
i use?
Note: I only need to copy files and directories, not making disk image
TIA
--
Regards,
Umarzuki Mochlis
http://gameornot.net
(I had no idea one could recover bad
sectors. I thought they were as good as gone.) Then I ran the test
again to get the LBA address of the second bad block. Surprise,
surprise, the test completed without problems.
I also tried booting off a live CD and running e2fsck -c -c on all
ext2/3 partiti
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Davide Mancusi wrote:
> The hard disk of my 4-year-old laptop is starting to fail. I ran
> fsck.ext3 -c on my root partition yesterday and a few blocks were
> marked as damaged. The blocks contained some XFCE4 theme files, so I
> thought that reinstall
Hello everyone,
The hard disk of my 4-year-old laptop is starting to fail. I ran
fsck.ext3 -c on my root partition yesterday and a few blocks were
marked as damaged. The blocks contained some XFCE4 theme files, so I
thought that reinstalling the relevant package should be enough. Now,
however, the
Christopher - thanks for the clarications.
--
Haines Brown, KB1GRM
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Wed, 13 Feb 2008 11:12:52 -0500
Haines Brown <[EMAIL PROTECTED]> wrote:
> I gather one can use the e2fsck with -c option to have it call
> /sbin/badblocks to report bad blocks on an unmounted partition.
This option causes e2fsck to use badblocks(8) program to do a
read-
I gather one can use the e2fsck with -c option to have it call
/sbin/badblocks to report bad blocks on an unmounted partition.
1. Although the -c option causes fsck to use badblocks to identify any
bad blocks present, does e2fsck then proceed to use this information to
fix corruption as usual
Hi,
my power supply switched off suddenly last week while
I was doing some update of system files last week.
Since then, I am not able to boot the 2.6.13.4 kernel
(with udev support) anymore, more specifically, my
/home parition cannot be mounted and booting stops
with the message:
"fsck.ext3: No
on Sat, Jun 26, 2004 at 08:02:17PM -0400, Ben Russo ([EMAIL PROTECTED]) wrote:
> I have an 80GB hard disk.
> badblocks shows that it has about 78M blocks.
> The first 50 million or so can be checked (write patterns)
> for many days with no problems.
> Beyond that I start to get errors.
>
> Does an
Ben Russo wrote:
I have an 80GB hard disk.
badblocks shows that it has about 78M blocks.
The first 50 million or so can be checked (write patterns)
for many days with no problems.
Beyond that I start to get errors.
Does anyone have any experience with creating a partition
in the "good" part of the
I have an 80GB hard disk.
badblocks shows that it has about 78M blocks.
The first 50 million or so can be checked (write patterns)
for many days with no problems.
Beyond that I start to get errors.
Does anyone have any experience with creating a partition
in the "good" part of the disk and just ign
Hi,
I have a problem with a reiserfs partition. Some days ago the drive
reported bad blocks, so I ran the badblocks program tried to fix the
filesystem with the badblocksoutput.
Assuming I fixed the badblock list with 'reiserfsck --badblocks' I tried
to access some (reported broken
to write the data I got lots of errors. So I ran badblocks:
jojda:/home/erik# badblocks -s -v -w -c 64 -o badblocks.out /dev/sda
Checking for bad blocks in read-write mode
From block 0 to 245117376
Testing with pattern 0xaa: done
Reading and comparing: done
Testing with pattern 0x55: done
Reading
I'd appreciate if you would not CC me, as I request in the
X-Followup-To header and the signature of each email.
> It could be a bad controller on the motherboard and
> it sounds like it. You may be damaging hard drives with
> a bad mootherboard.
Right, but using five different machines?
> My
martin f krafft wrote:
> problems), got the machine back into a running state, then ran
> `badblocks -svw` on the disk. And usually, I'd see a number of bad
> blocks, usually in excess of 100.
Modern IDE and SCSI drives fix the bad blocks using
the on chip microprocessor and give
also sprach cr <[EMAIL PROTECTED]> [2003.07.14.1057 +0200]:
> > I've been mad for years, absolutely f**king years, I've been over the
> > edge for yonks. :-)
>
> All Pink Floyd fans are anyway ;)
I beg to differ. We are normal, the rest is mad!
Aside, I believe that my reference to Uncle Fre
On Monday 14 July 2003 10:48, Pigeon wrote:
> I've been mad for years, absolutely f**king years, I've been over the
> edge for yonks. :-)
All Pink Floyd fans are anyway ;)
cr
... comfortably numb...
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? C
t; then ran
> `badblocks -svw` on the disk. And usually, I'd see a number of bad
> blocks, usually in excess of 100.
running badblocks does NOT prove that the disk is bad ...
- i didn't look at the code, but if badblock bypasses the
normal ide interface/system calls,
Alex Malinovich <[EMAIL PROTECTED]> writes:
> Some drives can, in fact do bad sector remapping on the fly.
By some drives, you mean "all drives sold in the last 10 years", right?
> However, manually finding bad blocks on a drive is no real cause for
> concern. When
as frequent
> segmentation faults, corrupt files, and zombie processes. In all
> cases, I replaced the drive, transferred the data (mostly without
> problems), got the machine back into a running state, then ran
> `badblocks -svw` on the disk. And usually, I'd see a number of ba
On Sun, 2003-07-13 at 13:18, martin f krafft wrote:
> What is weird is that S.M.A.R.T. reports no errors on most drives.
> I use the smartmontools, and even long offline tests don't produce
> any error information.
Martin,
Try checking the drives on yet another machine; How old are these
machines
I consequently plugged the drive into another
> test machine and ran badblocks -- and it found more than 2000 -- on
> a drive that had non the day before.
This is definitely a Bad Thing (tm). :) Getting 10 or 100 bad blocks
might not be that big of a concern (though having it happen on t
What is weird is that S.M.A.R.T. reports no errors on most drives.
I use the smartmontools, and even long offline tests don't produce
any error information.
--
Please do not CC me when replying to lists; I read them!
.''`. martin f. krafft <[EMAIL PROTECTED]>
: :' :proud Debian develo
red the data (mostly without
problems), got the machine back into a running state, then ran
`badblocks -svw` on the disk. And usually, I'd see a number of bad
blocks, usually in excess of 100.
The other day, I received a replacement drive from Hitachi, plugged
it into a test machine, ran badblock
The following is _reliably_ reported to the syslog every time I run
"parted /dev/hdg print"
Apr 6 11:44:36 creaky kernel: hdg: read_intr: status=0x59 { DriveReady
SeekComplete DataRequest Error }
Apr 6 11:44:36 creaky kernel: hdg: read_intr: error=0x40 {
UncorrectableError }, LBAsect=16778
J.S.Sahambi said:
> On my machine I have a 40 GB hard disk. I executed badblocks command on
> one (/dev/hda8) of the partitions and it found two bad blocks.
>
> How do I know if these blocks have been used by any file or not?
>
> And how to mark these bad blocks without formattin
On my machine I have a 40 GB hard disk. I executed badblocks command on
one (/dev/hda8) of the partitions and it found two bad blocks.
How do I know if these blocks have been used by any file or not?
And how to mark these bad blocks without formatting the partition so
that they are not used by
Thanks for the replies on how to deal with bad blocks on reiserfs; for the
meantime, I managed to solve my problem (unable to use dpkg as several files
in /var/lib/dpkg/lists were corrupt and unmoveable) by simply renaming the
"lists" folder "lists-BADBLOCKS", creatin
Am Dienstag, 15. Oktober 2002 09:51 schrieb Klaus Imgrund:
> On Tue, 15 Oct 2002 12:49:19 +0800
>
> Crispin Wellington <[EMAIL PROTECTED]> wrote:
> > On Tue, 2002-10-15 at 04:47, Bruce wrote:
> > > I figured this is a hardware/bad block problem. I rebooted
> > > with a rescue disk, and ran reiserf
On Tue, 15 Oct 2002 12:49:19 +0800
Crispin Wellington <[EMAIL PROTECTED]> wrote:
> On Tue, 2002-10-15 at 04:47, Bruce wrote:
> > I figured this is a hardware/bad block problem. I rebooted with a
> > rescue disk, and ran reiserfsck --check /dev/hda2, and received the
> > following error:
> >
> >
ve started deteriorating
quite yet...
B.
On Tuesday 15 October 2002 00:46, Crispin Wellington wrote:
> >
> > Is there a way (yet) to mark bad blocks on a reiserfs filesystem??
>
> No. Reiser does not handle bad-blocks. Ext2/3 does, but that doesn't
> mean anything, because you s
sector=148511 end_request: I/O errore, dev 03:02 (hda), sector 148511
>
> From the above, I gather I have bad blocks on the hard drive. I had a look at
> www.namesys.com/bad-block-handling.html, and the only mention of bad blocks
> includes instructions for how to install reiserfs on a (pre
rore, dev 03:02 (hda), sector 148511
From the above, I gather I have bad blocks on the hard drive. I had a look at
www.namesys.com/bad-block-handling.html, and the only mention of bad blocks
includes instructions for how to install reiserfs on a (presumably blank)
partition with bad blocks; it says n
Apologies for not directly debian-related question on the list,
but I run sid on the problem computer ( hope this is good excuse:-) )
One of my hard drives had developed bad sectors on reiserfs partition
and kernel paniced. Now I cannot mount that partition, because of the
read errors on the driv
on Sun, Apr 15, 2001 at 09:29:07PM +0200, Enrico Zini ([EMAIL PROTECTED]) wrote:
> Hello!
>
> Using badblocks I've found some bad blocks on one of my hard disks, and
> I'd like to mark them bad so that Linux will avoid to use them.
>
> The number of bad blocks I&#
Hello!
Using badblocks I've found some bad blocks on one of my hard disks, and
I'd like to mark them bad so that Linux will avoid to use them.
The number of bad blocks I've found is low, but they are scattered on many
disk partitions: some of them are formatted ext2, some reis
On Thu, 24 Feb 2000 10:51:08 -0800, Alex McCool wrote:
>I've noticed that the sector=591714 (and one other) is always the culprit.
>Can someone tell me how to repair/badblock these sectors?
Back it up, then low-level format it.
BUT BEWARE: Usually bad sector remapping works transparently w/o the
k. However modern harddisks have some part
of their capacity hidden and it is used to map the bad blocks away.
If the beginning of the disk has many bad blocks, then you most propably
are out of luck.
--j
--
Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Many vendors supply low-level format utilities which run under DOS. These
programs are
able to mark the bad blocks at a very low level so you can use the disk. Check
out the
disk manufacturer's website. Alternatively, create a small partition over the
first
couple blocks and start your
Hi,
I got a small used disk given to me that I am trying to put into a
small system I have. When I tried to run mke2fs on any of the partitions I
had created I get
Checking fro bad blocks (read-only test): Bad block 0 out of range;ignored.
done
Block 1 in primary superblock
On Sun, Apr 12, 1998 at 02:55:29PM -0700, George Bonser wrote:
>
> > On Sun, Apr 12, 1998 at 04:09:50PM +0200, Marcus Brinkmann wrote:
> > > I have now some bad blocks on my 2-year-old WD Caviar IDE drive. I'm not
> > > overly concerned, because I have a brand
On Sun, Apr 12, 1998 at 02:55:29PM -0700, George Bonser wrote:
> > On Sun, Apr 12, 1998 at 04:09:50PM +0200, Marcus Brinkmann wrote:
> > > I have now some bad blocks on my 2-year-old WD Caviar IDE drive. I'm not
> > > overly concerned, because I have a brand ne
>>
>> Hi,
>>
>> I have now some bad blocks on my 2-year-old WD Caviar IDE drive. I'm not
>> overly concerned, because I have a brand new SeaGate, on where I install
>> hamm atm, but I wonder if linux can mark bad blacks as 'used', so that it
&
On Mon, Apr 13, 1998 at 12:14:33AM +1000, Hamish Moffatt wrote:
> On Sun, Apr 12, 1998 at 04:09:50PM +0200, Marcus Brinkmann wrote:
> > I have now some bad blocks on my 2-year-old WD Caviar IDE drive. I'm not
> > overly concerned, because I have a brand new SeaGate, on where I
The drive has a three year warranty. Will WD fix the drive or sent me a new
one because of bad blocks? Has anyone has experience with WD warranty?
Should I try to make heavy use of the drive to detect more (soon to be) bad
blocks, as long as I have warranty?
If the drive is actively
On Sun, Apr 12, 1998 at 04:09:50PM +0200, Marcus Brinkmann wrote:
> I have now some bad blocks on my 2-year-old WD Caviar IDE drive. I'm not
> overly concerned, because I have a brand new SeaGate, on where I install
> hamm atm, but I wonder if linux can mark bad blacks as
Hi,
I have now some bad blocks on my 2-year-old WD Caviar IDE drive. I'm not
overly concerned, because I have a brand new SeaGate, on where I install
hamm atm, but I wonder if linux can mark bad blacks as 'used', so that it
doesn't write on them anymore. Or how do you cope
Dear Debian users,
Does anybody know how are handled the bad blocks on an ext2fs partition? Is
there
an automatic handling or must I always use the badblocks command and update the
badblocks list with e2fsck?
--
__
Cedric Bapst
-BEGIN PGP SIGNED MESSAGE-
On 2 Mar 1998, Pedro Quaresma de Almeida wrote:
> I have a hard disk that had gained a couple of bad blocks recently.
>
> Linux (Debian 1.3.1) is having problems dealing with them
>
> "kernel panic ..."
>
> what can I do to ma
Hi
I have a hard disk that had gained a couple of bad blocks recently.
Linux (Debian 1.3.1) is having problems dealing with them
"kernel panic ..."
what can I do to mark the bad block in Linux?
Shoud I go to msdos and format the disk?
will this last option solve my proble
> Also, I've been told not to run disk checks while the HD is mounted,
how
>can I load linux sans mounting the HD? does it work if I boot from a
>floppy?
>
> It shouldn't be a problem to run badblocks while the HD is mounted; it
> does not write to the drive, just
On Thu, Feb 26, 1998 at 08:12:29PM -0500, Ben Pfaff wrote:
> I keep getting {DriveReady SeekComplete DataRequest Error }'s and I
> figure
> it's all bad blocks. I ran "fsck /dev/hda2" but it only seems to do a
>cursory examination (not taking n
eep getting {DriveReady SeekComplete DataRequest Error }'s and I
> figure
> it's all bad blocks. I ran "fsck /dev/hda2" but it only seems to do a
> cursory examination (not taking nearly as long as the scan when I installed
> Linux) and I keep getting the same errors af
I keep getting {DriveReady SeekComplete DataRequest Error }'s and I
figure
it's all bad blocks. I ran "fsck /dev/hda2" but it only seems to do a
cursory examination (not taking nearly as long as the scan when I installed
Linux) and I keep getting t
I keep getting {DriveReady SeekComplete DataRequest Error }'s and I
figure
it's all bad blocks. I ran "fsck /dev/hda2" but it only seems to do a
cursory examination (not taking nearly as long as the scan when I installed
Linux) and I keep getting the same err
You need to create a file containing the block numbers of
the bad blocks. The badblocks program should work. Then
run e2fsck -L on the *un-mounted* filesystem. See the
manpages for badblocks and e2fsck. You may still need to
re-make the filesystem on the affected partition. I would
repeat
On Mon, 20 Oct 1997, Bob Clark wrote:
> You need to create a file containing the block numbers of
> the bad blocks. The badblocks program should work. Then
> run e2fsck -L on the *un-mounted* filesystem. See the
> manpages for badblocks and e2fsck. You may still need to
&
Hi.
I recently posted a message about "Kernel Panic" that was due to bad
blocks in my hard drive. My plan is to just start all over. What I need
now is a way to fix bad blocks or to skip over them if neccessary. I
received a message that told me to use e2fsck -c /dev/hda? ( where ?
>> Hi,
>>
>> I am running Debian 1.1 and am having problems with "bad blocks." I would
>> appreciate any help in solving my problem.
>>
>> This is the error message:
>> Bad Block 1384505 in group 169's inode table. Relocate? Yes.
>&
Hi,
I am running Debian 1.1 and am having problems with "bad blocks." I would
appreciate any help in solving my problem.
This is the error message:
Bad Block 1384505 in group 169's inode table. Relocate? Yes.
WARNING: Severe data loss possible!
Bad Block 1384521 in group 16
"e2fsck -cvf /dev/hda1" didn't fix
the problem. At Bruce's suggestion, I tried running the badblocks
program. It found 48 bad blocks. I then ran "e2fsck -l BadBlocksFile
/dev/hda1" where BadBlocksFile was the output from running badblocks.
Everything appeared to
86 matches
Mail list logo
