(This will take time -- perhaps more than a week. But the problem has already gone on that long, and 2TB drives are costly.)

I think i will give it try(i just started the test).Bad news is Ubuntu is on a laptop.But i think i won't be a problem even for my laptop to work with it for a week or more.

But there are even worse news.Today i had a pc freeze on my desktop with openbsd,shut it down with the power button and could not open it.This time i ran fsck(and said i have bad sectors.)It also said to run fsck_ffs but when i do it's duration is small-the time to just press a button-and nothing changes.I think that all my disks right now follow Murphy's Law: "If anything can go wrong, it will".

You've reported doing this multiple times. Are you aware that OpenSSH in included with OpenBSD? You can control your OpenBSD system from another, even from the Internet. You could # pkill Xorg or # halt or ... perhaps look through logs to see what is happening, while it is happening. This isn't Windows, mashing a power button is not always necessary.

See the ssh(1) and sshd(8) man pages, if you've never used them before.

Quote:

It also said to run fsck_ffs but when i do it's duration is small-the time to just press a button-and nothing changes.

That is not helpful towards a diagnosis. A log of the specific fsck_ffs command string and the output returned will be required for any further assistance with this particular problem. It appears you've never seen this; it would be helpful if you would take a look at it, particularly section b.

Quote:

I think that all my disks right now follow Murphy's Law: "If anything can go wrong, it will".

While that is possible, it's certainly not yet clear to me that this is the case.

Are you aware that OpenSSH in included with OpenBSD? You can control your OpenBSD system from another, even from the Internet. You could # pkill Xorg or # halt or ... perhaps look through logs to see what is happening, while it is happening. This isn't Windows, mashing a power button is not always necessary.

See the ssh(1) and sshd(8) man pages, if you've never used them before.

Nope,had no idea i could use this kind of tools.I thought ssh was for sending/reading mails in a secure way.I'll read the man pages for now and see what i can do.

Quote:

Originally Posted by jggimi

It appears you've never seen this; it would be helpful if you would take a look at it, particularly section b.

OK got it,i'll try to be more analytic from now on.

Quote:

Originally Posted by jggimi

While that is possible, it's certainly not yet clear to me that this is the case.

Hope it's not.I'm so happy i managed to make my OBSD to work,with lots of help from the forum of course-,and sad on the other hand that had to face so many issues the last days.Problems i had no idea the existed.

But in my country we say ; "every obstacle is for good" so i hope when this ends i'll be wiser.

The badblocks test has finally ended;it took 3-4 days( i had to stop it once cause i needed to take the laptop with me) and started it over.

The output of badblocks -w is

Code:

badblocks: Unknown code ext2 adding to in-memory bad block list

and above that it has numbers from 857210853 to 857211362.

I can remember that before ending i could see even smaller numbers to the terminal(around 7******** don't remember exactly :/ ) that now cannot be shown to the terminal and cannot copy paste the onces i can see right now.

The script(1) tool is a wonderful aid to logging what you are doing; I mentioned it to you in one of your other threads the other day. But you have reproduced for us key information from badblocks, and from SMART. And this time, you managed to reproduce for us a complete report from smartctl. Thank you.

It looks to me like the badblocks program was unable to "clear" up bad sectors for you (by having the drive select from spare sectors) when it wrote patterns.

You still have 18 "Pending" sectors, and 16 "Offline uncorrectable" sectors. The latter came during the one-and-only long offline test ever performed on the drive. That test never completed, it was stopped after only 10% of the sectors were inspected.

This failure to clear sectors indicates to me that the drive has no spare sectors remaining. If it were my drive, I would no longer trust it.

If you want a picture of how many bad sectors are actually on that drive, run a long offline test. This will read every sector on the drive. It will take longer than the 255 minutes described in the smartctl report; that is the time it would take if all sectors were working. Retrying bad sectors will extend that time, as the drive will retry and retry and retry each bad sector.

Once the test completes, you can compare your 16 offline uncorrectable sectors now with the number in a new report.

And this time, you managed to reproduce for us a complete report from smartctl. Thank you.

If someone should be thanking here it's me not you; Your volunteerism exceeds human imagination.We,noobs are sure tiring some-if not all- times.Once again thank you very much.

Quote:

Originally Posted by jggimi

This failure to clear sectors indicates to me that the drive has no spare sectors remaining. If it were my drive, I would no longer trust it.

And since you wouldn't i won't either.It's too bad 'cause i bought it some months ago and on the other hand i have a western digital external disk for about 4 years and so far it works great.And i'm kinda more unlucky 'cause by changing the case i lost gurantee but it's ok; i've learned a lot of things this days and some useful tools too.Thank you again for all the help jggimi.

Since badblocks had some trouble -- with a 510-sector area (that ended at at sector 857211362) and some other sector sets whose sector numbers you did not capture, I would *still* run a test of the drive electronics (short offline) and of the media (long offline). It is possible that the drive is functioning, but the USB electronics (or your cable) are causing trouble.

If both tests complete without error, you can then consider the enclosure electronics and USB cable to be "suspect." At that point I would swap the drive in the enclosure with a known-good drive, and put the 2TB drive into an internal bay in a desktop or server for additional testing.