Tejun Heo wrote:
Bill Davidsen wrote:
Jan Engelhardt wrote:
On Dec 1 2007 06:26, Justin Piszcz wrote:
I ran the following:
dd if=/dev/zero of=/dev/sdc
dd if=/dev/zero of=/dev/sdd
dd if=/dev/zero of=/dev/sde
(as it is always a very good idea to do this with any new disk)
Justin Piszcz wrote:
> The badblocks did not do anything; however, when I built a software raid
> 5 and the performed a dd:
>
> /usr/bin/time dd if=/dev/zero of=fill_disk bs=1M
>
> [42332.936615] ata5.00: exception Emask 0x2 SAct 0x7000 SErr 0x0 action
> 0x2 frozen
> [42332.936706] ata5.00: spuri
Bill Davidsen wrote:
> Jan Engelhardt wrote:
>> On Dec 1 2007 06:26, Justin Piszcz wrote:
>>> I ran the following:
>>>
>>> dd if=/dev/zero of=/dev/sdc
>>> dd if=/dev/zero of=/dev/sdd
>>> dd if=/dev/zero of=/dev/sde
>>>
>>> (as it is always a very good idea to do this with any new disk)
>>
>> Why wo
On Thu, 6 Dec 2007 17:38:08 -0500 (EST)
Justin Piszcz <[EMAIL PROTECTED]> wrote:
>
>
> On Thu, 6 Dec 2007, Andrew Morton wrote:
>
> > On Sat, 1 Dec 2007 06:26:08 -0500 (EST)
> > Justin Piszcz <[EMAIL PROTECTED]> wrote:
> >
> >> I am putting a new machine together and I have dual raptor raid 1 f
On Thu, 6 Dec 2007, Andrew Morton wrote:
On Sat, 1 Dec 2007 06:26:08 -0500 (EST)
Justin Piszcz <[EMAIL PROTECTED]> wrote:
I am putting a new machine together and I have dual raptor raid 1 for the
root, which works just fine under all stress tests.
Then I have the WD 750 GiB drive (not RE2,
On Sat, 1 Dec 2007 06:26:08 -0500 (EST)
Justin Piszcz <[EMAIL PROTECTED]> wrote:
> I am putting a new machine together and I have dual raptor raid 1 for the
> root, which works just fine under all stress tests.
>
> Then I have the WD 750 GiB drive (not RE2, desktop ones for ~150-160 on
> sale n
Justin Piszcz wrote:
The badblocks did not do anything; however, when I built a software raid
5 and the performed a dd:
/usr/bin/time dd if=/dev/zero of=fill_disk bs=1M
I saw this somewhere along the way:
[30189.967531] RAID5 conf printout:
[30189.967576] --- rd:3 wd:3
[30189.967617] disk 0
On Sat, 1 Dec 2007, Justin Piszcz wrote:
On Sat, 1 Dec 2007, Janek Kozicki wrote:
Justin Piszcz said: (by the date of Sat, 1 Dec 2007 07:23:41 -0500
(EST))
dd if=/dev/zero of=/dev/sdc
The purpose is with any new disk its good to write to all the blocks and
let the drive to all of
Justin Piszcz wrote:
I am putting a new machine together and I have dual raptor raid 1 for
the root, which works just fine under all stress tests.
Then I have the WD 750 GiB drive (not RE2, desktop ones for ~150-160 on
sale now adays):
I ran the following:
dd if=/dev/zero of=/dev/sdc
dd if=
Jan Engelhardt wrote:
On Dec 1 2007 06:26, Justin Piszcz wrote:
I ran the following:
dd if=/dev/zero of=/dev/sdc
dd if=/dev/zero of=/dev/sdd
dd if=/dev/zero of=/dev/sde
(as it is always a very good idea to do this with any new disk)
Why would you care about what's on the disk? fdisk, mkfs an
On Sat, 1 Dec 2007, Jan Engelhardt wrote:
On Dec 1 2007 06:26, Justin Piszcz wrote:
I ran the following:
dd if=/dev/zero of=/dev/sdc
dd if=/dev/zero of=/dev/sdd
dd if=/dev/zero of=/dev/sde
(as it is always a very good idea to do this with any new disk)
Why would you care about what's on
On Dec 1 2007 06:26, Justin Piszcz wrote:
> I ran the following:
>
> dd if=/dev/zero of=/dev/sdc
> dd if=/dev/zero of=/dev/sdd
> dd if=/dev/zero of=/dev/sde
>
> (as it is always a very good idea to do this with any new disk)
Why would you care about what's on the disk? fdisk, mkfs and
the day-to-
12 matches
Mail list logo
