VFS: unable to mount root fs on unknown block...

[thealphabeta]

I took the drive out and backed it up using UFS explorer on the Mac, so all my data is now on an external drive. So, yes I can still access it externally and appear to be able to read-write to it just fine.

I don't have the original disc I used although it was V2.0 I originally installed with and that was December 11

[durks]

I took the drive out and backed it up using UFS explorer on the Mac, so all my data is now on an external drive. So, yes I can still access it externally and appear to be able to read-write to it just fine.

Ok. If I had known that, I probably wouldn't have suggested that the hard disc might have been causing the problem. That's the kind of detail I meant when I asked for a detailed timeline: the more information and detail you provide, the better.

I don't have the original disc I used although it was V2.0 I originally installed with and that was December 11

That would have been the initial 2.0 release then, I think. My explicit suggestion then is to get hold of a copy of that, try to reinstall it, and see what happens. Somebody on this Forum should have an ISO archive - I hope.

[thealphabeta]

I did - on the first page of this thread...'Yes I have it all backed up. I used UFS to get it all off successfully. So yeah it's all trashable.'

Ok, I'll start another thread to see if I can get hold of a copy. Failing that I might just buy another HD and use this one in an external enclosure for my backup drive

[thealphabeta]

I have just taken the drive back out to be explored on my macbook pro. I have reformatted it and run disk warrior on it. Works fine. I can move files to it and run them etc without issue.

Seems odd that a clean install on a freshly formatted disc can cause this number of issues

[durks]

I have just taken the drive back out to be explored on my macbook pro. I have reformatted it and run disk warrior on it. Works fine.

Ok - the drive per se doesn't seem to be the problem. So let's assume it's working.

Seems odd that a clean install on a freshly formatted disc can cause this number of issues

I don't think that's the sequence you've mentioned before though? I *thought* you said what had happened was the VBox just wouldn't reboot, so then you tried to reinstall it to try to fix the problem - and, since then, nothing has worked. Can you clarify all of this? Thanks. What'd be really helpful would be if you could carefully and completely summarize the entire sequence of events - including error messages, and screenshots if at all possible.

In any case: you have a problem, so let's try to fix it.

Can you also clarify whether or not this concerns a VortexBox appliance which you bought (in which case the answer is to contact the supplier); or whether it's a stock PC which you bought/built, and then installed yourself using a VortexBox CD (in which case: does the box have any unusual hardware?)

Since you have the hard disc available for reading, can you also post the contents of /boot/grub2/grub.cfg so that we can see whether or not they look sane.