crash 2226
the following words to the mbuttes incomp.os.linux.misc...:
Whatever the cause of the system freezes was, they may be unrelated to the problem you have now, i.e. a failure to boot. The latter could simply be caused by filesystem damage due to an unclean shutdown...
If the filesystem is damaged, then you would indeed get such problems...
I see the following directories: dev bin etc modules scripts usr proc var root conf lib sbin init...
That is weird, because *-root* should normally live in the root filesystem, and then you should also see directories such as *-bin* and *-sbin* et al.
The fact that you find yourself in a shell environment shows that *-sbin-init* exists, and at the very least *-bin-bash* or an equivalent shell.
The output of...
Thanks for the tip, I put the drive back into the USB enclosure and connected to my Ubuntu notebook through the USB...
mount
... in this environment should tell you what is mounted and where.
It is not unthinkable that if your parbreastion got damaged all of your data will be lost. This is one of the reasons why you should make backups, and one of the reasons why I advise people to use a separate parbreastion for *-home* at the very least.
Note: None of the above explains why your system hung in the first place, but there are various possible causes for this. On account of software, it can be due to a proprietary video driver - those are often the cause for trouble.
On account of hardware, your machine could be overheating - dust in the fans, etc. - or there could be something wrong with your hard disk. However, given the current status of your filesystem(s), it's hard to say something about the hard disk itself at this stage.
Try to be as precise as possible regarding error messages, mounted filesystems, directory contents, et al. The better your information, the more focused our advice can be.
Hope this was useful... ;-)
-- With kind regards,
*Aragorn* (Registered GNU-Linux user #223157)