Author Topic: LiveCD install to hard disk drives me bananas  (Read 1174 times)

Offline wedgetail

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 2469
  • Any Bugs in site?
LiveCD install to hard disk drives me bananas
« on: April 25, 2011, 10:02:45 PM »
Edit: January 2012


http://www.pclinuxos.com/forum/index.php/topic,108512.msg927537.html#msg927537
In this thread after many months the problem was found, but not yet corrected on new ISOś as of 2012.12



Edit Saturday April 30 2011

After a very long and to me hard slog testing many combinations of drives it does seem clear that the something on the hard drive in question, I will call it SeaGate-2 (/dev/sdb in below) is preventing GRUB session at the end of a draklive-install to finish.
konsole trace indicates install is finished ie command prompt released.

I think on 3 occasions draklive-install worked, that made for very frustrating trouble shooting.

Test and using mount to show what is busy shows that the target drive is not released/umounted.

With the second HDD installed both the first and second drive will not complete a MiniMe liveCD install to a partition

Remove SeaGate-2 so only /dev/sda is mounted, LiveCD install full system

Install SeaGate-2 as only drive and (making it bootable of course) LiveCD installs full system to partition fine

Install original /dev/sda2 as the second drive and SeaGate-2 still installed and being booted, the problem is back

Installing SeaGate-2 as second drive in another PC and it works fine.

The problem was preventing me from do a recovery install of re-master backups to any partition, making it a bit scary having re-master ISOs but unable to do more than just run them.

Member as has pointed out as I understand that the GRUB session is trying to write the menu.lst and meets a surprise obstacle.

From what I can see the complete filesystem has been written to target partition and I made an attempt manually boot the partition but must admit at the time I was so confused that the failure to do so a couple of times could have been a simple error on my part

I can now recover a system by removing the second HDD while doing so gives me a practical solution, I find it very hard to let go.  The question also arises is that hard drive no longer 'safe'.

I really would like to figure what is going on so I am not leaving it just yet. This edit does not bump the topic but if anybody reads here, I am
welcoming any suggestions.
 
------------------------------------------------------------
------------------------------------------------------------


Having had some fun testing LiveHDD generation, which is successful for me now, I believe. The script Just19 kindly provided will make the LiveHDD installs fine.
During work I have discovered a really weird problem, my system will no longer install to hard disk from a newly downloaded minime2010.12

The troubles are described in more details here
http://www.pclinuxos.com/forum/index.php/topic,90298.0.html

However I have decided to hide here for some more general help. I have repeated the download of the minime ISO using my KDE install, unusual for me this time I also downloaded the md5sum.  Previously I had done md5sum and media check on the CD RW I was using (not had trouble so far with this disk, but used quite a few times too).

Edit: below line for clarity:
A second minime2010.12 iso downloaded today, I immediately burnt to a CD RO and the md5sum checked, ok

