Re: bad hard drive?

2001-03-19 Thread Marc-Adrian Napoli
hi,

> Bad hard drive.

badblocks shows nothing, and i have another of these 40 gig drives on a
different machine that does the exact some thing.

kaos:/# fsck /backup
Parallelizing fsck version 1.18 (11-Nov-1999)
e2fsck 1.18, 11-Nov-1999 for EXT2 FS 0.5b, 95/08/09
/dev/hdc1 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Padding at end of block bitmap is not set. Fix? yes


/dev/hdc1: * FILE SYSTEM WAS MODIFIED *
/dev/hdc1: 11/5003712 files (0.0% non-contiguous), 157031/10006479 blocks

kaos:/# fsck /backup
Parallelizing fsck version 1.18 (11-Nov-1999)
e2fsck 1.18, 11-Nov-1999 for EXT2 FS 0.5b, 95/08/09
/dev/hdc1: clean, 11/5003712 files, 157031/10006479 blocks

kaos:/# mount -o rw /backup
kaos:/# cd /backup
kaos:/backup# touch aoeu
touch: aoeu: Read-only file system
kaos:/backup# cd ..
kaos:/# umount /backup

kaos:/# fsck /backup
Parallelizing fsck version 1.18 (11-Nov-1999)
e2fsck 1.18, 11-Nov-1999 for EXT2 FS 0.5b, 95/08/09
/dev/hdc1 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes

and it goes on with the same error!

someone mentioned about these drives using ATA66? would that have any effect
here?

Regards,

Marc-Adrian Napoli
Network Administrator
Connect infobahn Australia
+61 2 92120387
>
> On Tue, Mar 20, 2001 at 11:12:14AM +1100, Marc-Adrian Napoli wrote:
> >
> > when copying files over to this drive, i always get errors. by that i
mean i
> > run fsck on the drive and there are errors. as soon as the fsck is
finished
> > i run it again and there are errors again. its now to the point where i
cant
> > even mount the drive read/write because there are so many errors!
> >
> > is the drive simply too big? am i getting these errors because bios
didnt
> > detect them?
>
> 
> Corwin J. Grey
> Techline, Inc.
> http://www.techline.com
> Engineering and Application Development
> 
> "What does this tell me?  That if Microsoft were the last software
> company left in the world, 13% of the US population would be scouring
> garage sales & Goodwill for old TRS-80s, CPM machines & Apple ]['s before
> they would buy Microsoft. That's not exactly a ringing endorsement."
> -- Seen on Slashdot
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact
[EMAIL PROTECTED]
>
>



Re: bad hard drive?

2001-03-19 Thread Corwin Grey

Bad hard drive.

On Tue, Mar 20, 2001 at 11:12:14AM +1100, Marc-Adrian Napoli wrote:
> 
> when copying files over to this drive, i always get errors. by that i mean i
> run fsck on the drive and there are errors. as soon as the fsck is finished
> i run it again and there are errors again. its now to the point where i cant
> even mount the drive read/write because there are so many errors!
> 
> is the drive simply too big? am i getting these errors because bios didnt
> detect them?


Corwin J. Grey
Techline, Inc.
http://www.techline.com
Engineering and Application Development

"What does this tell me?  That if Microsoft were the last software
company left in the world, 13% of the US population would be scouring
garage sales & Goodwill for old TRS-80s, CPM machines & Apple ]['s before
they would buy Microsoft. That's not exactly a ringing endorsement."
-- Seen on Slashdot



bad hard drive?

2001-03-19 Thread Marc-Adrian Napoli
hi all,

i have a 40gig IDE drive on a dual800 system running debian 2.2. bios did
not detect this drive correctly.

however, an fdisk on the /dev/hdb could see the drive, and i made a
partition /dev/hdb1 which was all 40 gig ext2.

when copying files over to this drive, i always get errors. by that i mean i
run fsck on the drive and there are errors. as soon as the fsck is finished
i run it again and there are errors again. its now to the point where i cant
even mount the drive read/write because there are so many errors!

is the drive simply too big? am i getting these errors because bios didnt
detect them?

Regards,

Marc-Adrian Napoli
Network Administrator
Connect infobahn Australia
+61 2 92120387