[SOLVED] - mylivecd installed to harddrive has extended boot time

[macemm]

Here's all the things I did to the hard drive partitioning layout before installing my latest mylivecd to the hard drive.

Code: [Select]

[hugh@renny ~]$ blkid
/dev/sda5: LABEL="swap4000" UUID="c6aadcc0-85f0-4e4c-9aab-2ac443402f01" TYPE="swap"
/dev/sda1: SEC_TYPE="msdos" LABEL="DellUtility" UUID="07DA-091B" TYPE="vfat"
/dev/sda2: LABEL="RECOVERY" UUID="92DC677ADC67578D" TYPE="ntfs"
/dev/sda3: LABEL="OS" UUID="28206A162069EAF0" TYPE="ntfs"
/dev/sda6: LABEL="mylivecd" UUID="98379e73-a54c-4845-a760-3aef23505070" TYPE="ext4"
/dev/sda7: UUID="06e73607-b4ba-4880-a258-0490933f6dd8" TYPE="ext4" LABEL="mylivesu"
/dev/sda8: UUID="2a066d25-13c4-41bf-8ba7-e7dca7c812ac" TYPE="ext4"
/dev/sda9: UUID="6b776499-2558-4fb0-98a3-b069ab6b8f59" TYPE="ext4"
/dev/sdb1: LABEL="usb-primus" UUID="10991830680120AB" TYPE="ntfs"

and from fdisk as root

Code: [Select]

[root@renny ~]# fdisk -l

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x18000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1              63      160649       80293+   6  FAT16
/dev/sda2   *      161792    24160255    11999232    7  HPFS/NTFS
/dev/sda3        24160256  1003112447   489476096    7  HPFS/NTFS
/dev/sda4      1003116492  1250146169   123514839    5  Extended
/dev/sda5      1003116544  1011308543     4096000   82  Linux swap / Solaris
/dev/sda6      1011310592  1114355711    51522560   83  Linux
/dev/sda7      1114357760  1217400831    51521536   83  Linux
/dev/sda8      1217405763  1233775934     8185086   83  Linux
/dev/sda9      1233775998  1250146169     8185086   83  Linux

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xa7d43d72

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *          63   972857343   486428640+   7  HPFS/NTFS
sda5 (swap) and sda6 (/) comprised the original install before being deleted after creating mylivecd.

New layout
swap at sda5 increased in size
sda6 is /home
sda7 is /

sda8 and sda9 are new and contain test3-pclinuxos-20011.6.ISO

I boot test3 from an entry in mylivecd boot/grub/menu.lst - boot is fast and fine.
Grub is installed in the mbr of /dev/sdb an external usb drive thus maintaining the integrity of the Windows installation on dev/sda

Boot time for mylivecd has increased by 40 seconds. I modifed splash=silent in sda7/boot/grub/menu.lst to splash=verbose and rebooted.

The 40 second delay is caused by the cursor sitting at this message:

cannot open file delete

After the 40 second delay boot continues normally.

Don't know what the cannot open file delete message means.

Be pleased to hear from anyone that does,

Hugh
edited for spelling

[AS]

Boot time for mylivecd has increased by 40 seconds. I modifed splash=silent in sda7/boot/grub/menu.lst to splash=verbose and rebooted.

when you want verbose mode, be sure to remove also the quiet option.

AS

[macemm]

when you want verbose mode, be sure to remove also the quiet option.

AS

Well, AS, that got rid of the cannot open file delete message. Now I have got more to read while waiting for the 40 seconds to pass!!

So, you've seen this cannot open file delete before?

Hugh

[AS]

when you want verbose mode, be sure to remove also the quiet option.

AS

Well, AS, that got rid of the cannot open file delete message. Now I have got more to read while waiting for the 40 seconds to pass!!

So, you've seen this cannot open file delete before?

Hugh

yes, i have seen it on one my machine, but doesn't cause any delay. The quiet option suppress some output, that's the reason I suggested to remove the option, was thinking at something else actually hidden....

Other times had seen reports about delay due to "waiting for /dev/sdaN to appear ... timeout in 1 minute" don't know if it's your issue....

[marcin82]

"waiting for /dev/sdaN to appear ... timeout in 1 minute" don't know if it's your issue....

Maybe that is the problem ...

macemm
Check out if real UUIDs are the same in the:

