2009/12/2 Tony Pursell <a...@princeswalk.fsnet.co.uk>:
> On 1 Dec 2009 at 23:51, Kris Douglas wrote:
>
>>
>> 2009/12/1 Kris Douglas <krisdoug...@gmail.com>:
>> > 2009/12/1 Tony Pursell <a...@princeswalk.fsnet.co.uk>:
>> >> On 1 Dec 2009 at 23:19, Kris Douglas wrote:
>> >>
>> >>>
>> >>> Hello everyone, I'm struggling with an installation of Ubuntu Karmic
>> >>> on my netbook.
>> >>>
>> >>> After an update, I switched my machine off and left it till the
>> >>> morning, when I went to boot it up, it sat on "loading grub.." for a
>> >>> while, and then proceeded to display "error: biosdisk read error" and
>> >>> then return me to a grub rescue> CLI.
>> >>>
>> >>> "Ok" I thought, and I went to try some of the recovery commands, which
>> >>> didn't actually work, as in, "not found", other than SET and LS. This
>> >>> is screwing me over quite a bit, because disasembling the machine in
>> >>> order to get the drive out it a pain, and I need it for work on a
>> >>> daily basis, ideally I would like to get my files off there.
>> >>>
>> >> To get files of...
>> >>
>> >> Perhaps a couple of USB sticks - one with a version of Ubuntu to boot
>> >> off (needs to be a recent version if you are using a ext4 file system on
>> >> your hard drive) and another to copy the files on to.
>> >
>> > I've just tried that, it doesn't seem to want to boot the device, im
>> > watching it's progress, it seems to be moving along, but very very
>> > slowly. Im reading some ata1 device errors too.
>> >
>> > --
>> > Kris Douglas
>> >
>>
>> Right, Gnome has come online now, I've accessed the device with
>> gparted, and it seems to have identified the partitions in the search,
>> but it is sitting forever reading the stuff on /dev/sda (the device)
>> and other than that, it's made little visual progress.
>>
>
> You might find some help with the original grub problem at
>
> http://grub.enbug.org/Manual
>
> Tony
>
> PS I'm not an expert - just trying to help with what little knowledge I
> have!

I much appreciate your help, Tony :)

Furthermore, I think the drive is either dead or very corrupted, loads
of I/O errors, so I think it's the drive.



-- 
Kris Douglas

-- 
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.ubuntu.com/UKTeam/

Reply via email to