First of all I would suggest you to update to ViX Vs 2.3; after all why struggle to get an old system to work?
Help asked via PM will be ignored.
The forum is there for help and all will benefit from your questions.
NO CARD SHARING TALK WILL BE TOLERATED, LAN OR WAN, IN OPEN FORUM OR PM !
English is not my native tongue.
I apologise for all my grammar, spelling and idiom errors.
also try to run in terminal
Code:fsck UUID=5bb3fb19-f1f9-4833-8c60-87197822746b
D I S C L A I M E R
My right to post information is protected under the rights for freedom act. In all instances, information discussed here on my posts are either hypothetical in nature, out of general curiosity, common knowledge, public knowledge, or role-play. Any use of the collective descriptions and shared knowledge from any of my posts are at the sole discretion of the reader. I am not responsible for what you do with it!
I have upgraded to 2.3... Looks great by the way. Now I need to read up on the OSD options aswell!!! :-)
thought that was a good shout Andy. But it says "fsck.auto: no such file or directory."
Okay looks to me like the MBR is corrupted probably with all the things you have tried.
Now you have to ask youself how much do I want to do to recover whats on the HDD.
You need a dedicated linux machine to fix this.
Last edited by Alias1; 24-12-11 at 21:59.
Posting Permissions
Reply With Quote