Ubuntu has corrupted my file !

[Tchize]

Here it is, the last song of dying hard disk!

If you want details, install the package smartmontools and run
 sudo smartctl -a /dev/hd?

This will print S.M.A.R.T informations about the device. To run a
complete ssmart test on hdd, issue
sudo smartctl -t long /dev/hd? followed by a sudo smartctl -l self-test
/dev/hd? when test is finished

The interest of smart tools is that they can detect hardware failure
before the endup in badblocks. But that supposes you read the smart
reports :)



sebastien a écrit :
> Hi all ! Thanks for all info !
>
> This file was located on a FAT32 partition.
>
> badblocks /dev/ gives the foolowing output :
> 75302080
> 75302084
> 75302085
> 75302086
> 75302087
> 75302088
> 75302089
> 75302090
> 75302091
> 75302092
> 75302093
> 75302094
> 75302095
> 75302096
> 75302097
> 75302098
> 75302099
> 75302100
> 75302101
> 75302102
> 75302103
> 75302104
> 75302105
> 75302106
> 75302107
> 75302108
> 75302109
> 75302110
> 75302111
>
> Why not reformat the partitioninto ext3 but Ive got 80Gb of data !
> ARGH ! !
>
>
> On Tue, 14 Nov 2006
> 14:04:40 +0100 Mario Vukelic <mario.vukelic at dantian.org> wrote:
>
>   
>> On Tue, 2006-11-14 at 22:57 +1100, James Gray wrote:
>>     
>>> AFAIK only non-journalling file systems impose this mandatory fsck  
>>> after a certain number of reboots etc. 
>>>       
>> Not true, ext3 does this (and it is very annoying)
>>
>>     
>>>  Why not use (at least) ext3  
>>> or reiserfs/jfs/xfs???
>>>       
>> He probably uses ext3 since this is the default in Ubuntu. And by the
>> way, reiserfs is _known_ to have corrupted files
>>
>>
>>     
>>> Stop using an ancient file system - backup your data (completely),  
>>> and reformat with filesystem that supports journalling. 
>>>       
>> See above
>>
>>
>>     
>
>