Once upon a time I had my wonderful Stuff: partition...
then, while donkeying a bit, I read a checksum error message on block 555 (strange it wasn't 666...).
I copied all the important files on my linux /home and formatted the partition, fist with quick, than normal and at last with verify. The result is that the error is still there, but on block 5155.

Is there anything I can do not to lowlevel format the drive?
I thought about deleting Stuff: from SCSIConfig and re-creating it, but I first need to backup everything as I'm not so sure the other volumes will survive...

Any help?

Quote:
Sounds like your HD might have some bad sectors, especially if the block is always the same. It's not uncommon that when you first get such errors, you'll get more after a while. If the HD is breaking up, it might be safe to replace it with a new one.

Quote:
Whatever you do, do NOT low level format your drive! It's not meant to be done for IDE HD's.

I put on dvd all the *really* important stuff, deleted dh2: and made it again with scsiconfig. nothing changed (error still on 5155) but now linux goes in kernel panic while booting... guess that backup was the right thing

Quote:

Is it possible to overcome this problem somehow? AFAIK there is no SFSSalv (yet?)...

###SFSCheck Output (since I can't see the attached file in the first post###

Partition start offset : 0x00000000:2316E600 End offset : 0x00000002:944B0A00
Surfaces : 1 Blocks/Track : 4771
Bytes/Block : 512 Sectors/Block : 1
Total blocks : 20486674 Size : 10003,2MB/9973,4MB (1%)
Device interface : TD64 Version : 1.210
Device buffers : 600 Device caches : 32x16384 (524288 bytes) [CPB]

Checking RootBlocks
...okay
Checking Config Block at block 20486672
Reserved areas in config block weren't all set to zero.
...damaged
Checking AdminSpaceContainers at block 2
...okay
Checking NodeContainers at block 7
...okay
Checking ObjectContainers at block 3
...okay
Checking Bitmap at block 34 (5122 blocks, 4000 bits/bitmap)
0 FFFF8000 == FFFF0000
Bitmap block 5155 contents is incorrect!
...error in bitmap block at block 5155.
...damaged

If the error is only reported by SFSCheck tool then it is not an error, but a "feature" of MorphOS 1.4.4+. SFSCheck is a bit outdated and doesn't handle correctly new version of SFS. Use 'defrag' tool from MOS1.4.4+ to check the partition integrity.

[ Edited by March on 2005/10/13 13:53 ]

Quote:

mmh... actually the first time I got the error (on block 555) it was both detected by sfscheck AND sfs, since mldonkey couldn't write the temp file and a sys requester appeared.
Anyway, defrag runs smoothly...
Did I buy a new 80Gb maxtor for nothing?

PS: if it's just sfscheck, how to explain the non-booting linux partition?

Quote:

There might be various reasons. What is exactly the problem?

ehm... just a stupid thing
Quite unsurprisingly, deleting dh2 and recreating it changed the physical name of the partitions.
the kernel was loking for init/ in /dev/hda4 that now is the former /dev/hda5 (home).
Guess changing root= option to /dev/hda3 will solve the problem: I checked and the partition is still there...