I don't get this, I never had this problem before until something corrupted my reiserfs journal, then I had to reformat everything again.
Even though I think I shutdown cleanly (with an init 0 or init 6) apparently it boot it detects both my two reiserfs filesystems (one / and one /home) as "unmounted cleanly" and performs an fsck on them. This doesn't take too much time, apparently since it just goes through the journals and usually it doesn't find any errors, but I am disturbed they are detected as such.
the fstab entries for the two filesystems are
/dev/hda5 / reiserfs defaults 1 1
/dev/hda6 /home reiserfs defaults 1 2
Also it detects DMA as turned off. It was turned off each time it encountered a read error from what I suspect were bad blocks the journal had been written on previously (now all traces of the previous filesystem are probably gone). I can't re-enable it - I thought it was only a setting that was turned off for that kernel session, not a setting that would last for other kernels!
hdparm -d1 -X /dev/hda gives me
bash-3.00# hdparm -d1 -X /dev/hda
setting using_dma to 1 (on)
HDIO_SET_DMA failed: Operation not permitted
setting xfermode to 0 (default PIO mode)
using_dma = 0 (off)
The hard disk is really slow - 3 MB per second(!)
I might as well ask it here - I am slightly perturbed, though it's not an issue currently. The last time I passed the "no journal" option to reiserfsck, but it detected a journal, found it couldn't read it and bailed out. But I wanted it to ignore the journal because it was corrupt - and fix the other parts of the filesystem manually, perhaps even wipe out the journal and create a new one. Is this the fault of the program, or can the filesystem not be checked if the journal is corrupt?