Code: [Select]

/wherever/boot/grub/menu.lstShow file menu.lst and content of proper /boot directory:

Code: [Select]

ls -l /path/to/the/bootShow also kernel version are you using:

Code: [Select]

uname -r

[macemm]

Code: [Select]

yes, i have seen it on one my machine, but doesn't cause any delay. The quiet option suppress some output, that's the reason I suggested to remove the option, was thinking at something else actually hidden....

Other times had seen reports about delay due to "waiting for /dev/sdaN to appear ... timeout in 1 minute" don't know if it's your issue....

AS, I have a waiting for sda7 to appear message.

marcin82

If you mean does my sda7 uuid in menu.lst match output of blkid then the answer is yes.

Code: [Select]

[hugh@renny ~]$ uname -r
2.6.38.8-pclos1.pae.bfs


Code: [Select]

timeout 30
color black/cyan yellow/cyan
gfxmenu (hd1,6)/boot/gfxmenu
default 3

title mylivecd
kernel (hd1,6)/boot/vmlinuz BOOT_IMAGE=mylivecd root=UUID=06e73607-b4ba-4880-a258-0490933f6dd8 nokmsboot vmalloc=256M acpi=on resume=LABEL=swap4000 splash=verbose vga=788
initrd (hd1,6)/boot/initrd.img

title linux-nonfb
kernel (hd1,6)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=06e73607-b4ba-4880-a258-0490933f6dd8 quiet nokmsboot vmalloc=256M acpi=on resume=UUID=0782b8df-b7fe-40c2-8749-7470ad731b26
initrd (hd1,6)/boot/initrd.img

title failsafe
kernel (hd1,6)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=06e73607-b4ba-4880-a258-0490933f6dd8 quiet nokmsboot failsafe vmalloc=256M acpi=on
initrd (hd1,6)/boot/initrd.img

title windows-7-professional
root (hd1,1)
chainloader +1

title test3-pclinuxos
kernel (hd1,8)/boot/vmlinuz BOOT_IMAGE=test3-pclinuxos root=UUID=6b776499-2558-4fb0-98a3-b069ab6b8f59  quiet nokmsboot vmalloc=256M acpi=on resume=UUID=c6aadcc0-85f0-4e4c-9aab-2ac443402f01 splash=silent vga=788
initrd (hd1,8)/boot/initrd.img


Code: [Select]

[hugh@renny ~]$ ls -l /boot/
total 10016
-rw-rw-r-- 1 root root     440 Apr  6  2010 boot.backup.sda
-rw-rw-r-- 1 root root     440 Jun 24 13:07 boot.backup.sdb
-rw-rw-r-- 1 root root     440 May 29 20:47 boot.backup.sdc
lrwxrwxrwx 1 root root      30 Jun 25 13:33 config -> config-2.6.38.8-pclos1.pae.bfs
-rw-r--r-- 1 root root  126224 Jun  4 08:52 config-2.6.38.8-pclos1.pae.bfs
-rwxr-xr-x 1 root root  517632 Jun 24 10:41 gfxmenu*
drwxr-xr-x 2 root root    4096 Jun 25 13:31 grub/
-rw------- 1 root root 5227662 Jun 24 10:41 initrd-2.6.38.8-pclos1.pae.bfs.img
lrwxrwxrwx 1 root root      34 Jun  8 17:29 initrd.img -> initrd-2.6.38.8-pclos1.pae.bfs.img
lrwxrwxrwx 1 root root      38 Jun 25 13:33 kernel.h -> /boot/kernel.h-2.6.38.8-pclos1.pae.bfs
-rw-r--r-- 1 root root    1493 Jun 25 13:33 kernel.h-2.6.38.8-pclos1.pae.bfs
-rw-r--r-- 1 root root  164504 May 18 05:03 memtest-4.20
-rw-r--r-- 1 root root  254766 Nov  6  2006 message-graphic
lrwxrwxrwx 1 root root      34 Jun  8 17:32 System.map -> System.map-2.6.38.8-pclos1.pae.bfs
-rw-r--r-- 1 root root 1563805 Jun  4 08:52 System.map-2.6.38.8-pclos1.pae.bfs
-rw-rw-r-- 1 root root     256 Jun 24 10:41 uk-latin1.klt
-rw-rw-r-- 1 root root     256 Apr  6  2010 us.klt
lrwxrwxrwx 1 root root      31 Jun  8 17:29 vmlinuz -> vmlinuz-2.6.38.8-pclos1.pae.bfs
-rw-r--r-- 1 root root 2358000 Jun  4 08:52 vmlinuz-2.6.38.8-pclos1.pae.bfs

