Uh-oh... fsck can't repair my files-partition!
Hello, after a total systemfreeze - probably due to a new installed kernel - i had to do a few resets. That bashed a few partiotions, among them the /files, which is my largest and most valuable with around 30 GB. All could be cleaned except of files, here is the output: -- # fsck /files ** /dev/ad0s2e (NO WRITE) ** Last Mounted on /files ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups FREE BLK COUNT(S) WRONG IN SUPERBLK SALVAGE? no SUMMARY INFORMATION BAD SALVAGE? no BLK(S) MISSING IN BIT MAPS SALVAGE? no 5499 files, 23301161 used, 4289037 free (1517 frags, 535940 blocks, 0.0% fragmentation) -- What am i gonna do now? =( BTW: i can mount and access the fs, but fear not everything survived. OS is 5.0-CURRENT. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Uh-oh... fsck can't repair my files-partition!
[EMAIL PROTECTED] wrote on 10/22/2002 12:58:49 PM: Hello, after a total systemfreeze - probably due to a new installed kernel - i had to do a few resets. That bashed a few partiotions, among them the /files, which is my largest and most valuable with around 30 GB. All could be cleaned except of files, here is the output: -- # fsck /files ** /dev/ad0s2e (NO WRITE) ** Last Mounted on /files ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups FREE BLK COUNT(S) WRONG IN SUPERBLK SALVAGE? no SUMMARY INFORMATION BAD SALVAGE? no BLK(S) MISSING IN BIT MAPS SALVAGE? no Howabout answering these questions with 'yes' instead of 'no'? That always works for me. In fact, I have a hard drive on it's last legs, the other day it apparently crashed, I hard-reset the computer, ran fsck -y on that disk and finally after running this about 8 times it finally was marked clean. -- Chip 5499 files, 23301161 used, 4289037 free (1517 frags, 535940 blocks, 0.0% fragmentation) -- What am i gonna do now? =( BTW: i can mount and access the fs, but fear not everything survived. OS is 5.0-CURRENT. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Uh-oh... fsck can't repair my files-partition!
Howabout answering these questions with 'yes' instead of 'no'? That always works for me. In fact, I have a hard drive on it's last legs, the other day it apparently crashed, I hard-reset the computer, ran fsck -y on that disk and finally after running this about 8 times it finally was marked clean. LOL There is no prompt to type y or n, and it is the same with fsck -y. Sorry for not mentioning this. Meanwhile i got the tip to try... fsck -y /dev/ad0s2 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Uh-oh... fsck can't repair my files-partition!
LOL There is no prompt to type y or n, and it is the same with fsck -y. Sorry for not mentioning this. Meanwhile i got the tip to try... Dismount the volume before running fsck. The (NO WRITE) message means that the filesystem was in use or otherwise read-only. YES :D Thank you guys, that's been the reason - needed to umount first. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
