| 1 |
On 28 July 2010 15:27, Bill Longman <bill.longman@×××××.com> wrote: |
| 2 |
> On 07/28/2010 07:04 AM, Mick wrote: |
| 3 |
>> On 28 July 2010 14:53, Bill Longman <bill.longman@×××××.com> wrote: |
| 4 |
>>> On 07/28/2010 06:42 AM, Mick wrote: |
| 5 |
>>>> On 28 July 2010 09:50, KH <gentoo-user@××××××××××××××××.de> wrote: |
| 6 |
>>>> |
| 7 |
>>>>> I installed grub by connecting the hdd to my workstation. This did not |
| 8 |
>>>>> change anything. |
| 9 |
>>>>> Also I changed /etc/fstab . Now I have 0 0 for every partition. The pc |
| 10 |
>>>>> boots fine now. I can use it but ... There is no /dev/hd* . Running |
| 11 |
>>>>> mount /boot I get the answer /dev/hda1 does not exist. Also there is no |
| 12 |
>>>>> /dev/sd* |
| 13 |
>>>>> |
| 14 |
>>>>> Any ideas? |
| 15 |
>>>> |
| 16 |
>>>> KH, if you have changed the kernel to use libATA (i.e. the newer |
| 17 |
>>>> SATA/PATA options) then you need to update your fstab from /dev/hdaX |
| 18 |
>>>> to /dev/sdaX and change your grub.conf accordingly. |
| 19 |
>>> |
| 20 |
>>> But he doesn't even have those devices, so this will not do him any good |
| 21 |
>>> until we know how the kernel is configured (or not) and get the devices |
| 22 |
>>> back. |
| 23 |
>> |
| 24 |
>> I am not sure that he does not have those devices ... I don't know if |
| 25 |
>> the error message is returned from grub or from the OS. |
| 26 |
>> |
| 27 |
>> It could be that the kernel stanza is wrongly pointing to /dev/hda, |
| 28 |
>> and, or fstab is not correct. |
| 29 |
> |
| 30 |
> He says the "pc boots fine now" and he "can use it" and he goes on to |
| 31 |
> say that he has "no /dev/hd*" or "/dev/sd*" devices, so I have to |
| 32 |
> believe he's got a running system. |
| 33 |
|
| 34 |
Hmm ... he'll have to be able to hang his OS off some fs or other if |
| 35 |
it is indeed working. Unless he's running some clever ramdisk, then I |
| 36 |
would not reach the conclusion that he has a working OS. |
| 37 |
|
| 38 |
> Not having any /dev/hd* files would |
| 39 |
> support the error trying to mount /boot. Trying to fix /etc/fstab first |
| 40 |
> is not the way to attack his problem given the information we have now. |
| 41 |
|
| 42 |
Perhaps he passed the correct path to his grub and the boot sequence |
| 43 |
fails when it tries to find the devices listed in fstab, so the OS |
| 44 |
never completes booting. |
| 45 |
|
| 46 |
Either way, hopefully the OP will shed some light to this rather than |
| 47 |
us assuming more or less what might actually be the case. |
| 48 |
-- |
| 49 |
Regards, |
| 50 |
Mick |
Archives