• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Dell OptiPlex 790 in loop

    Scheduled Pinned Locked Moved
    General
    5
    17
    8.4k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • B
      BryceZ
      last edited by

      Peter, you probably want to look into [URL=‘http://www.fogproject.org/wiki/index.php?title=Boot_looping_and_Chainloading’]chainloading[/URL].

      1 Reply Last reply Reply Quote 0
      • P
        Peter Nowak
        last edited by

        Many thanks for all replies! Great to see that this forrum is so active! I’ll look into updating to the latest kernel first as suggested and see how I get on, thakns again everyone!

        1 Reply Last reply Reply Quote 0
        • D
          Derek Boyer
          last edited by

          I had to use the chainloading artice that BryceZ posted a link to for that model to work. I was getting the infinite booting loop as well

          1 Reply Last reply Reply Quote 0
          • P
            Peter Nowak
            last edited by

            [quote=“BryceZ, post: 2452, member: 2”]Peter, you probably want to look into [URL=‘http://www.fogproject.org/wiki/index.php?title=Boot_looping_and_Chainloading’]chainloading[/URL].[/quote]

            Hi BryceZ,

            First of all thanks for your suggestion and sorry for the loong delay in doing this! Reading some other post seem to indicate that this really is a good solution, I’ve tried to do this now and had some problems. I’m a total noob at linux CLI so I’m sure I’ve buggered something up, here is what I did using the CLI:

            [COLOR=#1f497d][SIZE=3][FONT=Calibri][root@frfrg001 ~]# cp /tftpboot/pxelinux.0 /tftpboot/pxelinux.0_20120515[/FONT][/SIZE][/COLOR]
            [COLOR=#1f497d][SIZE=3][FONT=Calibri][root@frfrg001 ~]# cp /tftpboot/vesamenu.c32 /tftpboot/vesamenu.c32_20120515[/FONT][/SIZE][/COLOR]
            [COLOR=#1f497d][SIZE=3][FONT=Calibri][root@frfrg001 ~]# vi /tftpboot/pxelinux.cfg/default[/FONT][/SIZE][/COLOR]
            [COLOR=#1f497d][SIZE=3][FONT=Calibri][root@frfrg001 scratch]# cd /scratch[/FONT][/SIZE][/COLOR]
            [COLOR=#1f497d][SIZE=3][FONT=Calibri][root@frfrg001 scratch]# ll[/FONT][/SIZE][/COLOR]
            [COLOR=#1f497d][SIZE=3][FONT=Calibri]total 224[/FONT][/SIZE][/COLOR]
            [COLOR=#1f497d][SIZE=3][FONT=Calibri]-rwx------ 1 jhnowaki rme 20704 May 15 16:41 chain.c32[/FONT][/SIZE][/COLOR]
            [COLOR=#1f497d][SIZE=3][FONT=Calibri]-rwx------ 1 jhnowaki rme 26460 May 15 16:41 pxelinux.0[/FONT][/SIZE][/COLOR]
            [COLOR=#1f497d][SIZE=3][FONT=Calibri]-rwx------ 1 jhnowaki rme 155792 May 15 16:41 vesamenu.c32[/FONT][/SIZE][/COLOR]
            [COLOR=#1f497d][SIZE=3][FONT=Calibri][root@frfrg001 scratch]# cp ./* /tftpboot[/FONT][/SIZE][/COLOR]
            [COLOR=#1f497d][SIZE=3][FONT=Calibri]cp: overwrite /tftpboot/pxelinux.0'? y[/FONT][/SIZE][/COLOR] [COLOR=#1f497d][SIZE=3][FONT=Calibri]cp: overwrite /tftpboot/vesamenu.c32’? y[/FONT][/SIZE][/COLOR]
            [COLOR=#1f497d][SIZE=3][FONT=Calibri][root@frfrg001 scratch]#[/FONT][/SIZE][/COLOR]

            As I am using the text based menu (I think?) I [COLOR=#000000]modified [/COLOR][FONT=Calibri][COLOR=#1f497d][COLOR=#000000]the first line of [FONT=Calibri]/tftpboot/pxelinux.cfg/default from [/FONT][/COLOR]“[/COLOR][/FONT][FONT=Courier New][COLOR=#000000]DEFAULT vesanebu.c32[/COLOR][/FONT][FONT=Calibri][COLOR=#1f497d]” -> “[/COLOR][/FONT][FONT=Courier New][COLOR=#000000]DEFAULT fog.next[/COLOR][/FONT][FONT=Calibri][COLOR=#1f497d]” [COLOR=#000000]and added the rest of the text.[/COLOR][/COLOR][/FONT]
            And what I’m getting now when trying to boot ANY PC into FOG is this:

            [COLOR=#1f497d][SIZE=3][FONT=Calibri]Missing parameter in configuration file. Keyword: \n[/FONT][/SIZE][/COLOR]
            [COLOR=#1f497d][SIZE=3][FONT=Calibri]Missing parameter in configuration file. Keyword: \n[/FONT][/SIZE][/COLOR]
            [COLOR=#1f497d][SIZE=3][FONT=Calibri]Missing parameter in configuration file. Keyword: \n[/FONT][/SIZE][/COLOR]
            [COLOR=#1f497d][SIZE=3][FONT=Calibri]Missing parameter in configuration file. Keyword: \n[/FONT][/SIZE][/COLOR]
            [COLOR=#1f497d][SIZE=3][FONT=Calibri]Missing parameter in configuration file. Keyword: \n[/FONT][/SIZE][/COLOR]

            [COLOR=#1f497d][SIZE=3][FONT=Calibri]Could not find kernel image: chain.c32[/FONT][/SIZE][/COLOR]
            [COLOR=#1f497d][SIZE=3][FONT=Calibri]Boot: [/FONT][/SIZE][/COLOR]
            [COLOR=#1f497d][SIZE=3][FONT=Calibri]Could not find kernel image: chain.c32[/FONT][/SIZE][/COLOR]
            [COLOR=#1f497d][SIZE=3][FONT=Calibri]Boot: [/FONT][/SIZE][/COLOR]
            [COLOR=#1f497d][SIZE=3][FONT=Calibri]Could not find kernel image: chain.c32[/FONT][/SIZE][/COLOR]
            [COLOR=#1f497d][SIZE=3][FONT=Calibri]Boot: [/FONT][/SIZE][/COLOR]
            [COLOR=#1f497d][SIZE=3][FONT=Calibri]Could not find kernel image: chain.c32[/FONT][/SIZE][/COLOR]
            [COLOR=#1f497d][SIZE=3][FONT=Calibri]Boot: [/FONT][/SIZE][/COLOR]
            [COLOR=#1f497d][SIZE=3][FONT=Calibri]Could not find kernel image: chain.c32[/FONT][/SIZE][/COLOR]
            [FONT=Calibri][COLOR=#1f497d]Boot:[/COLOR][/FONT]

            Any idea what I’ve done wrong? Oh, and I used the v.4.05 SYSLINUX files.

            Many thanks in advance for your help!

            1 Reply Last reply Reply Quote 0
            • B
              BryceZ
              last edited by

              Off the top of my head I’d say it’s a permissions issue. It looks like you’re only giving access to the owner (in this case jhnowaki), which may not match the read access needed for TFTP… try chmod 644 on chain.c32 pxelinux.0 and vesamenu.c32, just to make sure it’s not a read issue.

              1 Reply Last reply Reply Quote 0
              • P
                Peter Nowak
                last edited by

                [quote=“BryceZ, post: 3506, member: 2”]Off the top of my head I’d say it’s a permissions issue. It looks like you’re only giving access to the owner (in this case jhnowaki), which may not match the read access needed for TFTP… try chmod 644 on chain.c32 pxelinux.0 and vesamenu.c32, just to make sure it’s not a read issue.[/quote]

                Thanks BryceZ, just another quick (probably stupid) question, what is the difference between the “text menu” or the “graphical menu” as I’m starting to doubt which one I’m using…

                When successfully loaded, I see a graphical “FOG logo” and underneith, I see all the options in the menu which I can highlight using the arrow keys (enter selects) and it all looks “text based” but am I perhaps using “Graphical menus” ?

                1 Reply Last reply Reply Quote 0
                • B
                  BryceZ
                  last edited by

                  This is the default graphical menu:
                  [IMG]https://carmenwiki.osu.edu/download/attachments/26522106/Screenshot_01.png?version=2&modificationDate=1302028112087[/IMG]

                  1 Reply Last reply Reply Quote 0
                  • P
                    Peter Nowak
                    last edited by

                    [quote=“BryceZ, post: 3509, member: 2”]This is the default graphical menu:
                    [IMG]https://carmenwiki.osu.edu/download/attachments/26522106/Screenshot_01.png?version=2&modificationDate=1302028112087[/IMG][/quote]Thanks again, I can’t seem to see the image, I am logged in using IE9 but the image is just a “X [IMG]”
                    is there another way you could send me this image like directly PM or similar or perhaps a link to someone showing how the graphical menu looks?

                    Thanks, again![/IMG]

                    1 Reply Last reply Reply Quote 0
                    • B
                      BryceZ
                      last edited by

                      Of course it doesn’t work, because I wasn’t thinking and linked to an image on a secured site. I’ve attached a copy of the image to this post.

                      [url=“/_imported_xf_attachments/0/116_Screenshot_01.png?:”]Screenshot_01.png[/url]

                      1 Reply Last reply Reply Quote 0
                      • P
                        Peter Nowak
                        last edited by

                        [quote=“BryceZ, post: 3514, member: 2”]Of course it doesn’t work, because I wasn’t thinking and linked to an image on a secured site. I’ve attached a copy of the image to this post.[/quote]Much better! Great stuff, now I think I know where I’m going wrong, I am in fact using the “Graphical menu” so I have edited the wrong file! I’ll get try to change this again tomorrow, many thanks again!

                        1 Reply Last reply Reply Quote 0
                        • P
                          Peter Nowak
                          last edited by

                          [quote=“BryceZ, post: 3514, member: 2”]Of course it doesn’t work, because I wasn’t thinking and linked to an image on a secured site. I’ve attached a copy of the image to this post.[/quote]Right, getting closer now (I think)
                          Having gone back to the original [FONT=Courier New]/tftpboot/pxelinux.cfg/default[/FONT] as I wrongly edited it. I now edited fog.local in /tftpboot/pxelinux.cfg/default instead to look like:

                          LABEL fog.local
                          kernel chain.c32
                          append hd0
                          MENU DEFAULT
                          MENU LABEL Boot from hard disk
                          TEXT HELP
                          Boot from the local hard drive.
                          If you are unsure, select this option.
                          ENDTEXT
                          and now at least I am getting to the default menu again (looks exactly like the one in the pic. you attached)

                          The first line (Boot from local drive) is highlighted and after the timer (3s) expires, the screen just flickers once and I back to the same screen and the timer is restarted again to 3s and it just loops like that forever. So there is definately some change as the D790 no longer restarts but unfortunately I can’t seem to get it to boot of the HD at all. Not even if I press enter when the first line (boot from local drive) is highlighted, again, the screen just flickers and I’m back to the default menu.

                          Should I perhaps try v.4.04 of those 3 SYSLINUX files insted of v.4.05 which I currently downloaded?

                          All the other menu lines do work, I can get system information etc. but after the reboot I find myself in the main menu again and I can’t get it to boot of the HD…

                          1 Reply Last reply Reply Quote 0
                          • B
                            BryceZ
                            last edited by

                            SYSLINUX 4.05 did make some adjustments to chain.c32, so it is possible that a bug was introduced, and using 4.04 might help. Another thing to check; what happens when you don’t PXE boot? Does it boot normally to the hard drive? Also, append hd0 tries to load the first disk drive detected by SYSLINUX, so is it possible that it’s seeing another non-bootable drive on this system?

                            1 Reply Last reply Reply Quote 0
                            • P
                              Peter Nowak
                              last edited by

                              Ah, good suggestions, I’ll have a look at this. Again many thanks. If the D790 is not set to boot from Network with PXE as first choice, then it successfully boots from HD as first choice.

                              But I will double check the HD0 as you may very well be right in that perhaps the HD is not connected to “port0” I’ll have to check that.

                              Cheers again BryceZ, you advice and suggestions are very appreciated

                              1 Reply Last reply Reply Quote 0
                              • P
                                Peter Nowak
                                last edited by

                                Hi Bryce,

                                thanks for your help and assistance! It’s now working, the problem it would seem was permissions to the chain.c32 file and the pxelinux.0 file, all wokring now!

                                Cheers!

                                1 Reply Last reply Reply Quote 0
                                • 1 / 1
                                • First post
                                  Last post

                                176

                                Online

                                11.6k

                                Users

                                17.1k

                                Topics

                                154.6k

                                Posts
                                Copyright © 2012-2024 FOG Project