Quote:
Originally Posted by blue68f100
256meg may be a little low. Installer scripts errors at times will just trigger another step to create what is missing.
|
It takes 184 pin PC2100 right? I should be able to find plenty of that lying around.
Quote:
|
I see this quite often. You also get these errors when the HD/share is full. This problem was corrected in v4 when they expanded the partitions. Did you test to see if it's still failing to boot.
|
Yep I tried a couple of times and it's still booting to the recovery console.
How does the installer fix corrupted disks? It just seemed to start installing without running any disk checks or fixups.
Quote:
|
Were you running the AV, was optional package for the 4200? So this may not even apply. If AV this may need to be un installed to free up some HD space. There is an uninstaller script that can be run from the cmd line, but you may not be booting far enough to execute.
|
Not sure what AV is, so probably not
There is heaps of free space - it was quite underutilised.
Quote:
|
Have you installed or added any software to the OS's for special functions?
|
nope
Quote:
|
Have you tried running SpinRite to check the remaining drives?
|
no, but correct me if I'm wrong, wouldn't SpinRite have to understand the partition first before it started re-writing data to another block? Since the OS is Linux based and the partitions are RAIDed together, how can SpinRite understand them?
Quote:
|
There were some issues like this several years ago, but I do not recall what was done.
|
I'll do some searching.
Does SNAP provide a ssh log-in or something? If I could just log in and run some tools (which I can do from a Linux boot disk) then I'm sure I could get it going...
thanks for the help!