While in KDE I reformatted two partitions: /dev/sda2 (LABEL=minime2010) and /dev/sdb18 (LABEL=DELTA-18) on two separate drives. ( I can' believe it has any influence but the sda was set up with the old fdisk and the sdb was setup with the new fdisk sector offset 63 and 2048 for those in the know  ;D)

I have also checked e2fsck on the partitions, nothing reported (one example below on sdb18)

Now I boot the LiveCD, runs fine, and open a root konsole and use {draklive-install} to catch the record;  

While in KDE

Code: [Select]
[root@localhost gert]# mke2fs -t ext4 -L minime2010 /dev/sda2
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=minime2010
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
1831424 inodes, 7325640 blocks
366282 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
224 block groups
32768 blocks per group, 32768 fragments per group
8176 inodes per group
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000

Writing inode tables: done                            
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 35 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.
[root@localhost gert]#

[root@localhost gert]# mke2fs -t ext4 -L DELTA-18 /dev/sdb18
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=DELTA-18
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
1310720 inodes, 5242880 blocks
262144 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
160 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000

Writing inode tables: done                            
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 39 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.
[root@localhost gert]#

Starting the LiveCD

/dev/sda2

Code: [Select]
[root@localhost guest]# draklive-install

I slect only /sda2 as the root for the install
The drive has a common LABEL=SWAP4000 (4 GB swap)
Failed to do the uncheck to prevent formatting, so we will see
  Should retain my LABEL=minime2010

[root@localhost guest]# draklive-install
/media/ user
umount: /dev/sda2: not mounted
mke2fs 1.41.12 (17-May-2010)
tune2fs 1.41.12 (17-May-2010)
Setting maximal mount count to -1
Setting interval between checks to 0 seconds
tune2fs 1.41.12 (17-May-2010)
Setting up swapspace version 1, size = 4088504 KiB
no label, UUID=6fdbb9bb-f52e-4f56-8c4b-844de0960066
Setting up swapspace version 1, size = 4088504 KiB
LABEL=swap4000, UUID=061c4ede-3435-4b06-8be5-e07ba90e2191
tar: ./home/guest/.local/share/akonadi/akonadiserver.socket: socket ignored
tar: ./home/guest/.local/share/akonadi/db_misc/mysql.socket: socket ignored
tar: ./home/guest/tmp/ksocket-guest/klauncherMT3281.slave-socket: socket ignored
tar: ./home/guest/tmp/ksocket-guest/kdeinit4__0: socket ignored
tar: ./var/run/acpid.socket: socket ignored
tar: ./var/run/xdmctl/dmctl-\:0/socket: socket ignored
tar: ./var/run/xdmctl/dmctl/socket: socket ignored
tar: ./var/run/uuidd/request: socket ignored
tar: ./var/run/nscd/socket: socket ignored
tar: ./var/run/dbus/system_bus_socket: socket ignored
tar: ./var/run/avahi-daemon/socket: socket ignored
add_entry at /usr/lib/libDrakX/bootloader.pm line 604, <> line 9.
standalone::bug_handler() called from /usr/lib/libDrakX/bootloader.pm:604
bootloader::add_entry() called from /usr/lib/libDrakX/bootloader.pm:1109
bootloader::suggest() called from /usr/lib/libDrakX/any.pm:211
any::setupBootloaderBefore() called from /usr/lib/libDrakX/any.pm:135
any::setupBootloaderBeforeStandalone() called from /usr/sbin/draklive-install:308
main::setup_bootloader() called from /usr/sbin/draklive-install:73
main::install_live() called from /usr/sbin/draklive-install:42
[root@localhost guest]#    #Fail to pick up the Grub section

/dev/sdb18

Code: [Select]
[root@localhost guest]# e2fsck -f /dev/sdb18
e2fsck 1.41.12 (17-May-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
DELTA-18: 11/1310720 files (0.0% non-contiguous), 126289/5242880 blocks
[root@localhost guest]#


I uncheck the format option before installing
Installing files going along fine (always it seems), as usual

Code: [Select]
[root@localhost guest]# draklive-install
/media/ user
Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion `width >= -1' failed at /usr/lib/libDrakX/fs/partitioning_wizard.pm line 390.
Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion `width >= -1' failed at /usr/lib/libDrakX/fs/partitioning_wizard.pm line 390.
umount: /dev/sdb18: not mounted
Setting up swapspace version 1, size = 4088504 KiB
LABEL=swap4000, UUID=061c4ede-3435-4b06-8be5-e07ba90e2191
Setting up swapspace version 1, size = 4088504 KiB
no label, UUID=6fdbb9bb-f52e-4f56-8c4b-844de0960066
tune2fs 1.41.12 (17-May-2010)
tar: ./home/guest/.local/share/akonadi/akonadiserver.socket: socket ignored
tar: ./home/guest/.local/share/akonadi/db_misc/mysql.socket: socket ignored
tar: ./home/guest/tmp/ksocket-guest/klauncherMT3281.slave-socket: socket ignored
tar: ./home/guest/tmp/ksocket-guest/kdeinit4__0: socket ignored
tar: ./var/run/acpid.socket: socket ignored
tar: ./var/run/xdmctl/dmctl-\:0/socket: socket ignored
tar: ./var/run/xdmctl/dmctl/socket: socket ignored
tar: ./var/run/uuidd/request: socket ignored
tar: ./var/run/nscd/socket: socket ignored
tar: ./var/run/dbus/system_bus_socket: socket ignored
tar: ./var/run/avahi-daemon/socket: socket ignored
add_entry at /usr/lib/libDrakX/bootloader.pm line 604, <> line 9.
standalone::bug_handler() called from /usr/lib/libDrakX/bootloader.pm:604
bootloader::add_entry() called from /usr/lib/libDrakX/bootloader.pm:1109
bootloader::suggest() called from /usr/lib/libDrakX/any.pm:211
any::setupBootloaderBefore() called from /usr/lib/libDrakX/any.pm:135
any::setupBootloaderBeforeStandalone() called from /usr/sbin/draklive-install:308
main::setup_bootloader() called from /usr/sbin/draklive-install:73
main::install_live() called from /usr/sbin/draklive-install:42
[root@localhost guest]#

Again it fails the Grub session.

I would like this sorted out as I have a number of re-master backups, especially my fully configured minime of a few days ago.

Now that I can not do full install from either a CD or LiveHDD I am sort of between the rock and a hard place, still wanting to know what the problem may be.

I believe the install session should end with something like:

Code: [Select]
   GNU GRUB  version 0.97  (640K lower / 3072K upper memory)

 [ Minimal BASH-like line editing is supported.  For the first word, TAB
   lists possible command completions.  Anywhere else TAB lists the possible
   completions of a device/filename. ]
grub> root (hd0,5)
 Filesystem type is ext2fs, partition type 0x83
grub> setup --stage2=/boot/grub/stage2 (hd0,5)
 Checking if "/boot/grub/stage1" exists... yes
 Checking if "/boot/grub/stage2" exists... yes
 Checking if "/boot/grub/e2fs_stage1_5" exists... yes
 Running "embed /boot/grub/e2fs_stage1_5 (hd0,5)"... failed (this is not fatal)
 Running "embed /boot/grub/e2fs_stage1_5 (hd0,5)"... failed (this is not fatal)
 Running "install --stage2=/boot/grub/stage2 /boot/grub/stage1 (hd0,5) /boot/grub/stage2 p /boot/grub/menu.lst "... succeeded
Done.
grub> quit

This was an install session ending where the minime LiveCD on the CD RW was used on and older pc

Edit, badly formulated paragraph below as it lacked important dat, now in red:

Only about an hour ago I used the same CD RW to make a successful install to "empty" space on a drive, on another different Desktop PC system As I was caught un aware here, selecting install to empty space on the single hard drive. The install is not exactly the same as installing to an existing formatted  partition. The install formatted two partitions to ext4 but terminated the Grub session properly in my understanding, made the system Multiboot XP/Linux



as drew my attention the ending few lines which seems to indicate that writing to the menu.lst is attempted ...  and I notice the debug handler may be called.

I am no doubt overlooking something blindingly obvious, but since I had CD install well under control, I have forgotten what I used to look for if it did not work.

Recalcitrant pc system specs:
The pc is simple Intel Pentium Dual Core E5300, 4GB of RAM and two hard disks with external USB drive hanging off for backup (often not connected)

In the last 2 days I don't remember looking in dmesg when working the LiveCD, hmmm will have a look next time.

I have re-installed GRUB a number of times, an at one stage I thought this was the problem as I had one successful run out of perhaps 20 attempts.

What can make GRUB sneak away apparently without leaving a trace?

I seem to remember one of my systems had gdb debugger install, but don't remember how I used it.  Should I attempt installing gdb this on the LiveCD and then run draklive-install?
« Last Edit: January 14, 2013, 10:53:07 PM by wedgetail »
32 bit: KDE (older) & various KDE-mini, ASUSTek P5P41D Rev X.0x, BIOS AMI0207 07/21/2009, "Pentium(R) Dual-Core CPU E5300 @ 2.60GHz", nVidia GeForce 9600 GT, 2x1GB Seagate Technology 1000528AS HDD
TV CompuPro VideoMate Vista E700 (not working in Linux), Acer X243HD LCD Screen

Offline AS

  • Hero Member
  • *****
  • Posts: 4098
  • Have a nice ... night!
Re: LiveCD install to hard disk drives me bananas
« Reply #1 on: April 26, 2011, 02:19:05 AM »
Hello wedgetail,
Quote
add_entry at /usr/lib/libDrakX/bootloader.pm line 604, <> line 9.
standalone::bug_handler() called from /usr/lib/libDrakX/bootloader.pm:604
bootloader::add_entry() called from /usr/lib/libDrakX/bootloader.pm:1109
bootloader::suggest() called from /usr/lib/libDrakX/any.pm:211
any::setupBootloaderBefore() called from /usr/lib/libDrakX/any.pm:135
any::setupBootloaderBeforeStandalone() called from /usr/sbin/draklive-install:308
main::setup_bootloader() called from /usr/sbin/draklive-install:73
main::install_live() called from /usr/sbin/draklive-install:42
[root@localhost guest]#    #Fail to pick up the Grub section


I think you don't need gdb, because you already have a backtrace of what is going on, quoted above:
read from bottom to top (as usual for backtraces):

the main script draklive-install
at line 42 call install_live()
at line 73 call setup_bootloader()
at line 308 call setupBootloaderBeforeStandalone()
...
at line 1109 add_entry() is called:
Quote
bootloader::add_entry() called from /usr/lib/libDrakX/bootloader.pm:1109

at line 604 (which is near the end of subroutine add_entry() ) the program call "die" which is a perl function that raise exceptions,
and therefore "standalone::bug_handler() called from /usr/lib/libDrakX/bootloader.pm:604" is supposed to catch the exception.

To me look like add_entry() is failing in a unexpected way.


I already suggested (at least for the time of installation) to remove the suspected entries, suggested in the other thread:
http://www.pclinuxos.com/forum/index.php/topic,90298.msg757061.html#msg757061

I'm quoting here the same message because I think it's strictly related:
Quote
title   Just19-minime_new_a_(hd1,16)
kernel (hd1,16)/Just19-minime_new_a_(hd1,16)/vmlinuz livecd=/Just19-minime_new_a_(hd1,16)/Just19-minime_new_a_(hd1,16) fromusb root=UUID=a3462aa3-67fa-4bb5-b685-3480c31ef194 acpi=on vga=791 splash=verbose
initrd (hd1,16)/Just19-minime_new_a_(hd1,16)/initrd.gz



/usr/lib/libDrakX/bootloader.pm line 604 <----------

if I understand correctly the script, this is actually failing when trying to add a new entry to menu.lst,
I would temporarily remove the entries related to poorman, may be the installation script fail while parsing unusual lines containing (hd?,?) ...

AS


Did you tried to perform the installation without those entry ?

AS

Offline wedgetail

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 2469
  • Any Bugs in site?
Re: LiveCD install to hard disk drives me bananas
« Reply #2 on: April 26, 2011, 03:08:01 AM »
as
You are trying to trick me  ;D I am sure. Your comments valued though, as the deeper insights into the programs I love, but I am lost too. I understand what you are saying but I am only a dabbler and that is problematic, getting in too deep

1.. Please forget anything about Just19 script, this is what you refer to in quote. In this thread the script is not involved. The script generates these names you higlight, it is meant as drive/partition hint in Grub speak.  If my problem is solved Just19 script generated files will also work I believe. OK, no more script for the time being.

2.. This thread only involves the use of a pristine as can be LiveCD, which will not work on this particular system, and I have no idea where to look, well not quite true. First let me know if you agree, no mor script in here at the moment  :D  

a.. LiveCD booted, immediately trying to do a full install first to target /dev/sda2 then when failed immediately targetting /dev/sdb18.  This is two different drives, but are the two main drives on the PC system I am using, really my main workhorse with many systems.

The targets are "cleaned out" each time buy reformatting, just desperate belts and braces on my part.  I am hiding here as I think it is just too weird for newcomers.

b.. I have just re-viewed my original post in this thread, after a nice walk along the beach with nobody in sight,  8) did me good.  Made some edits to clarify points.
« Last Edit: April 26, 2011, 03:25:50 AM by wedgetail »
32 bit: KDE (older) & various KDE-mini, ASUSTek P5P41D Rev X.0x, BIOS AMI0207 07/21/2009, "Pentium(R) Dual-Core CPU E5300 @ 2.60GHz", nVidia GeForce 9600 GT, 2x1GB Seagate Technology 1000528AS HDD
TV CompuPro VideoMate Vista E700 (not working in Linux), Acer X243HD LCD Screen

Offline wedgetail

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 2469
  • Any Bugs in site?
Re: LiveCD install to hard disk drives me bananas
« Reply #3 on: April 26, 2011, 03:30:42 AM »
I am now looking at {dmesg} when running Live systems, I need to repeat a run with the Pristine LiveCD as any other system is no suspect to me, but one of the suspect showed heap of EXT2 messages that I don't like. Before posting I would rather see what the P LiveCD does.

For my own record: I have the {dmesg} output from my running {Gert Poorman} used to attempt some gdb work and another full install to /dev/sda2 - failed as expected

Quote
[root@localhost gert]# mount
/dev/root on / type rootfs (rw)
none on /proc type proc (rw)
none on /dev/pts type devpts (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
/dev/sda2 on /mnt/install type ext4 (rw)   <-- /sda2 mount is now hardwired into the system
none on /mnt/install/proc type proc (rw)
none on /mnt/install/sys type sysfs (rw)
none on /mnt/install/proc/bus/usb type usbfs (rw)
/dev/sdc1 on /media/TOSHIBA type vfat (rw,nosuid,nodev,uhelper=hal,uid=500,utf8,shortname=mixed,flush)
[root@localhost gert]#

The mention of hard wiring because, the running user session, root konsole can not umount /sda2
I can run {draklive-install} again targetting /dev/sdb18 running umount now when install fails, shows that /sdb18 now hardwired (/sda2 does not appear in the umount result but I can still not access it via another mountpoint.

Logging out and logging in as root and try umount no joy either, it is there for good as busy now.

The only way I can terminate is using the mechanical re-set or power off (two different buttons) even the power button now seems to misbehave, ie turns on when I think I have switched off. Need longer than usual push and hold.

dmesg from P (Pristine) LiveCD run

Running LiveCD I have recorded what is added after {draklive-install} is started, a few martian inserts and journaling starts I have  edited out. I have the full dmesg record, but the start looks normal to me at quick glance.

I wonder why all partitions are mounted and more than once.

Quote
EXT4-fs (sda2): mounted filesystem with ordered data mode
EXT4-fs (sda3): mounted filesystem with ordered data mode
EXT4-fs (sda7): mounted filesystem with ordered data mode
EXT3-fs (sda8): mounted filesystem with ordered data mode
EXT4-fs (sda9): mounted filesystem with ordered data mode
EXT4-fs (sda10): mounted filesystem with ordered data mode
EXT4-fs (sda11): mounted filesystem with ordered data mode
EXT4-fs (sda12): mounted filesystem with ordered data mode
EXT4-fs (sda13): mounted filesystem with ordered data mode

EXT4-fs (sda3): mounted filesystem with ordered data mode

EXT4-fs (sdb2): mounted filesystem with ordered data mode
EXT4-fs (sdb3): mounted filesystem with ordered data mode
EXT4-fs (sdb5): mounted filesystem with ordered data mode
EXT4-fs (sdb6): mounted filesystem with ordered data mode
EXT4-fs (sdb7): mounted filesystem with ordered data mode
EXT4-fs (sdb8): mounted filesystem with ordered data mode
EXT4-fs (sdb9): mounted filesystem with ordered data mode
EXT4-fs (sdb10): mounted filesystem with ordered data mode
EXT4-fs (sdb11): mounted filesystem with ordered data mode
EXT4-fs (sdb12): mounted filesystem with ordered data mode
EXT4-fs (sdb13): mounted filesystem with ordered data mode
EXT4-fs (sdb14): mounted filesystem with ordered data mode
EXT3-fs (sdb15): mounted filesystem with ordered data mode
EXT3-fs (sdb16): mounted filesystem with ordered data mode
EXT3-fs (sdb17): mounted filesystem with ordered data mode

unionfs: new lower inode mtime (bindex=0, name=db_data)
unionfs: new lower inode mtime (bindex=0, name=session-bus)
unionfs: new lower inode mtime (bindex=0, name=.gnupg)
unionfs: new lower inode mtime (bindex=0, name=gdm)
unionfs: new lower inode mtime (bindex=0, name=console)


EXT4-fs (sda2): mounted filesystem with ordered data mode

Adding 4088500k swap on /dev/sda6.  Priority:-1 extents:1 across:4088500k


EXT4-fs (sda3): mounted filesystem with ordered data mode
EXT4-fs (sda7): mounted filesystem with ordered data mode
EXT3-fs (sda8): mounted filesystem with ordered data mode
EXT4-fs (sda9): mounted filesystem with ordered data mode
EXT4-fs (sda10): mounted filesystem with ordered data mode
EXT4-fs (sda11): mounted filesystem with ordered data mode
EXT4-fs (sda12): mounted filesystem with ordered data mode
EXT4-fs (sda13): mounted filesystem with ordered data mode
EXT4-fs (sda3): mounted filesystem with ordered data mode

EXT4-fs (sdb2): mounted filesystem with ordered data mode
EXT4-fs (sdb3): mounted filesystem with ordered data mode
EXT4-fs (sdb5): mounted filesystem with ordered data mode
EXT4-fs (sdb6): mounted filesystem with ordered data mode
EXT4-fs (sdb7): mounted filesystem with ordered data mode
EXT4-fs (sdb8): mounted filesystem with ordered data mode
EXT4-fs (sdb9): mounted filesystem with ordered data mode
EXT4-fs (sdb10): mounted filesystem with ordered data mode
EXT4-fs (sdb11): mounted filesystem with ordered data mode
EXT4-fs (sdb12): mounted filesystem with ordered data mode
EXT4-fs (sdb13): mounted filesystem with ordered data mode
EXT4-fs (sdb14): mounted filesystem with ordered data mode
EXT3-fs (sdb15): mounted filesystem with ordered data mode
EXT3-fs (sdb16): mounted filesystem with ordered data mode
EXT3-fs (sdb17): mounted filesystem with ordered data mode

unionfs: new lower inode mtime (bindex=0, name=.config)
unionfs: new lower inode mtime (bindex=0, name=log)

Just an odd thing:
A one of the attempts installing from LiveCD I noticed the installer wanted to format ext2 on my preformatted partitions, normally I no longer "see or register" what the proposed type is but I am sure I have seen this before. 



( work in progress, .......)
« Last Edit: April 26, 2011, 05:37:24 AM by wedgetail »
32 bit: KDE (older) & various KDE-mini, ASUSTek P5P41D Rev X.0x, BIOS AMI0207 07/21/2009, "Pentium(R) Dual-Core CPU E5300 @ 2.60GHz", nVidia GeForce 9600 GT, 2x1GB Seagate Technology 1000528AS HDD
TV CompuPro VideoMate Vista E700 (not working in Linux), Acer X243HD LCD Screen

Offline Was_Just19

  • Hero Member
  • *****
  • Posts: 6849
  • MLU
Re: LiveCD install to hard disk drives me bananas
« Reply #4 on: April 26, 2011, 06:26:26 AM »
wedgetail,
                   following on from what  as  posted ........  on the target PC, delete all poorman references in all menu.lst files that may be present on any partition and try the install again.

It seems possible/even likely  that the poorman entries with the (hdx,y) extensions are causing Grub a problem when it tries to pick up other installs on the PC.

I would also suggest that you ensure that there is no usb device attached when attempting the install, just to eliminate another possible cause of the problem.

It seems this extension will need to be edited to prevent problems and also allow for persistence to be used.

regards.

Offline menotu

  • PCLinuxOS Tester
  • Super Villain
  • *******
  • Posts: 15515
  • ┌∩┐(◕_◕)┌∩┐
Re: LiveCD install to hard disk drives me bananas
« Reply #5 on: April 26, 2011, 07:42:43 AM »
Have you tried an earlier ISO for the install - mebbe a 2010.10 or 2010.07 version - you just never know.

I've known the KDE 2010.12 ISO to sometimes cause problems writing the bootloader at the end of the install - sometimes 20+ minutes before the reboot message appears (but GRUB does seem to work after the long wait)
PCLinuxOS 32bit KDE 4.10.4; kernel-3.4.11-pclos1.bfs & 64bit 3.4.38bfs; NVidia GeForce 8400GS 1GB 310.19 driver

Sony Vaio SVE1513A4ESI Laptop, Intel Core i5, 2.6GHz, 6GB RAM, 750GB, 15.6" Intel HD Graphics 4000

Offline wedgetail

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 2469
  • Any Bugs in site?
Re: LiveCD install to hard disk drives me bananas
« Reply #6 on: April 26, 2011, 07:57:23 AM »
Just19
With my last posting above from dmesg I almost think I can agree with you. Not convinced, but since I was considering removing all drives from the recalcitrant pc and install a brand new drive with zilch bytes from this pc this sounds like a good step on the way.

Can confirm that the other PC that has seen absolutely no PoorMan stuff and only one drive is performing faultlessly on the original RW CD, just preparing a new Remaster LiveCD-Custom for Wedgtail to make operation about 20% faster for my use, by saving clicks. Looking forward to get my MiniMe back, it is when you don't have it you notice  ;D

Test:
Removing PoorMan Ref very quickly no better, then taking out my USB 2GB memory stick I use as notepad. No go same problem.

menotu
I did try a LiveCD minime2010.07 same result and also one of my minime re-masters rock solid same failure on trying an install grub session fails.

I don't think I have waited that long for anything, not that patient unless I happen to be making a cop of coffee or being called on the telephone.

Just19 may just have lit a candle giving a dimmer of enlightenment.
« Last Edit: April 29, 2011, 09:35:12 PM by wedgetail »
32 bit: KDE (older) & various KDE-mini, ASUSTek P5P41D Rev X.0x, BIOS AMI0207 07/21/2009, "Pentium(R) Dual-Core CPU E5300 @ 2.60GHz", nVidia GeForce 9600 GT, 2x1GB Seagate Technology 1000528AS HDD
TV CompuPro VideoMate Vista E700 (not working in Linux), Acer X243HD LCD Screen