here is the result of dmesg | grep hd
Kernel command line: ro root=LABEL=/ hdb=ide-scsi
ide_setup: hdb=ide-scsi
ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda

MA, hdb

MA
ide1: BM-DMA at 0x9800-0x9807, BIOS settings: hdc

io, hdd

io
ide2: BM-DMA at 0x9808-0x980f, BIOS settings: hde

io, hdf

io
hda: WDC AC310200R, ATA DISK drive
hdb: SONY CD-RW CRX140E, ATAPI CD/DVD-ROM drive
hdc: ST380021A, ATA DISK drive
hda: attached ide-disk driver.
hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_no_data_intr: error=0x04 { DriveStatusError }
hda: host protected area => 1
hda: 20044080 sectors (10263 MB) w/512KiB Cache, CHS=1247/255/63, UDMA(33)
hdc: attached ide-disk driver.
hdc: host protected area => 1
hdc: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=155061/16/63, UDMA(100)
hda: [EZD] [remap 0->1] [1247/255/63] hda1 hda2 hda3
hdc: hdc1
hdb: attached ide-scsi driver.
The system was working fine - until one day when I returned from work, rebooted (I *think* there was a power outage) and boom! No Xwindows, and hard drive had lost+found in it...
It occurs to me that the system may not have been able to "find" the drive and somehow pointed lost+found to the mapping (ie /media now points to /lost+found) Does that make sense to anyone or otherwise ring a bell?
also - Michael
I didn't notice if the system did a file check - if it did - then it did so quickly and I didn't notice.
I repartitioned hdc1, the drive that contained only data and was mapped to /media
gary