Page 1 of 4

Posted: Fri 27 Jul 2007, 11:03
by Greystar
Sorry barry......I don't use terminal much didn't understand. And thanks for the just highlight bit i was tring Ctrl insert and gave up thats why i did a screenshot. Anyway,

sh-3.00# cat /proc/partitions
major minor #blocks name

7 0 71784 loop0
7 1 524288 loop1
3 0 29302560 hda
3 1 3582463 hda1
3 2 3582495 hda2
3 3 3590527 hda3
3 4 1 hda4
3 5 257008 hda5
3 6 5116671 hda6
3 7 5124703 hda7
sh-3.00# probepart
/dev/hdc|iso9660|0|QSI CD-RW/DVD-ROM SBW-242
/dev/hda1|ext2|7164927|Linux Ext2Fs
/dev/hda2|ext2|7164990|Linux Ext2Fs
/dev/hda3|ext2|7181055|Linux Ext2Fs
/dev/hda4|none|37094085|Extended (contains other slice)
/dev/hda5|swap|514017|Linux Swap
/dev/hda6|ext2|10233342|Linux Ext2Fs
/dev/hda7|ext3|10249407|Linux Ext3FS
sh-3.00# fdisk -l

Disk /dev/hda: 30.0 GB, 30005821440 bytes
255 heads, 63 sectors/track, 3648 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hda1 1 446 3582463+ 83 Linux
/dev/hda2 447 892 3582495 83 Linux
/dev/hda3 893 1339 3590527+ 83 Linux
/dev/hda4 1340 3648 18547042+ 5 Extended
/dev/hda5 1340 1371 257008+ 82 Linux swap / Solaris
/dev/hda6 1372 2008 5116671 83 Linux
/dev/hda7 2009 2646 5124703+ 83 Linux
sh-3.00#

2.17 Installer Problems

Posted: Fri 27 Jul 2007, 22:47
by nic2109
Hello; while I think that all the partitions have been detected the resulting installed system will not boot up. It gives me Error 15 - file not found.

The command output you requested is
# cat /proc/partitions
major minor #blocks name

7 0 74780 loop0
8 0 96213285 sda
8 1 10241406 sda1
8 2 10241437 sda2
8 3 1 sda3
8 5 2048256 sda5
8 6 2827408 sda6
# probepart
/dev/sda1|ext2|20482812
/dev/sda2|ext2|20482874
/dev/sda3|none|2
/dev/sda5|swap|4096512
/dev/sda6|ext2|5654816
/dev/hdc|iso9660|0
# fdisk -l

Disk /dev/sda: 98.5 GB, 98522403840 bytes
255 heads, 63 sectors/track, 11978 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 1 1275 10241406 83 Linux
/dev/sda2 1276 2550 10241437+ 83 Linux
/dev/sda3 11372 11978 4875727+ 5 Extended
/dev/sda5 11372 11626 2048256 82 Linux swap / Solaris
/dev/sda6 11627 11978 2827408+ 83 Linux
#
# puppyinstaller
sda "ATA FUJITSU MHV2100B, size 98.5 GB"
sda
sda1: ext2, size 9.767 GB, Puppy version 217 installed
sda2: ext2, size 9.767 GB
sda6: ext2, size 2.696 GB, Puppy version 217 installed

#
The partitions sda1 and sda2 were created afresh using gparted prior to running the install and I selected sda1 and a frugal install. The sda6 partition has a 2.17 install and used to work but doesn't now! I cannot now remember whether it's Frugal or HD.

While GRUB doesn't boot up, if I boot from the CD without any parameters then a save file is detected, but I'm not sure which.

The menu.lst looks like this.

# GRUB configuration file '/boot/grub/menu.lst'.
# generated by 'grubconfig'. Fri Jul 27 21:46:05 2007
#
# The backup copy of the MBR for drive '/dev/sda' is
# here '/boot/grub/mbr.sda.12021'. You can restore it like this.
# dd if=/boot/grub/mbr.sda.12021 of=/dev/sda bs=512 count=1
#
# Start GRUB global section
#timeout 30
color light-gray/blue black/light-gray
# End GRUB global section
# Linux bootable partition config begins
title Linux (on /dev/sda1)
root (hd0,0)
kernel /boot/vmlinuz root=/dev/sda1 ro vga=normal
# Linux bootable partition config ends
# Linux bootable partition config begins
title Linux (on /dev/sda2)
root (hd0,1)
kernel /boot/vmlinuz root=/dev/sda2 ro vga=normal
# Linux bootable partition config ends
# Linux bootable partition config begins
title Linux (on /dev/sda6)
root (hd0,5)
kernel /boot/vmlinuz root=/dev/sda6 ro vga=normal
# Linux bootable partition config ends
title Install GRUB to floppy disk (on /dev/fd0)
pause Insert a formatted floppy disk and press enter.
root (hd0,0)
setup (fd0)
pause Press enter to continue.
title Install GRUB to Linux partition (on /dev/sda1)
root (hd0,0)
setup (hd0,0)
pause Press enter to continue.
title - For help press 'c', then type: 'help'
root (hd0)
title - For usage examples, type: 'cat /boot/grub/usage.txt'
root (hd0)
Barry; I realise that this isn't exactly the same issue, but I have put it here in case it's relevant and/or helpful.

