Tags:
Error Booting SCo Unix System V/386 on i80489
i am using an old PC Intel 486 with 100 Mb HDD.When i start booting it, i got a message fsstat : Root file system needs checking. OK to check the root file system (/dev/root)? (y/n) : i used Y to check then it shows ** phase 1 - Check Blocks and Sizes and display 4 messgaes like Possible file size error I=138 too few blocks allocated Possible file size error I=140 too few blocks allocated Possible file size error I=141 too few blocks allocated Possible file size error I=142 too few blocks allocated Possible file size error I=143 too few blocks allocated Possible file size error I=144 too few blocks allocated then phase 2 check pathnames phase 3 check connectivity phase 4 check Reference counts unref file I=130 owner=root mode=10000 size=0 mtime=jan 08 20:18:48 1970 cleared unref file I=131 owner=root mode=10000 size=0 mtime=jan 08 20:18:48 1970 cleared unref file I=132 owner=root mode=10000 size=0 mtime=jan 08 20:18:48 1970 cleared
Phase 5 check free list bitmap (ignored) phase 6 salvage free list bitmap
then it asked me to set file system state to kkay : i pressed Y then it says 9909 files 972462 blocks 47508 free
ROOT FILE SYSTEM WAS MODIFIED ROOT REMOUNTED
AFTER THE LAST MESSAGE IT HANGUP, YESTERDAY I LEFT IT ON THE SAME MESSAGE FOR WHOLE THE NIGHT AND TODAY MORNING I FOUND IT ON THE SAME STAGE.
PLSELP ME THAT HOW CAN I BOOT MY SYSTEM NORMALLY AS I AM TOO NEW FOR UNIX.
I was a SCO engineer in a past life, so let see how we go..
Normally, the check file system does work, I'd suspect you have a bad sector somewhere, how old is the hard drive? Got enough free space? Do you do backup regularly? as the only way I knew to defrag was to do a full backup and a full restore...
Dear Mr. Debuggerau Thanks for quick response, my HDD is too old, acutully we used it before switching to Windows. It was stopped using in the year 2004 but it was turned on, but last year Oct we switched it off and kept in store.
sorry to say this, but it may have to be returned there... Whats the reason for getting it going, restore data or what? I may be able to help tomorrow when I return.
It sounds like the OS itself lost some files (/etc/init ...) and has no idea what to do after the fsck finishes, the i-node numbers are rather low.
Most likely you would need a different boot media, preferably a boot floppy created with that system so it knows about the hardware. You might be able to use a boot cd, even from a newer version though.
If you could get that to boot and get to a shell, then you could try to get the HD to mount:
mount /dev/hd0root /mnt
I'll stop here. Let me know if you can even get that far. If you can then we might be able to fix up the OS.
