Interrupting the boot process on an aironet 1242AG AP?

Does anyone know if there's a trick to this?
According to the documentation, I'm supposed to be hitting the Esc key when I see the Loading "flash:/[imagename]" ####### ... line, but this doesn't seem to be working.  I've tried hitting the Esc key a lot during those lines, holding it down, hitting it early, hitting it late, hitting it in the middle, and still no joy.  I'm wanting to hit it with something very heavy and hard about now, but I doubt that'll do anything but cause more problems.  Anyone know what I could be doing wrong here?
I'm trying to break into a handful of malfunctioning 1242AG APs to see if I can get them working, or if they're faulting hardware that's beyond repair.  (So far they're all coming back with: no "IP_ADDR" variable set, so if anyone knows how to set that without breaking out of the boot cycle, that would be helpful too.)

Matt,
Press and hold MODE. Apply power and continue to hold for about 30 sec. The AP will try to find a TFTP server, but after failing, you should have a rommon-like prompt (if I am recalling correctly).
Justin
... typd on tny kybrd.

Similar Messages

  • There is always a blue screen appears after the Apple logo during the booting process. And then everything is back to normal. What is this thing? Is there something wrong with my screen or something?

    There is always a blue screen appears after the Apple logo during the booting process. And then everything is back to normal. What is this thing? Is there something wrong with my screen or something?

    Nah - that's just the normal boot process.
    Clinton

  • My MacBookPro (mid 2012) will not complete the boot process. Yosemite's progress widget gets about 1/3 to 1/2 way across when the logo disappears and the screen goes all white for 10-15 secs or so, then the machine shuts down and restarts.

    My MacBookPro (mid 2012) will not complete the boot process. Yosemite's progress widget gets about 1/3 to 1/2 way across when the logo disappears and the screen goes all white for 10-15 secs, then the machine shuts down and restarts. This sequence will repeat seemingly forever unless I shut it down manually.
    I upgraded to Yosemite from Mountain Lion a couple months ago, skipping Maverick completely, and I've done any associated updates that Apple told me about. I don't recall which version of Yosemite I have, but I'm sure it is the "latest and greatest".
    I've tried re-starting in Safe Mode / Safe Boot and that does the same thing as described above except without the endless restarts. Instead of restarting at some point, SafeBoot proceeds to the white screen and then it hangs until I restart it manually. (I've waited as long os 20-30 minutes with no response).
    When I tried the option-command-p-r key combo I never get any chimes or other noises besides the original 1 time boot sound that you would expect to get when starting up a macbook pro.
    I was using the mac quite normally (meaning I was doing work I normally do on it and there was no indication of anything wrong) immediately prior to this happening.
    The machine is BootCamp(ed) with Windows 8.1 which I use from a VMWare virtual machine instead of natively so that I can have both OSes running at the same time. I also think this is unrelated to my problem. I have been using this setup for more than 2 years.
    My upgrade to Yosemite was uneventful and I thought it went well and was very smooth. I don't want to lead attention away from Yosemite, but at this point my problem does not seem related to the upgrade.
    Any help is appreciated.

    Install or Reinstall OS X from Scratch
    Be sure you backup your files to an external drive or second internal drive because the following procedure will remove everything from the hard drive.
    Boot to the Recovery HD:
    Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
    Erase the hard drive:
      1. Select Disk Utility from the main menu and click on the Continue button.
      2. After DU loads select your startup volume (usually Macintosh HD) from the
          left side list. Click on the Erase tab in the DU main window.
      3. Set the format type to Mac OS Extended (Journaled.) Optionally, click on
          the Security button and set the Zero Data option to one-pass. Click on
          the Erase button and wait until the process has completed.
      4. Quit DU and return to the main menu.
    Reinstall OS X: Select Reinstall OS X and click on the Install button.
    Note: You will need an active Internet connection. I suggest using Ethernet if possible
               because it is three times faster than wireless.

  • Tty1-6 freeze in the middle of the boot process, tty7 and X works fine

    I'm running Arch+KDE (and some alternative like xmonad as wm). I have the following strange problem:
    Booting works fine, KDM starts, I can login, everythings works. However, although I can change to tty1-6 via ctrl+alt+f1...6 they are frozen in the middle of the boot process, here's exactly what I see after switching to another tty:
    [ 2.733866] ata2.00: 78165360 sectors, multi 16: LBA48
    [ 2.747003] ata2.00: configured for UDMA/100
    [ 2.747223] scsi 1:0:0:0: Direct-Access ATA ST340014A 3.06 PQ: 0 ANSI: 5
    [ 2.760075] usb 1-1: new high speed USB device number 2 using ehci_hcd
    [ 2.771843] sd 1:0:0:0: [sda] 78165360 512-byte logical blocks: (40.0 GB/37.2 GiB)
    [ 2.772018] sd 1:0:0:0: [sda] Write Protect is off
    [ 2.772098] sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
    [ 2.772128] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    [ 2.777708] sr0: scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda tray
    [ 2.777797] cdrom: Uniform CD-ROM driver Revision: 3.20
    [ 2.778630] sr 0:0:0:0: Attached scsi CD-ROM sr0
    [ 2.785447] sda: sda1 sda2 sda3 sda4
    [ 2.786061] sd 1:0:0:0: [sda] Attached SCSI disk
    [ 2.885089] hub 1-1:1.0: USB hub found
    [ 2.885518] hub 1-1:1.0: 4 ports detected
    [ 2.993360] usb 1-2: new high speed USB device number 3 using ehci_hcd
    [ 3.236962] usb 1-1.1: new full speed USB device number 5 using ehci_hcd
    [ 3.384005] input: Logitech Logitech USB Headset as /devices/pci0000:00/0000:00:1d.7/usb1/1-1/1-1.1/1-1.1:1.3/input/input1
    [ 3.384294] generic-usb 0003:046D:0A02.0001: input,hidraw0: USB HID v1.00 Device [Logitech Logitech USB Headset] on usb-0000:00:1d.7-1.1/input3
    The next lines which are not shown are (via dmesg)
    [ 3.384294] generic-usb 0003:046D:0A02.0001: input,hidraw0: USB HID v1.00 Device [Logitech Logitech USB Headset] on usb-0000:00:1d.7-1.1/input3
    [ 3.390423] usbcore: registered new interface driver usbhid
    [ 3.390511] usbhid: USB HID core driver
    [ 3.393690] usb 1-1.3: new high speed USB device number 6 using ehci_hcd
    [ 3.424849] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
    [ 3.840034] usb 3-1: new low speed USB device number 2 using uhci_hcd
    [ 4.025136] input: Logitech USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0/input/input2
    [ 4.025381] generic-usb 0003:046D:C050.0002: input,hidraw1: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:1d.1-1/input0
    [ 5.739092] udevd[227]: starting version 171
    [ 6.392169] input: Sleep Button as /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input3
    [ 6.392182] ACPI: Sleep Button [SLPB]
    [ 6.392256] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
    [ 6.392262] ACPI: Power Button [PWRF]
    [ 6.484257] input: PC Speaker as /devices/platform/pcspkr/input/input5
    [ 6.486020] ACPI: acpi_idle registered with cpuidle
    [ 6.567251] Linux agpgart interface v0.103
    [ 6.589560] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
    [ 6.695744] i801_smbus 0000:00:1f.3: PCI INT B -> GSI 17 (level, low) -> IRQ 17
    [ 6.711992] iTCO_vendor_support: vendor-support=0
    [ 6.719428] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.06
    [ 6.720445] iTCO_wdt: Found a ICH5 or ICH5R TCO device (Version=1, TCOBASE=0x0460)
    [ 6.721211] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
    [ 6.722801] parport_pc 00:07: reported by Plug and Play ACPI
    [ 6.722852] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
    [ 6.743621] agpgart-intel 0000:00:00.0: Intel 865 Chipset
    [ 6.743658] agpgart-intel 0000:00:00.0: detected gtt size: 131072K total, 131072K mappable
    [ 6.743755] agpgart-intel 0000:00:00.0: detected 1024K stolen memory
    [ 6.744774] agpgart-intel 0000:00:00.0: AGP aperture is 128M @ 0xa0000000
    [ 6.847264] ppdev: user-space parallel port driver
    [ 6.852667] Intel 82802 RNG detected
    [ 6.878022] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
    [ 6.923869] [drm] Initialized drm 1.1.0 20060810
    [ 7.050148] i915 0000:00:02.0: enabling device (0000 -> 0003)
    [ 7.050160] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    [ 7.050168] i915 0000:00:02.0: setting latency timer to 64
    [ 7.072268] e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
    [ 7.072273] e100: Copyright(c) 1999-2006 Intel Corporation
    [ 7.072344] e100 0000:01:08.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
    [ 7.110870] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
    [ 7.110875] [drm] Driver supports precise vblank timestamp query.
    [ 7.113855] i915 0000:00:02.0: BAR 6: can't assign [??? 0x00000000 flags 0x0] (bogus alignment)
    [ 7.113859] [drm] failed to find VBIOS tables
    [ 7.133720] e100 0000:01:08.0: PME# disabled
    [ 7.140882] [drm] initialized overlay support
    [ 7.141854] e100 0000:01:08.0: eth0: addr 0xfe9df000, irq 20, MAC addr 00:07:e9:4b:a9:8c
    [ 7.178193] [drm] capturing error event; look for more information in /debug/dri/0/i915_error_state
    [ 7.181514] render error detected, EIR: 0x00000010
    [ 7.181514] [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x00000010, masking
    [ 7.181514] render error detected, EIR: 0x00000010
    [ 7.219489] No connectors reported connected with modes
    [ 7.219497] [drm] Cannot find any crtc or sizes - going 1024x768
    [ 7.237564] sr 0:0:0:0: Attached scsi generic sg0 type 5
    [ 7.238588] sd 1:0:0:0: Attached scsi generic sg1 type 0
    [ 7.299180] Console: switching to colour frame buffer device 128x48
    [ 7.347619] fb0: inteldrmfb frame buffer device
    [ 7.347623] drm: registered panic notifier
    [ 7.347832] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
    [ 7.557756] Intel ICH 0000:00:1f.5: PCI INT B -> GSI 17 (level, low) -> IRQ 17
    [ 7.557804] Intel ICH 0000:00:1f.5: setting latency timer to 64
    [ 7.681210] nvidia: module license 'NVIDIA' taints kernel.
    [ 7.681217] Disabling lock debugging due to kernel taint
    [ 7.710730] Linux media interface: v0.10
    [ 7.800616] usbcore: registered new interface driver uas
    [ 7.877282] Linux video capture interface: v2.00
    [ 7.930178] uvcvideo: Found UVC 1.00 device <unnamed> (046d:0802)
    [ 7.972100] input: UVC Camera (046d:0802) as /devices/pci0000:00/0000:00:1d.7/usb1/1-1/1-1.3/1-1.3:1.0/input/input6
    [ 7.972388] usbcore: registered new interface driver uvcvideo
    [ 7.972392] USB Video Class driver (v1.0.0)
    [ 7.990026] intel8x0_measure_ac97_clock: measured 50989 usecs (2457 samples)
    [ 7.990031] intel8x0: clocking to 48000
    [ 8.093410] Initializing USB Mass Storage driver...
    [ 8.100022] scsi4 : usb-storage 1-2:1.0
    [ 8.103449] usbcore: registered new interface driver usb-storage
    [ 8.103453] USB Mass Storage support registered.
    [ 8.401795] usbcore: registered new interface driver snd-usb-audio
    [ 8.568477] nvidia 0000:01:01.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
    [ 8.568494] vgaarb: device changed decodes: PCI:0000:01:01.0,olddecodes=io+mem,decodes=none:owns=io+mem
    [ 8.569407] NVRM: loading NVIDIA UNIX x86 Kernel Module 173.14.30 Thu Apr 14 08:47:14 PDT 2011
    [ 9.104388] scsi 4:0:0:0: Direct-Access WD Ext HDD 1021 2002 PQ: 0 ANSI: 4
    [ 9.104713] sd 4:0:0:0: Attached scsi generic sg2 type 0
    [ 9.105502] sd 4:0:0:0: [sdb] 2930272256 512-byte logical blocks: (1.50 TB/1.36 TiB)
    [ 9.106381] sd 4:0:0:0: [sdb] Test WP failed, assume Write Enabled
    [ 9.106386] sd 4:0:0:0: [sdb] Assuming drive cache: write through
    [ 9.108519] sd 4:0:0:0: [sdb] Test WP failed, assume Write Enabled
    [ 9.108524] sd 4:0:0:0: [sdb] Assuming drive cache: write through
    [ 9.129321] sdb: sdb1 sdb2 sdb3 sdb4
    [ 9.131752] sd 4:0:0:0: [sdb] Test WP failed, assume Write Enabled
    [ 9.131758] sd 4:0:0:0: [sdb] Assuming drive cache: write through
    [ 9.131762] sd 4:0:0:0: [sdb] Attached SCSI disk
    [ 10.662601] EXT4-fs (sda3): re-mounted. Opts: (null)
    [ 11.097052] EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: (null)
    [ 11.412380] Adding 2104508k swap on /dev/sda2. Priority:-1 extents:1 across:2104508k
    [ 14.876829] e100 0000:01:08.0: eth0: NIC Link is Up 100 Mbps Full Duplex
    [ 20.827578] NET: Registered protocol family 10
    [ 31.203380] eth0: no IPv6 routers present
    The curious thing is that everything works perfect in KDE, resp. tty7 ?!?

    what ever upgrade the software downloaded is the problem
    You didn't mention this in your first post. Any idea what it was? Backups?
    Besides that, this may be a fault in the video card, driver, or a screen fault.
    Courtesy of BDAqua (if possible):
    Take a screen shot & view that in Preview, move the Preview window around, if you see double lines it's a Video card/VRAM problem, if the lines do not move moving the pic around then it's the LCD or cable.

  • How to stop the boot process after the GRUB menu?

    Hello there.
    I am getting an error message in the boot process, after the GRUB menu, but I can't read completely the message because it is shown too fast. So, how can I stop the process when I see the error message, for writing down it?
    Thanks in advance.

    zuargo wrote:
    Hello there.
    I am getting an error message in the boot process, after the GRUB menu, but I can't read completely the message because it is shown too fast. So, how can I stop the process when I see the error message, for writing down it?
    Thanks in advance.
    I didn't try this before, but if you use systemd, you may want to try systemd.confirm_spawn to invoke interactive booting process, so you can start the services one by one manually therefore locate the one throwing out error message.
    It is explained in the systemd manual:
    http://www.freedesktop.org/software/sys … stemd.html

  • Set default console font early in the boot process using mkinitrd?

    Hi,
    I'm a Slackware user, and I have a cross-distro question to the Arch gurus here. I like using a custom font (Lat2Terminus16) in the console, on servers. Now I remember having defined this font as default in the Arch console when I gave it a try, and then added it not only to rc.conf, but also to the configuration file that drives the initrd creation. Thus, the console font was defined very early in the boot process.
    Now here's my question: is there any way to achieve this on a stock Linux distribution like Slackware? The man page for mkinitrd and mkinitrd.conf doesn't say anything about custom console fonts. So how do you guys do that?
    Cheers from the sunny South of France.

    Zom wrote:
    We do it by adding 'consolefont' to the HOOKS section in mkinitrd.conf.
    E: Or you could just add the relevant files to the FILES section, if you don't want to use the hook I suppose.
    Yes, but there's no HOOKS and no FILES section in a default Slackware install. My question was more or less to the Arch devs, to know if there was a *generic* (e. g. non-Arch-specific) way to achieve this.

  • Hi, can iMovie give pronlems during the boot process from my iMac Mine. I have often after working with iMovie that i get during the boot Psi SDXH pause so the boot process stops

    hi,
    can iMovie give problems during the boot process from my iMac Mini?
    I have often, after working with iMovie that i get during the boot Psi SDXH pause
    so the boot process stops at this point
    I have often reinstall OSX Mavericks
    regards,
    HenkfromWinterswijk
    Netherlands

    Hello Federico,
    Your EliteBook is a Business model.  Your issue would be best answered on the HP Enterprise Business Community Forum
    Good luck!
    ↙-----------How do I give Kudos?| How do I mark a post as Solved? ----------------↓

  • Is the Magic Mouse useable during the boot process?

    My wired mouse died and I was considering the Magic Mouse as a replacement. Since I often boot to different drives, I need the mouse to be active during the boot process so I can select the drive to use. Anyone know if this will work?

    Strange thing about that... I have the Apple flat aluminum keyboard, but for some strange reason, the cursor keys don't move the cursor when on the boot screen (work fine once the system is booted). The only way I was able to boot up this morning was to borrow a wired Apple mouse from another computer.

  • Interrupt Catalyst boot process

    After entering the command "boot enable-break" in configuration mode ("Enable Break" under "show boot" now shows "yes") the switch will stop loading IOS if you send it a break via the console port while it is loading the IOS.  It will then give the message "Interrupt within 5 seconds to abort boot process."  What key do I hit at this point to interrupt it?  I've tried another break and all the normal Cisco interrupt key sequences but it always continues to boot 5 seconds later.  Relevant portion of boot log follows:
    ...done Initializing Flash.
    Boot Sector Filesystem (bs:) installed, fsid: 3
    Loading "flash:c3550-ipbasek9-mz.122-44.SE6/c3550-ipbasek9-mz.122-44.SE6.bin"...####################################################################################################################################################################################################bad mzip file, unknown zip method
    Error loading "flash:c3550-ipbasek9-mz.122-44.SE6/c3550-ipbasek9-mz.122-44.SE6.bin"
    Interrupt within 5 seconds to abort boot process.
    Loading "flash:/c3550-ipbasek9-mz.122-44.SE6/c3550-ipbasek9-mz.122-44.SE6.bin"...#######################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################
    File "flash:c3550-ipbasek9-mz.122-44.SE6/c3550-ipbasek9-mz.122-44.SE6.bin" uncompressed and installed, entry point: 0x3000
    executing...

    Disclaimer
    The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
    Liability Disclaimer
    In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
    Posting
    It may require a "break" signal, from you terminal, and different terminal emulators handle that, if they support it, differently.
    See if this helps: http://www.cisco.com/c/en/us/support/docs/routers/10000-series-routers/12818-61.html

  • Uhoh! I have kind of broken up the boot process

    Ok - from the top...
    1) Have Nitdroid on an 8GB SD card.  Worked fine.
    2) Decided to try and give MeeGo a look.  Formatted card and wrote the image to the card.
    3) Installed UBoot, as would be needed to get into Meego.
    4) Meego didn't load,
    5) Decided to reformat card and install NitDroid back on to it.
    6) U boot has been uninstalled (I believe), but the boot up still loads it (shows Tux Penguin) and scrolls lots of linux text, and then hangs...
    EDIT = 7) Phone boots into Maemo if SD Card is not in the phone, but does still list all the text beforehand.
    Any ideas what I can do to just get back to a simple bootup choice of Maemo or Nitdroid?
    I could flash the phone, but even then, I am not sure if this will resolve it, and then I will have to re-install all the apps afterwards.
    If tnis post is a cure to your issue, please MARK IT AS SOLUTION.
    If this post has helped anyone in any way, PLEASE SHARE YOUR KUDOS, by clicking on the GREEN STAR.
    Solved!
    Go to Solution.

    That's all "geek" to me.  How do I get out of the mess tho?
    EDIT - Sod it! Have re-flashed the phone, and will just have to watch what is installed from the restore, and untick all things I don't want back on it...
    If tnis post is a cure to your issue, please MARK IT AS SOLUTION.
    If this post has helped anyone in any way, PLEASE SHARE YOUR KUDOS, by clicking on the GREEN STAR.

  • How can i quicken the booting process

    I have a MacBook Pro 17 with a 17 inch monitor, a Mid2009 model.
    The startup-process takes longer each week - now I've reached a time of 4,5 minutes until I can  start working.
    I've installed Mavericks, and have used under 20% of the 500GB harddrive.
    What can I do?
    I look forward to any help, as I have tried
    - SMC Reset
    - PRAM Reset
    - Clean Install
    - used Onyx
    - used Washing Machine
    - checked the harddrive: it's OK
    - repaired the access priviledges...
    Cheers
    Alex

    stock machine meaning before you make any changes, which you did by restoring data from time machine
    think of it this way, restoring from time machine brings back all the junk we just cleaned out by doing a fresh OS install
    so to troubleshoot, reboot holding command r, use disk utility to erase then drive then choose install OSX BUT do not restore from time machine yet
    let the machine run for about 15 minutes (spotlight needs to index) then give it 2-4 restarts and you should see MUCH better response times

  • Skipping parts of the boot process

    When I boot up arch on my laptop, it always tries to establish a Network connection, even when there is no chance of success, because I'm not plugged into a LAN. When this is the case, it often takes about 15-20 seconds  before it fails, and so far I haven't found any key combinations that let me skip out on it. Does anyone know a way to skip out on that when there's no network available?
    Thanks

    Just background the network Daemon in your /etc/rc.conf like this:
    DAEMONS=(... @network ...)
    I stronly recommend reading the http://wiki.archlinux.org/index.php/Beginners_Guide . You'll find everything you need there!
    Cheers

  • How does the boot-process assemble the raid?

    Hi everyone,
    I just switched from Debian and CentOS to archlinux on all my machines and I really love it so far!
    Now I feel that I can really customize my OS the way I want.
    But I was thinking about one thing that I don't really understand yet, and of what I have
    read on this forum I'm certain that someone knows the answer.
    On my primary machine I have an mdadm-raid.
    And the partitions looks like this:
    /dev/sda                          /dev/sdb
    Disk1                              Disk2
    /dev/sda1                        /dev/sdb1
    100mb ext2 (boot)            100mb empty (I did empty partition so that the disks looks the same.)
    /dev/sda2  <- RAID0 ->   /dev/sdb2            /dev/md0
    2500MB ext3 (root)          2500MB ext3
    /dev/sda3  <- RAID0 ->   /dev/sdb3            /dev/md1
    2250MB (swap)                2250MB swap
    /dev/sda4  <- RAID0 ->   /dev/sdb4            /dev/md2
    245150MB ext3 (home)    245150MB ext3
    So there was a little tricky to get it installed and assemble the raid at boot, but now it's working like a dream again.
    And what I did what except loading mdadm-hook of course I used the kernel parameter: ro root=/dev/md0 md=0,/dev/sda2,/dev/sdb2 a.s.o. to
    tell the initrd how to assemble the raid at boot.
    But before archlinux i've done this setup in the installer, and after I've installed for example Debian, the system boots correctly and
    assemble the raid at boot, but without the kernel-parameters, how does the system know how the raid should be assembled?
    I've tried to include the mdadm.conf but with no success, does the initrd contain the raid information is some way?

    To obtain that file, run:
    abs
    This will provide the abs tree of core,extra, and community in /var/abs.
    Then you can get the file:
    # vim: set ft=sh:
    run_hook ()
        input="$(cat /proc/cmdline)"
        mdconfig="/etc/mdadm.conf"
        # for partitionable raid, we need to load md_mod first!
        modprobe md_mod 2>/dev/null
        # if no config file is present create one from command line parameters
        if ! [ -e $mdconfig ]; then
            #Create initial mdadm.conf
            # scan all devices in /proc/partitions
            echo DEVICE partitions > $mdconfig
            for i in $input; do
            case $i in
                    # raid
                    md=[0-9]*,/*)
                        device="$(/bin/replace -s,/ "$i" "=" "")"
                        array="$(/bin/replace -s/ "$device" "," " devices=")"
                        echo "ARRAY /dev/$array" >> $mdconfig
                        RAID_FOUND=1
                    # partitionable raid
                    md=d[0-9]*,/*)
                        device="$(/bin/replace -s=d "$i" "md=" "md_")"
                        array="$(/bin/replace -s/ "$device" "," " devices=")"
                        echo "ARRAY /dev/$array" >> $mdconfig
                        RAID_FOUND=1
                    # raid UUID
                    md=[0-9]*,[0-9,a-z]*)
                        device="$(/bin/replace -s,/ "$i" "=" "")"
                        array="$(/bin/replace -s/ "$device" "," " uuid=")"
                        echo "ARRAY /dev/$array" >> $mdconfig
                        RAID_FOUND=1
                    # partitionable raid UUID
                    md=d[0-9]*,[0-9,a-z]*)
                        device="$(/bin/replace -s=d "$i" "md=" "md_")"
                        array="$(/bin/replace -s/ "$device" "," " uuid=")"
                        echo "ARRAY /dev/$array" >> $mdconfig
                        RAID_FOUND=1
                esac
            done
        else
            RAID_FOUND=1
        fi
        if [ "$RAID_FOUND" = 1 ]; then
            # assemble everything
            /sbin/mdassemble.static
        fi
    The above is what is provided in mine............

  • Udev breaking the booting process

    Hello,
    I have a very frustrating problem.
    I did install Archlinux... baaaad things happened.
    I can't actually boot... eveything is installed fine... but
    When I boot the filesystem check fails, saying /dev/sda6 is already mounted.
    Says that
    /dev/sda6 is mounted [fail]
    **********************FILESYSTEM CHECK FAILED ******************
    * Please repair manually and reboot. Note that the root file system is currently
    * mounted read-only. To remount it read-write type: mount -n -o remount,rw /
    * When you exit the maintenance shell the system will reboot automatically
    I just won't post my fstab since I can't copy anything, but I've checked it numerous times, and it's not the source of the problem.
    I can tell how it's parttioned tho...
    sda1 - /boot
    sda2 - swap
    sda5 - /
    sda6 - /usr
    sda7 - /usr/local
    sda8 - /var
    sda9 - /var/log
    sda10 - /var/spool
    sda11 - /tmp
    sda12 - /home
    I've tried doing a 'lsof' on maintenance console.
    I found out libkmod.so was loaded from /usr by UDEVD... Why the hell UDEVD is loaded there, before fscks?!
    Oh... by the way. It's a 100% fresh install.
    Thanks,
    silk

    nomorewindows wrote:
    Here's what I did earlier in another post: (You can copy the needed files to your root partition until it is corrected using a recovery CD or another installation)  Then when it finally mounts the /usr partition it will cover up the root partition. 
    /sbin/modprobe is a soft-link to /usr/bin/kmod which isn't mounted yet, despite the early /usr mount option.  When it comes to mounting /usr at that time, I don't think mine is.
    Have mine fixed, just put the /usr/bin/kmod binary "undermounted" on my / partition (temporarily) along with /usr/lib/libkmod.so.1 and /usr/lib/libz.so.1 (copying the actual files and then linking to them).  Currently, the real files are /usr/lib/libkmod.so.1.3.0 and /usr/lib/libz.so.1.2.5
    A better option is to use ABS to grab core/kmod
    edit PKGBUILD and add --prefix=/ to the configure args, remove "usr" from the soft links.
    Putting something as basic as module loading anywhere other than '/bin' is pure lunacy.  I'm sorry but I consider kernel module loading a touch more critical for system bootstrapping than say libreoffice, kde or firefox (all of which *belong* somwhere other than '/'.
    I've always built my systems to be minimally bootable (and repairable) from '/' only, then use that to bootstrap all the other partitions like /usr /opt, etc.
    I had the unpleasant experience that mkinitcpio.conf somehow got reset (did kernel 3.2.1 cause this?) so that my /usr wasn't mountable and because kmod only resided on '/usr' i couldn't load the module necessary to mount '/usr' to start bootstrap.
    and just more ranting, i do't give a rip about what freedesktop says.  I don't care about any 'desktop' when booting, i'm more than happy sometimes working in a console.
    Last edited by bnolsen (2012-01-23 18:05:10)

  • [solved]Trying to insert a blocking systemd unit into the boot process

    What i'm trying to do is to start (and *wait* for it to complete) a unit before starting another.
    In particular, i need to create and mount a partition on the fly before any filesystem gets mounted.
    My unit file is:
    # cat /etc/systemd/system/early-boot-koko.service
    [Unit]
    Description=Configurazione ottimale per il boot da rete
    [Service]
    Before=systemd-remount-fs.service
    #Nice=19
    #IOSchedulingClass=3
    #IOSchedulingPriority=7
    Type=oneshot # is forking instead of oneshot needed here?
    ExecStart=/root/scripts/early-boot.sh
    TimeoutSec=0
    #StandardInput=tty
    RemainAfterExit=yes
    I created even created an override to systemd-remount-fs.service and added early-boot-koko.service to the "After" array:
    ]# cat /etc/systemd/system/systemd-remount-fs.service
    # This file is part of systemd.
    # systemd is free software; you can redistribute it and/or modify it
    # under the terms of the GNU Lesser General Public License as published by
    # the Free Software Foundation; either version 2.1 of the License, or
    # (at your option) any later version.
    [Unit]
    Description=Remount Root and Kernel File Systems
    Documentation=man:systemd-remount-fs.service(8)
    Documentation=http://www.freedesktop.org/wiki/Software/systemd/APIFileSystems
    DefaultDependencies=no
    Conflicts=shutdown.target
    After=systemd-readahead-collect.service systemd-readahead-replay.service systemd-fsck-root.service early-boot-koko.service
    Before=local-fs-pre.target local-fs.target shutdown.target
    Wants=local-fs-pre.target
    ConditionPathExists=/etc/fstab
    [Service]
    Type=oneshot
    RemainAfterExit=yes
    ExecStart=/usr/lib/systemd/systemd-remount-fs
    But when i boot, i notice that early-boot-koko.service is still running while systemd-remount-fs has exited :
    # systemctl |grep 'early\|remount'
    early-boot-koko.service loaded active running Configurazione ottimale per il boot da rete
    systemd-remount-fs.service loaded active exited Remount Root and Kernel File Systems
    ...but i need  early-boot-koko.service to complete before systemd-remount-fs is started.
    What am i doing wrong?
    Thanks.
    Last edited by kokoko3k (2014-10-09 12:14:23)

    ...it was the comment on the same line:
    Type=oneshot # is forking instead of oneshot needed here?
    solved...

Maybe you are looking for