Please ignore this post if it's not and I'll raise it in a more general problems forum.

Thanks for all you do!

Posted: Sat 28 Jul 2007, 00:51
by BarryK
I then instal co-exit puppy on hda1, and then instal GRUB on MBR.
hda1,2,3,6 shows in P.U.I. HDA1 IS NOT GONE.

I don't know what installing grub to the superblock of a partition
changes, but it makes the partition disappear in P.U.I. on my computer.

Hope you can use this.
Jorgen.
Jorgen has posted this, which is extremely interesting. For everyone else who has a "missing" partition in the Uni Installer, where is your GRUB installed? -- is it on the MBR or a partition?

This would account for why I don't get this problem, as I always install GRUB to the MBR.

Feedback for partitions not found

Posted: Sat 28 Jul 2007, 01:47
by RazzBear
I have run the tests you have requested and here are the results i got

cat /proc/partitions
major minor #blocks name
7 0 64108 loop0
3 0 78150744 hda
3 1 61440561 hda1
3 2 10241437 hda2
3 3 6466162 hda3

probepart
/dev/hda1|ntfs|122881122
/dev/hda2|ext3|20482874
/dev/hda3|ext2|12932324
/dev/hdc|iso9660|0


fdisk -l
Disk /dev/hda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hda1 * 1 7649 61440561 7 HPFS/NTFS
/dev/hda2 7650 8924 10241437+ 83 Linux
/dev/hda3 8925 9729 6466162+ 83 Linux

Universal installer only recognises hda1
Have attached pic to show you

follow-up 2

Posted: Sat 28 Jul 2007, 01:52
by RazzBear
Sorry about the big picture in my previous post

I have grub intalled on linux partitions (not on MBR)
and using windows bootloader on /dev/hda1 to bring up a boot selection menu

Posted: Sat 28 Jul 2007, 02:52
by Bruce B
Yes Barry, I'd say there is a problem as you described.
# probepart
/dev/hda1|ext2|78124032
/dev/hda2|ext2|58589054
/dev/hda3|ext2|58589054
/dev/hda4|none|2
/dev/hda5|ext2|58588992
/dev/hda6|ext3|58588992
/dev/hda7|ext2|174803202
/dev/hda8|swap|1108422
/dev/hdc1|ext2|156296322
/dev/hdc2|ext2|156280320
/dev/sda1|vfat|3893910
/dev/sr0|iso9660|0
/dev/hdb|iso9660|0
# mount
/dev/root on /initrd type ext2 (rw)
tmpfs on /initrd/mnt/tmpfs type tmpfs (rw)
/dev/loop0 on /initrd/pup_ro2 type squashfs (ro,noatime)
tmpfs on /initrd/pup_rw type tmpfs (rw)
unionfs on / type aufs (rw,xino=/initrd/pup_rw/.aufs.xino,diropq=w,dirs=/initrd/pup_rw=rw:/initrd/pup_ro2=ro)
none on /proc type proc (rw)
none on /dev/pts type devpts (rw)
none on /sys type sysfs (rw)
none on /proc/bus/usb type usbfs (rw)
Puppy booted with puppy pfix=nox,ram argument, then xwin run to setup the GUI

The universal installer doesn't give an option to install on /dev/hda1

Re: follow-up 2

Posted: Sat 28 Jul 2007, 02:58
by Bruce B
RazzBear wrote:Sorry about the big picture in my previous post

I have grub intalled on linux partitions (not on MBR)
and using windows bootloader on /dev/hda1 to bring up a boot selection menu
Forgive my bluntness, but why apologize and then leave the big picture?

Posted: Sat 28 Jul 2007, 03:10
by Greystar
I choose MBR to install grub .

Posted: Sat 28 Jul 2007, 08:31
by RazzBear
I posted picture first then apologised in my next post
after seeing how big it was

"Sorry about the big picture in my previous post "

Maybe i could have resized or cropped just the relevant part,
is what the apology is for

2.17 Universal Installer feedback needed

Posted: Sat 28 Jul 2007, 09:48
by Guest07
Grup in MBR. Did a Grup reinstal in MBR - no difference.
So somewhere in the update of the 1500+ lines puppyinstaller-script is a secret hiding. Could be around the 'find' command or ext2/3 where something is altered.

Posted: Sat 28 Jul 2007, 10:16
by Sage
There is a method of resetting these fora so that they display, even in 640x480. Apparently our two moderators haven't learned about this trick. Line overflow is really irksome. I'm sure that the board or php have some advice somewhere on how to do it? Moderators should always defer to the L.C.D. to allow for young folks with old kit, old folks with poor eyesight and poor folks who can't afford 100" lcd monitors with outrageous resolutions.

