Taavi Tänavsuu wrote:
Hi,
Got a brand new Samsung 250 GB IDE harddisk, added it to my home PC
running
FreeBSD 5.3, created FreeBSD filesystem there. I have been using it for
several months, keeping relatively large (5-10 GB) home video files
there,
and it has been working fine.
But now suddenly got the following problem:
================
pepe# mount /dev/ad3s1d /mnt/suur_ketas/
mount: /dev/ad3s1d: Input/output error
pepe# mount /dev/ad3s1d /mnt/suur_ketas/
mount: /dev/ad3s1d: Input/output error
pepe# fsck -f /dev/ad3s1d
** /dev/ad3s1d
** Last Mounted on /mnt/suur_ketas
** Phase 1 - Check Blocks and Sizes
CANNOT READ BLK: 51184064
UNEXPECTED SOFT UPDATE INCONSISTENCY
CONTINUE? [yn] y
THE FOLLOWING DISK SECTORS COULD NOT BE READ: 51184077, 51184080,
PARTIALLY TRUNCATED INODE I=4498435
SALVAGE? [yn] y
INCORRECT BLOCK COUNT I=4498438 (673600 should be 667584)
CORRECT? [yn] y
INCORRECT BLOCK COUNT I=4498439 (467936 should be 459392)
CORRECT? [yn] y
INCORRECT BLOCK COUNT I=19595269 (838304 should be 829248)
CORRECT? [yn] y
PARTIALLY TRUNCATED INODE I=20843652
SALVAGE? [yn] y
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
CANNOT READ BLK: 51184064
UNEXPECTED SOFT UPDATE INCONSISTENCY
CONTINUE? [yn] y
THE FOLLOWING DISK SECTORS COULD NOT BE READ: 51184077, 51184080,
FREE BLK COUNT(S) WRONG IN SUPERBLK
SALVAGE? [yn] y
SUMMARY INFORMATION BAD
SALVAGE? [yn] y
BLK(S) MISSING IN BIT MAPS
SALVAGE? [yn] y
160 files, 53062183 used, 65193686 free (78 frags, 8149201 blocks,
0.0%fragmentation)
***** FILE SYSTEM STILL DIRTY *****
***** FILE SYSTEM WAS MODIFIED *****
***** PLEASE RERUN FSCK *****
pepe# fsck -f -y /dev/ad3s1d
** /dev/ad3s1d
** Last Mounted on /mnt/suur_ketas
** Phase 1 - Check Blocks and Sizes
CANNOT READ BLK: 51184064
UNEXPECTED SOFT UPDATE INCONSISTENCY
CONTINUE? yes
THE FOLLOWING DISK SECTORS COULD NOT BE READ: 51184077, 51184080,
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
CANNOT READ BLK: 51184064
UNEXPECTED SOFT UPDATE INCONSISTENCY
CONTINUE? yes
THE FOLLOWING DISK SECTORS COULD NOT BE READ: 51184077, 51184080,
160 files, 53062183 used, 65193686 free (78 frags, 8149201 blocks,
0.0%fragmentation)
***** FILE SYSTEM STILL DIRTY *****
***** PLEASE RERUN FSCK *****
pepe# fsck -f -y /dev/ad3s1d
** /dev/ad3s1d
** Last Mounted on /mnt/suur_ketas
** Phase 1 - Check Blocks and Sizes
CANNOT READ BLK: 51184064
UNEXPECTED SOFT UPDATE INCONSISTENCY
CONTINUE? yes
THE FOLLOWING DISK SECTORS COULD NOT BE READ: 51184077, 51184080,
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
CANNOT READ BLK: 51184064
UNEXPECTED SOFT UPDATE INCONSISTENCY
CONTINUE? yes
THE FOLLOWING DISK SECTORS COULD NOT BE READ: 51184077, 51184080,
160 files, 53062183 used, 65193686 free (78 frags, 8149201 blocks,
0.0%fragmentation)
***** FILE SYSTEM STILL DIRTY *****
***** PLEASE RERUN FSCK *****
pepe# mount /dev/ad3s1d /mnt/suur_ketas/
mount: /dev/ad3s1d: Input/output error
pepe# mount /dev/ad3s1d /mnt/suur_ketas/
mount: /dev/ad3s1d: Input/output error
================
I'm not yet very familiar with harddisks, filesystems, and FreeBSD,
but is
there anything else i could try to make the disk usable again, or is it
somehow physically damaged?
-taavi "k6ps" tänavsuu
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
"[EMAIL PROTECTED]"
.
Taavi,
I'm not an expert but the smartmontools port may help, I am installing
it now to keep me informed of hdd status. I can remember reading in the
documentation about repairing drives.
http://smartmontools.sourceforge.net/
http://www.linuxjournal.com/article/6983
I hope this helps in some way,
Ivan
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"