Install hangup....

[Joseph]

Karl Larsen wrote:
> Joseph wrote:
>> Karl Larsen wrote:
>>   
>>> Joseph wrote:
>>>     
>>>> David Vincent wrote:
>>>>   
>>>>       
>>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>>> Hash: SHA1
>>>>>
>>>>> Joseph wrote:
>>>>>     
>>>>>         
>>>>>> I haven't gotten assistance yet for this problem, and by 
>>>>>>           
>>>> After I sent this, I'd gone for a walk.  When I came back about a half hour later, it had indeed 
>>>> installed.  However, I'm back at the error point where I was before.
>>>>
>>>>   
>>>>       
>>>     That is NOT the case. It must have just quit without doing anything. 
>>> The error you copied is a kernel complaining all is not right.
>>>
>>>     You can not just walk out and leave a loader stuck at a problem. 
>>> This will just screw up your system.
>>>
>>> Karl
>>>
>>>     
>>>> It wouldn't boot from the HD, so I put the disk in and booted in the "Safe Mode" which took me to a 
>>>> list of choices.  I chose the "Recovery Mode" and here's the errors I get in the last couple of 
>>>> lines starting with the one that appears correct (lines are as seen on the screen):
>>>>
>>>> 	[   34.484528] RAMDISK:  Compressed image found at block 0
>>>> 	[   34.493544] invalid compressed format (err=1)
>>>> 	[   34.494287] VFS: Cannot open root device "UUID=dc6c48c4-cc9b-4851-a668-a132c5
>>>> 9bafbe" or unknown-block(0,0)
>>>> 	[   34.494351] Please append a correct "root=" boot option; here are the availab
>>>> le partitions:
>>>> 	[   34.494414] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown wn-block(0,0)
>>>> _
>>>>
>>>>
>>>>
>>>> OK...   everything is exactly as I see it on the screen.  I hope this too is detailed enough.
>>>>
>>>> Any ideas?
>>>>
>>>> Joseph
>>>>
>>>>       
>>
>> Karl, you'd commented on my error, but the real problem is in the last part.  Would you come over 
>> here and help me with the last part....    which I will re-iterate:
>>
>> It wouldn't boot from the HD, so I put the disk in and booted in the "Safe Mode" which took me to a 
>> list of choices.  I chose the "Recovery Mode" and here's the errors I get in the last couple of 
>> lines starting with the one that appears correct (lines are as seen on the screen):
>>
>>   	[   34.484528] RAMDISK:  Compressed image found at block 0
>>   	[   34.493544] invalid compressed format (err=1)
>>   	[   34.494287] VFS: Cannot open root device "UUID=dc6c48c4-cc9b-4851-a668-a132c5
>> 9bafbe" or unknown-block(0,0)
>>   	[   34.494351] Please append a correct "root=" boot option; here are the availab
>> le partitions:
>>   	[   34.494414] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown wn-block(0,0)
>>   _
>>
>>
>> So can you offer any wisdom for how to correct this problem??  Also, what do you do with a loader 
>> that's hung up?  I would think that you wait or shut it down....   both of which I'm told is not 
>> good.  There's nothing else to do.
>>
>> Joseph
>>
>>
>>
>>
>>   
>     Tou are the only person I have ever done this to. You are way to 
> uneducated to teach a thing to. So try to get what you want from someone 
> else :-)
> 
> Karl
> 
> 



That's ok, Karl.  I was only trying to find answers to things that I felt was important to know. 
Even about things YOU thought important enough to mention...  and I asked for further information so 
I would understand it all better.

I'm sorry you're taking my requests for information this way.



Joseph