Posted: Sat 28 Jul 2007, 11:56
by Joe_DK
I can add, to my posts before, that if I install grub to the superblock of the partition, which makes the partition disappear in universal installer.
Then a re-install of grub to mbr, won't make it appear again. only a delete and create of partition and then install to mbr, will work.
Well, thats on my system!

Can anyone confirm this?

Guest07:
Have you installed grub to superblock of the missing partition at any time?

Jorgen.

Posted: Sat 28 Jul 2007, 13:50
by BarryK
I'll post another puppyinstaller script to test very soon.

There is a lot of clever code in there connected with GRUB detection, and maybe that has got something to do with it. I'm not familiar enough with it to locate the problem, especially since I can't reproduce the bug and I'm forced to just work through the code theoretically.

Anyway, will post something very soon.

Posted: Sat 28 Jul 2007, 13:58
by BarryK
Well, this is not ready to be used, but could you guys just start it up and tell me if it shows all your partitions? Attached.

2.17 Universal Installer feedback needed

Posted: Sat 28 Jul 2007, 16:35
by Guest07
SUCCESS - thanks Barry !
Now its there again. Did an upgrade of the full install on hda2 - writing from there. javascript:emoticon(':roll:')

Posted: Sat 28 Jul 2007, 16:56
by Bruce B
RazzBear wrote:I posted picture first then apologised in my next post
after seeing how big it was

"Sorry about the big picture in my previous post "

Maybe i could have resized or cropped just the relevant part,
is what the apology is for
I get it. You thought it was too late to remove, crop or resize after it was posted. It wasn't and probably still isn't.

Posted: Sat 28 Jul 2007, 17:44
by Bruce B
Barry, puppyinstaller-bk1.gz worked for me also. It now shows /dev/hda1, wereas the default installer didn't.

Posted: Sat 28 Jul 2007, 18:20
by Sit Heel Speak
All existing disks/partitions are seen here.

I just tried 2.17, nolzma version downloaded from a mirror other than ibiblio, with a good md5sum starting with 2d0. Installing to a 1.6GB hard disk, cabled as secondary master.

If the disk has a single existing vfat partition, formatted vfat but with nothing on it, then Puppy Universal Installer (PUI) will put a frugal install on it, automatically.

If the disk has no partitions (i.e. I just used GPartEd to erase the vfat partition, but didn't then put a new partition on), then PUI does not offer any install. This is potentially confusing to a new user, since it still offers (only) the superfloppy install, and I can foresee woe down that path. You have to fdisk the disk first, using GPartEd, whose default setting is ext2. Ext3 and reiserfs are also offered.

If you at this point go away from PUI and call up GPartEd from the menu, and tell GPartEd to fdisk the particular disk partition to ext2, ext3, or reiserfs, then PUI installs to it just fine. You can choose either a frugal (co-exist) install or a full install. There is a danger to new users here, since the desired disk is not automatically selected by GPartEd.

It might be wise if GPartEd is automatically started, after an initial advisement prompt, and if the option is somehow advised of or prompted for, before GPartEd is started, which disk to install to. Also, it would be nice if PUI offers to put a 256MB swap partition on the disk if none already exists on the system.

Since I have a pre-exising GRUB install, I told PUI to quit when it offered to install GRUB; I then modified my existing GRUB config file (menu.lst) to boot from the newly-created install.

Works just fine, no matter whether the underlying partition is ext2, ext3, or reiserfs.

Upon first boot to the new disk-install, the heavy-encrypted pup_save file I created works just fine (however, I have recently seen it stated on the Gentoo forum that aes is now trivially easy to break).

Auto-version-update did not find any of the other pup_saves I have on other hard disks in this system (for earlier Puppy versions), which is good.

I notice the 2.17 bootup script is creating a Linux swap file, regardless of the fact I never told it to.

After creating the hard disk full install using PUI from the live CD, the CD (well, in my case, DVD actually) would not eject using the DVD-writer's front panel eject button. Had to choose Menu-Shutdown-Reboot and then push the DVD-writer's eject button in between Puppy shutdown and the initial BIOS splash screen of the next boot, in order to get the DVD to eject so as to boot from hard disk. I guess this means that it is not possible to play a DVD or access a data CD from the initial live-CD boot of 2.17.

The "Do you want to encrypt the pup_save.2fs file?" question talks about "to void the overhead." That should be "to avoid the overhead." Grammatical neatness counts.

BTW, when I GPartEd'd this disk, I forgot to format it after I fdisk'ed it. All three times with the three filesystems ext2, ext3 and reiserfs. Didn't matter, Puppy installed and ran just fine. I presume, then, that GPartEd automatically formats the partition if I forget to?

Posted: Sat 28 Jul 2007, 18:51
by Joe_DK
Seems you have solved it, I can see all partitions now!
Jorgen.

Posted: Sat 28 Jul 2007, 20:14
by Sage
That CD retention matter can be a nuisance. Klaus introduced the auto-tray-open-before-shutdown-with-message right at the beginning of liveCD s. Has a touch of class about it! Several distros have adopted it. Not sure what the overheads are, though?