[EMAIL PROTECTED] wrote:
Quoting Johannes Wiedersich <[EMAIL PROTECTED]>:
[EMAIL PROTECTED] wrote:
i guess this should be considered a "bad answer" from the system:
# mount /dev/hda9/ /mnt/drive
mount: /dev/hda9 is not a valid block device
hinting towards a very damaged HD!
What does dmesg say about finding any HD?
hda: Maxtor 6E030L0, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
But at the end of dmesg I found this:
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
(fs/jbd/recovery.c, 255): journal_recover: JBD: recovery, exit status 0,
recovered transactions 788311 to 788361
(fs/jbd/recovery.c, 257): journal_recover: JBD: Replayed 228 and
revoked 0/0
blocks
EXT3-fs: recovery complete.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
(fs/jbd/recovery.c, 255): journal_recover: JBD: recovery, exit status 0,
recovered transactions 774678 to 774899
(fs/jbd/recovery.c, 257): journal_recover: JBD: Replayed 2580 and
revoked 0/3
blocks
EXT3-fs: recovery complete.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
(fs/jbd/recovery.c, 255): journal_recover: JBD: recovery, exit status 0,
recovered transactions 1179887 to 1180069
(fs/jbd/recovery.c, 257): journal_recover: JBD: Replayed 518 and
revoked 0/0
blocks
EXT3-fs: recovery complete.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Adding 771080k swap on /dev/hda7. Priority:-1 extents:1
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
(fs/jbd/recovery.c, 255): journal_recover: JBD: recovery, exit status 0,
recovered transactions 124675 to 124717
(fs/jbd/recovery.c, 257): journal_recover: JBD: Replayed 266 and
revoked 4/25
blocks
EXT3-fs: hda8: orphan cleanup on readonly fs
ext3_orphan_cleanup: deleting unreferenced inode 12051
ext3_orphan_cleanup: deleting unreferenced inode 12050
ext3_orphan_cleanup: deleting unreferenced inode 12049
EXT3-fs: hda8: 3 orphan inodes deleted
EXT3-fs: recovery complete.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
(fs/jbd/recovery.c, 255): journal_recover: JBD: recovery, exit status 0,
recovered transactions 934305 to 934375
(fs/jbd/recovery.c, 257): journal_recover: JBD: Replayed 425 and
revoked 2/4
blocks
EXT3-fs: recovery complete.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
My dmesg tells me
hda: SAMSUNG Serial number, type
hda: max request size ...
hda: hda1 hda2 hda3
ie some information about the disk and it's partitions.
If the disk is detected by Knoppix you should also find your
partitions in the /etc/fstab Knoppix created for you.
On this boot with knoppix, the /dev/hda was detected and mounted, but
with
plenty of room.
df
[EMAIL PROTECTED] df hda*
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 2471 17 2454 1% /
/dev/root 2471 17 2454 1% /
/dev/root 2471 17 2454 1% /
/dev/root 2471 17 2454 1% /
/dev/root 2471 17 2454 1% /
so...
/severino
That doesn't look like /dev/hda is mounted; just the ramdisk.
Please give the output of *just* 'df'.
You might also want to run fsck on your hda partitions, and see if that
picks anything up before you try to mount them again.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
