Re: Install hangup....

David Vincent wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Joseph wrote:
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.

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?


1. hard drive error - are you sure your hd is working fine? i'd run
spinrite on there but sadly that isn't a free utility and i can't point
you at a download for it - perhaps boot into the livecd desktop and run
fsck on your created partitions? what filesystem did you choose? ext3?

2. ram error - did you test your ram yet?

3. boot the livecd to a desktop, open a terminal, issue the command
"blkid", compare the UUID results with the partition grub is trying to
load up there in your pasted text and see if it it aimed at the wrong
partition or something. i doubt this is it, usually grub is good at
throwing its own obscure error I have to google to understand.

4. boot into the livecd desktop and then use the partition editor to
setup your partitions before you run the install, then install from the
alternate cd and use manual partitioning to install making sure you
don't delete your partitions you just mount them at appropriate spots
and format the filesystems as necessary.

hrm...anyone else?

- -d


I booted to the live CD and I tried to bring up the internet browser and when the browser came up,
the system seized and there were about 5 varying width multi-colored bars across the screen....
and it sat there.

I did the memory test and found some interesting little tidbits about this computer.... I have a
Celeron 2660Mhz chip; 512Mb Ram; and the Chipset is Intel i845 E/G/PE/GE 133Mhz - Not sure what all
the chipset info means though... <grimace>

However, my memory came up with a lot of errors.... I ran it twice and it's now saying there's 184
errors.... AND it says, "Unexpected Interrupt - Halting" at the top of the red error field.

So I would suspect that the drive, which is read ok in my other computer, is not the problem...
but rather the memory.

Guess I must go find another stick of RAM....

Are my suspicions probably?

Joseph




--
ubuntu-users mailing list
ubuntu-users@xxxxxxxxxxxxxxxx
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

Relevant Pages

  • Re: Can someone else help? Was changing partition size.
    ... I tried the supposed fix to make Windows 98SE boot up with more ... than a gig of memory but that has not worked either. ... The last time I did that set of changes, it was done by using a Linux LiveCD ... and finish the Win98 install. ...
    (microsoft.public.windowsxp.general)
  • Re: Screen break up and boot up hanging.
    ... The memory modules do match. ... distortions appear for the first few minutes. ... Then the boot up routine stalled / hung. ... Does your machine require/suggest that you install the modules in pairs? ...
    (microsoft.public.windowsxp.hardware)
  • Re: Problem after converting FDisk Partitions to LVM
    ... The issue I was reporting about was, that my 2 freshly installed W4.0 partitions didn't boot up anymore, after the eCS beta was installed and changed FDisk to LVM in the process. ... I wasn't trying to migrate an existing, over time matured W4 system to eCS, rather than trying to learn about the shortcomings of the latest FDisk and potential dangers in possibly switching my W4 FP16+ box to LVM, in order to install and boot additional OS' from HDD areas beyond FDisk's limited abilities. ...
    (comp.os.os2.setup.storage)
  • Re: Slow memory check and Hard drive boot up
    ... After the memory check is through,it takes a very long time to ... recognize the hard drives, and DVD drive. ... I have a 400GB drive as the boot drive and a ITB drive for data. ... may show the Windows partitions you have. ...
    (microsoft.public.windowsxp.general)
  • Re: Total nightmare with XP remove & reinstall
    ... execute "winnt" from the i386 directory, and install from the hard drive. ... leaving the rest of the disk for the actual install. ... And if you needed a boot disk, ... Memtest86+ tests virtually all the memory ...
    (alt.comp.hardware.pc-homebuilt)