Hugh

[marcin82]

If you mean does my sda7 uuid in menu.lst match output of blkid then the answer is yes.

Yes, but file (my for example) initrd-2.6.38.8-pclos1.bfs.img uses old UUID for this partition (/dev/sda7?). If you want, you can try to create new initrd ... to get rid of this "waiting".

[macemm]

Yes, but file initrd-2.6.38.8-pclos1.bfs.img uses old UUID for this partition (/dev/sda7?). If you want, you can try to create new initrd ... to get rid of this "waiting".

Sure, I would like to try to create new initrd.

Would you mind telling me how you know the file initrd-2.6.38.8-pclos1.bfs.img uses the old UUID?

Thanks,

Hugh

[marcin82]

Would you mind telling me how you know the file initrd-2.6.38.8-pclos1.bfs.img uses the old UUID?

Cause I had the same problem. It was caused by my changes in partition table (formatting, moving) and these operations was reason of UUIDs have been changed. Someday I wrote about this at polish forum:
http://forum.pclinuxos.org.pl/viewtopic.php?f=8&t=2909&p=18806#p18811 .
=============
Ok, move file initrd-2.6.38.8-pclos1.pae.bfs.img to safe place eg. your /home partition, then type in a terminal:

Code: [Select]

mkinitrd /boot/initrd-2.6.38.8-pclos1.pae.bfs.img 2.6.38.8-pclos1.pae.bfs

[macemm]

Cause I had the same problem. It was caused by my changes in partition table (formatting, moving) and these operations was reason of UUID changes. Someday I wrote about this at polish forum:
http://forum.pclinuxos.org.pl/viewtopic.php?f=8&t=2909&p=18806#p18811 .
=============
Ok, move file initrd-2.6.38.8-pclos1.pae.bfs.img to safe place eg. your /home partition, then type in a terminal:

Code: [Select]

mkinitrd /boot/initrd-2.6.38.8-pclos1.pae.bfs.img 2.6.38.8-pclos1.pae.bfs

Hi again. I had to leave for a message.

I have moved the .img to my home folder (safe as anywhere)
I have run the mkinitrd command. There were no error messages.

Do I need to do anything else? edit files? reboot to see if it works?

Thanks,

Hugh

[marcin82]

Run reboot, if it doesn't work, move previous file *.img to his previous location using live-cd, and will be OK. Give feedback if "time to appear" is still appearing
=============
EDIT: You're welcome! ;]

[macemm]

Run reboot, if it doesn't work, move previous file *.img to his previous location using live-cd, and will be OK. Give feedback if "time to appear" is still appearing

Hi,

I am back.
It works.
Delay has gone.

Thank you for your time and patience.

Hugh

[zorlac]

I just tried the above instructions on a fresh XFCE install and still have the "cannot open file delete" delay on booting up.
It boots OK after the pregnant pause so I guess I'll just have to learn to live with it.

[AS]

I just tried the above instructions on a fresh XFCE install and still have the "cannot open file delete" delay on booting up.
It boots OK after the pregnant pause so I guess I'll just have to learn to live with it.

zorlac,

the two things (message and delay) are unrelated. You can safely ignore the message, to get rid of the delay (if any) probably you need to rebuild the initrd image: (substitute the kernel version with the version currently installed on your system, you can get the version using the command uname -r )

mkinitrd   -f   /boot/initrd-2.6.38.8-pclos3.bfs.img      2.6.38.8-pclos3.bfs

Do not confuse the "silent screen" with a "delay". 
http://www.pclinuxos.com/forum/index.php/topic,93245.msg783071.html#msg783071

AS

[zorlac]

Thanks AS,

mkinitrd didn't really do anything but changing from quite to verbose on the boot setup here

verbose vmalloc=256M acpi=on resume=UUID=3434d4d5-fc07-4b05-9818-5cf6a447d4fb

let me see all the wondrous goings on during what I was mistaking for a pause. 

Thanks!