Root device /dev/sda1 doesn't exist

I got something like this when I booted today (at the stage of initializing kernel):
Root device '/dev/sda1' doesn't exist, attempting to create it
ERROR: Failed to parse block device ids
ERROR: Unable to detect or create root device'
I did try the normal kernel (I currently use kernel26-ice), but haven't tried those xen0 and selinux kernels though. Also I tried changing /dev/sda1 to hda1 in menu.lst and fstab, but no luck .
E: Will try this one once I have time: http://wiki.archlinux.org/index.php/Ins … .27t_exist
Other help is still of course greatly appreciated .
Last edited by algorythm (2009-10-11 11:21:56)

Yeah, thanks but I even used rootdelay=90 by then.
The problem turned out to be that I didn't have the "sata" or "filesystems" hook on my (/etc/)mkinitcpio.conf, so it wouldn't have been possible to recognize any other partitions or any filesystems either (at least with my machine).
So how I booted correctly (with the first time btw) was that I booted the -fallback kernel that DOES have (all) the hook(s) I needed in the kernel26(-ice)-fallback.img.
So I had these hooks before this:
base udev fbsplash autodetect pata scsi sata uresume filesystems
During this:
base udev uresume
And now after this:
base udev sata uresume filesystems
Cheers!
Last edited by algorythm (2009-10-14 15:51:15)

Similar Messages

  • /dev/sda1 doesn't exist

    Hello,
    Whenever I try to mount my flash drive I use this command:
    #mount /dev/sda1 /mnt/usb
    For some reason, it says now that /dev/sda1 doesn't exist.
    I think my flash drive itself is dead but it's not inserted when the computer starts so I don't know why the device isn't in /dev.
    I'm currently at school so I can't give the exact error. Tell me if you need the output of any command.

    I do have other things in the usb ports. They're a brother printer and a wireless mouse piece. Here is the output of dmesg:
    [ameen@manghi ~]$ dmesg
    Linux version 2.6.19-ARCH (root@Laptop) (gcc version 4.1.2 20061215 (prerelease)) #1 SMP PREEMPT Thu Jan 11 20:08:17 CET 2007
    BIOS-provided physical RAM map:
    BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
    BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
    BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
    BIOS-e820: 0000000000100000 - 000000001fff0000 (usable)
    BIOS-e820: 000000001fff0000 - 000000001fff8000 (ACPI data)
    BIOS-e820: 000000001fff8000 - 0000000020000000 (ACPI NVS)
    BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
    BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
    BIOS-e820: 00000000ffee0000 - 00000000fff00000 (reserved)
    BIOS-e820: 00000000fffc0000 - 0000000100000000 (reserved)
    0MB HIGHMEM available.
    511MB LOWMEM available.
    Entering add_active_range(0, 0, 131056) 0 entries of 256 used
    Zone PFN ranges:
    DMA 0 -> 4096
    Normal 4096 -> 131056
    HighMem 131056 -> 131056
    early_node_map[1] active PFN ranges
    0: 0 -> 131056
    On node 0 totalpages: 131056
    DMA zone: 32 pages used for memmap
    DMA zone: 0 pages reserved
    DMA zone: 4064 pages, LIFO batch:0
    Normal zone: 991 pages used for memmap
    Normal zone: 125969 pages, LIFO batch:31
    HighMem zone: 0 pages used for memmap
    DMI 2.3 present.
    ACPI: RSDP (v000 AMI ) @ 0x000fa2c0
    ACPI: RSDT (v001 AMIINT SiS735XX 0x00001000 MSFT 0x0100000b) @ 0x1fff0000
    ACPI: FADT (v001 AMIINT SiS735XX 0x00001000 MSFT 0x0100000b) @ 0x1fff0030
    ACPI: DSDT (v001 SiS 735 0x00000100 MSFT 0x0100000d) @ 0x00000000
    ACPI: PM-Timer IO Port: 0x808
    Allocating PCI resources starting at 30000000 (gap: 20000000:dec00000)
    Detected 1095.404 MHz processor.
    Built 1 zonelists. Total pages: 130033
    Kernel command line: root=/dev/hdb2 ro
    Local APIC disabled by BIOS -- you can enable it with "lapic"
    mapped APIC to ffffd000 (0140b000)
    Enabling fast FPU save and restore... done.
    Enabling unmasked SIMD FPU exception support... done.
    Initializing CPU#0
    PID hash table entries: 2048 (order: 11, 8192 bytes)
    Console: colour VGA+ 80x25
    Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
    Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
    Memory: 515000k/524224k available (2330k kernel code, 8704k reserved, 735k data, 260k init, 0k highmem)
    virtual kernel memory layout:
    fixmap : 0xfff83000 - 0xfffff000 ( 496 kB)
    pkmap : 0xff800000 - 0xffc00000 (4096 kB)
    vmalloc : 0xe0800000 - 0xff7fe000 ( 495 MB)
    lowmem : 0xc0000000 - 0xdfff0000 ( 511 MB)
    .init : 0xc0405000 - 0xc0446000 ( 260 kB)
    .data : 0xc0346806 - 0xc03fe64c ( 735 kB)
    .text : 0xc0100000 - 0xc0346806 (2330 kB)
    Checking if this processor honours the WP bit even in supervisor mode... Ok.
    Calibrating delay using timer specific routine.. 2192.10 BogoMIPS (lpj=4384211)
    Security Framework v1.0.0 initialized
    Mount-cache hash table entries: 512
    CPU: After generic identify, caps: 0383f9ff c1c3f9ff 00000000 00000000 00000000 00000000 00000000
    CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
    CPU: L2 Cache: 256K (64 bytes/line)
    CPU: After all inits, caps: 0383f9ff c1c3f9ff 00000000 00000420 00000000 00000000 00000000
    Intel machine check architecture supported.
    Intel machine check reporting enabled on CPU#0.
    Compat vDSO mapped to ffffe000.
    Checking 'hlt' instruction... OK.
    SMP alternatives: switching to UP code
    Freeing SMP alternatives: 12k freed
    checking if image is initramfs... it is
    Freeing initrd memory: 501k freed
    ACPI: Core revision 20060707
    ACPI: Looking for DSDT in initramfs... error, file /DSDT.aml not found.
    ACPI: setting ELCR to 0200 (from 0c20)
    CPU0: AMD Athlon(tm) Processor stepping 00
    SMP motherboard not detected.
    Local APIC not detected. Using dummy APIC emulation.
    Brought up 1 CPUs
    NET: Registered protocol family 16
    ACPI: bus type pci registered
    PCI: PCI BIOS revision 2.10 entry at 0xfdb01, last bus=1
    PCI: Using configuration type 1
    Setting up standard PCI resources
    ACPI: Interpreter enabled
    ACPI: Using PIC for interrupt routing
    ACPI: PCI Root Bridge [PCI0] (0000:00)
    PCI: Probing PCI hardware (bus 00)
    Uncovering SIS18 that hid as a SIS503 (compatible=1)
    Enabling SiS 96x SMBus.
    Boot video device is 0000:01:00.0
    ACPI: PCI Interrupt Routing Table [_SB_.PCI0._PRT]
    ACPI: Power Resource [URP1] (off)
    ACPI: Power Resource [URP2] (off)
    ACPI: Power Resource [FDDP] (off)
    ACPI: Power Resource [LPTP] (off)
    ACPI: PCI Interrupt Link [LNKA] (IRQs *11)
    ACPI: PCI Interrupt Link [LNKB] (IRQs *11)
    ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 7 *10 12 14 15)
    ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 7 *10 12 14 15)
    ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 10 12 14 15) *0, disabled.
    ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 7 10 12 14 15) *0, disabled.
    ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 7 *10 12 14 15)
    ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 *5 7 10 12 14 15)
    Linux Plug and Play Support v0.97 (c) Adam Belay
    pnp: PnP ACPI init
    pnp: PnP ACPI: found 11 devices
    SCSI subsystem initialized
    PCI: Using ACPI for IRQ routing
    PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
    NetLabel: Initializing
    NetLabel: domain hash size = 128
    NetLabel: protocols = UNLABELED CIPSOv4
    NetLabel: unlabeled traffic allowed by default
    PCI: Bridge: 0000:00:01.0
    IO window: disabled.
    MEM window: cde00000-cfefffff
    PREFETCH window: bdc00000-cdcfffff
    NET: Registered protocol family 2
    IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
    TCP established hash table entries: 16384 (order: 5, 196608 bytes)
    TCP bind hash table entries: 8192 (order: 4, 98304 bytes)
    TCP: Hash tables configured (established 16384 bind 8192)
    TCP reno registered
    apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
    apm: overridden by ACPI.
    VFS: Disk quotas dquot_6.5.1
    Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
    Installing knfsd (copyright (C) 1996 [email protected]).
    io scheduler noop registered
    io scheduler anticipatory registered
    io scheduler deadline registered
    io scheduler cfq registered (default)
    ACPI: Power Button (FF) [PWRF]
    ACPI: Sleep Button (CM) [SLPB]
    isapnp: Scanning for PnP cards...
    isapnp: No Plug & Play device found
    Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
    serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
    serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
    00:08: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
    00:09: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
    ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 10
    PCI: setting IRQ 10 as level-triggered
    ACPI: PCI Interrupt 0000:00:0f.0[A] -> Link [LNKD] -> GSI 10 (level, low) -> IRQ 10
    0000:00:0f.0: ttyS2 at I/O 0xd000 (irq = 10) is a 16550A
    RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
    loop: loaded (max 8 devices)
    PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12
    serio: i8042 KBD port at 0x60,0x64 irq 1
    serio: i8042 AUX port at 0x60,0x64 irq 12
    mice: PS/2 mouse device common for all mice
    TCP cubic registered
    NET: Registered protocol family 1
    NET: Registered protocol family 17
    Using IPI No-Shortcut mode
    ACPI: (supports S0 S1 S4 S5)
    Time: tsc clocksource has been installed.
    Freeing unused kernel memory: 260k freed
    input: AT Translated Set 2 keyboard as /class/input/input0
    Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
    ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
    SIS5513: IDE controller at PCI slot 0000:00:02.5
    SIS5513: chipset revision 208
    SIS5513: not 100% native mode: will probe irqs later
    SIS5513: SiS735 ATA 100 (2nd gen) controller
    ide0: BM-DMA at 0xff00-0xff07, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xff08-0xff0f, BIOS settings: hdc:DMA, hdd:DMA
    Probing IDE interface ide0...
    hda: ST380013A, ATA DISK drive
    hdb: SAMSUNG SP8004H, ATA DISK drive
    ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
    Probing IDE interface ide1...
    hdc: ATAPI CD-RW CW5205, ATAPI CD/DVD-ROM drive
    hdd: SONY CD-RW CRX160E, ATAPI CD/DVD-ROM drive
    ide1 at 0x170-0x177,0x376 on irq 15
    hda: max request size: 512KiB
    hda: 156301488 sectors (80026 MB) w/8192KiB Cache, CHS=16383/255/63, UDMA(100)
    hda: cache flushes supported
    hda: hda1 hda2 <hda5>
    hdb: max request size: 128KiB
    hdb: 156368016 sectors (80060 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(100)
    hdb: cache flushes supported
    hdb: hdb1 hdb2
    hdc: ATAPI 52X CD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33)
    Uniform CD-ROM driver Revision: 3.20
    hdd: ATAPI 32X CD-ROM CD-R/RW drive, 4096kB Cache, UDMA(33)
    kjournald starting. Commit interval 5 seconds
    EXT3-fs: mounted filesystem with ordered data mode.
    usbcore: registered new interface driver usbfs
    usbcore: registered new interface driver hub
    usbcore: registered new device driver usb
    ath_hal: module license 'Proprietary' taints kernel.
    ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
    wlan: 0.8.4.2 (0.9.2.1)
    ath_rate_sample: 1.2 (0.9.2.1)
    ath_pci: 0.9.4.5 (0.9.2.1)
    ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 11
    PCI: setting IRQ 11 as level-triggered
    ACPI: PCI Interrupt 0000:00:0b.0[A] -> Link [LNKB] -> GSI 11 (level, low) -> IRQ 11
    wifi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
    wifi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
    wifi0: H/W encryption support: WEP AES AES_CCM TKIP
    wifi0: mac 7.8 phy 4.5 radio 5.6
    wifi0: Use hw queue 1 for WME_AC_BE traffic
    wifi0: Use hw queue 0 for WME_AC_BK traffic
    wifi0: Use hw queue 2 for WME_AC_VI traffic
    wifi0: Use hw queue 3 for WME_AC_VO traffic
    wifi0: Use hw queue 8 for CAB traffic
    wifi0: Use hw queue 9 for beacons
    wifi0: Atheros 5212: mem=0xcffe0000, irq=11
    Linux agpgart interface v0.101 (c) Dave Jones
    ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
    ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
    NVRM: loading NVIDIA Linux x86 Kernel Module 1.0-9631 Thu Nov 9 17:38:10 PST 2006
    agpgart: Detected SiS 735 chipset
    agpgart: AGP aperture is 64M @ 0xd0000000
    sis630_smbus 0000:00:02.0: SIS630 comp. bus not detected, module not inserted.
    ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
    ACPI: PCI Interrupt 0000:00:02.2[D] -> Link [LNKD] -> GSI 10 (level, low) -> IRQ 10
    ohci_hcd 0000:00:02.2: OHCI Host Controller
    pci_hotplug: PCI Hot Plug PCI Core version: 0.5
    ohci_hcd 0000:00:02.2: new USB bus registered, assigned bus number 1
    ohci_hcd 0000:00:02.2: irq 10, io mem 0xcfffe000
    usb usb1: configuration #1 chosen from 1 choice
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 3 ports detected
    USB Universal Host Controller Interface driver v3.0
    shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
    ACPI: PCI Interrupt 0000:00:13.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
    uhci_hcd 0000:00:13.0: UHCI Host Controller
    uhci_hcd 0000:00:13.0: new USB bus registered, assigned bus number 2
    uhci_hcd 0000:00:13.0: irq 11, io base 0x0000c800
    usb usb2: configuration #1 chosen from 1 choice
    hub 2-0:1.0: USB hub found
    hub 2-0:1.0: 2 ports detected
    ACPI: PCI Interrupt 0000:00:13.1[B] -> Link [LNKB] -> GSI 11 (level, low) -> IRQ 11
    uhci_hcd 0000:00:13.1: UHCI Host Controller
    uhci_hcd 0000:00:13.1: new USB bus registered, assigned bus number 3
    uhci_hcd 0000:00:13.1: irq 11, io base 0x0000cc00
    usb usb3: configuration #1 chosen from 1 choice
    hub 3-0:1.0: USB hub found
    hub 3-0:1.0: 2 ports detected
    ACPI: PCI Interrupt Link [LNKH] enabled at IRQ 5
    PCI: setting IRQ 5 as level-triggered
    ACPI: PCI Interrupt 0000:00:02.3[A] -> Link [LNKH] -> GSI 5 (level, low) -> IRQ 5
    ohci_hcd 0000:00:02.3: OHCI Host Controller
    ohci_hcd 0000:00:02.3: new USB bus registered, assigned bus number 4
    ohci_hcd 0000:00:02.3: irq 5, io mem 0xcffff000
    sis900.c: v1.08.10 Apr. 2 2006
    usb usb4: configuration #1 chosen from 1 choice
    hub 4-0:1.0: USB hub found
    hub 4-0:1.0: 3 ports detected
    usb 2-1: new full speed USB device using uhci_hcd and address 2
    input: PC Speaker as /class/input/input1
    ACPI: PCI Interrupt Link [LNKG] enabled at IRQ 10
    ACPI: PCI Interrupt 0000:00:03.0[A] -> Link [LNKG] -> GSI 10 (level, low) -> IRQ 10
    0000:00:03.0: Realtek RTL8201 PHY transceiver found at address 1.
    0000:00:03.0: Using transceiver found at address 1 as default
    eth0: SiS 900 PCI Fast Ethernet at 0xd400, IRQ 10, 00:0a:e6:95:b8:e5.
    sis96x_smbus 0000:00:02.1: SiS96x SMBus base address: 0x0c00
    usb 2-1: configuration #1 chosen from 1 choice
    usb 3-2: new low speed USB device using uhci_hcd and address 2
    usb 3-2: configuration #1 chosen from 1 choice
    parport: PnPBIOS parport detected.
    parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
    ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10
    ACPI: PCI Interrupt 0000:00:13.2[C] -> Link [LNKC] -> GSI 10 (level, low) -> IRQ 10
    ehci_hcd 0000:00:13.2: EHCI Host Controller
    ehci_hcd 0000:00:13.2: new USB bus registered, assigned bus number 5
    ehci_hcd 0000:00:13.2: irq 10, io mem 0xcfffdf00
    ehci_hcd 0000:00:13.2: USB 2.0 started, EHCI 0.95, driver 10 Dec 2004
    usb usb5: configuration #1 chosen from 1 choice
    hub 5-0:1.0: USB hub found
    hub 5-0:1.0: 4 ports detected
    PPP generic driver version 2.4.2
    ACPI: PCI Interrupt 0000:00:02.7[C] -> Link [LNKC] -> GSI 10 (level, low) -> IRQ 10
    usb 3-2: USB disconnect, address 2
    usb 3-2: new low speed USB device using uhci_hcd and address 3
    intel8x0_measure_ac97_clock: measured 53955 usecs
    intel8x0: clocking to 48000
    usb 3-2: configuration #1 chosen from 1 choice
    usb 2-1: USB disconnect, address 2
    lp0: using parport0 (interrupt-driven).
    Real Time Clock Driver v1.12ac
    input: ImExPS/2 Generic Explorer Mouse as /class/input/input2
    usb 2-1: new full speed USB device using uhci_hcd and address 3
    ppdev: user-space parallel port driver
    usb 2-1: configuration #1 chosen from 1 choice
    drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 3 if 0 alt 0 proto 2 vid 0x04F9 pid 0x0028
    usbcore: registered new interface driver usblp
    drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
    usbcore: registered new interface driver hiddev
    input: Logitech USB RECEIVER as /class/input/input3
    input: USB HID v1.11 Mouse [Logitech USB RECEIVER] on usb-0000:00:13.1-2
    usbcore: registered new interface driver usbhid
    drivers/usb/input/hid-core.c: v2.6:USB HID core driver
    EXT3 FS on hdb2, internal journal
    ext3: No journal on filesystem on hda1
    fuse init (API version 7.8)
    Adding 1510068k swap on /dev/hda5. Priority:-1 extents:1 across:1510068k
    agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
    agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode
    agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode
    NET: Registered protocol family 10
    lo: Disabled Privacy Extensions
    Mobile IPv6
    ath0: no IPv6 routers present
    EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
    ADDRCONF(NETDEV_UP): ath0: link is not ready
    ADDRCONF(NETDEV_CHANGE): ath0: link becomes ready
    ath0: no IPv6 routers present

  • [SOLVED] - Arch Boot Error: Unable to find Root Device /dev/sdb1

    I had Arch running perfectly using /dev/sdb1 (versus Disk Label or UUID) and decided to do a update.  After the Update I can't boot
    to a running system, and I get this error message:
    ERROR: Unable to find root device /dev/sdb1 
    You are being dropped into a recovery shell.
    Is there an easy way to convert to UUID or Disk Label since the latest Upgrade doesn't allow me to continue to use /dev/sdb1 ??
    I'd prefer not to have to rebuild both USB Flash Drives to get functional systems.
    Any Help is greatly appreciated.
    Suggestions?
    Larry
    Last edited by lkraemer (2012-02-21 15:14:02)

    Check your grub and read https://wiki.archlinux.org/index.php/UUID#By-uuid
    Edit:
    https://bbs.archlinux.org/viewtopic.php … 0#p1059160
    https://bbs.archlinux.org/viewtopic.php?pid=1059338
    https://bbs.archlinux.org/viewtopic.php?id=135288
    Last edited by karol (2012-02-21 01:07:21)

  • [SOLVED] ERROR: Unable to find root device '/dev/sda3'

    Earlier I updated the kernel to my arch system and found this error while trying to boot. I hate to post this because there are so many topics like it, but I've been looking for hours for a solution to this problem and can't find one.
    Here is the output:
    Booting 'Arch Linux'
    root (hd0,1)
    Filesystem type is ext2fs, partition type 0x83
    kernet /vmlinuz-linux root=/dev/sda3 ro
    [Linux-bzImage, setup=0x4200, size=0x2ff2d0]
    initrd /initrd @ 0xfd17000, 0x2c878c bytes]
    Probing EDD (edd=off to disable)... ok
    Decompressing Linux... Parsing ELF... done.
    Booting the kernel.
    :: Starting udevd...
    done.
    Waiting 10 seconds for device /dev/sda3 ...
    ERROR: device '/dev/sda3' not found. skipping fsck.
    ERROR: Unable to find root device '/dev/sda3'.
    You are being dropped to a recovery shell
    type 'exit' to try and continue booting
    sh: can't access tty; job control turned off
    My partition layout is like this:
    swap: /dev/sda1
    boot: /dev/sda2
    root: /dev/sda3
    extended: /dev/sda4
    home: /dev/sda5
    I have two hard drives, but i'm sure /dev/sda is the one with my OS.
    Here are some things I've tried:
    This was at the very bottom of the pacman wiki
    # mkdir /mnt/arch
    # mount /dev/sdaX /mnt/arch (your root partition)
    # cd /mnt/arch
    # mount -t proc proc proc/
    # mount -t sysfs sys sys/
    # mount -o bind /dev dev/
    # mount /dev/sdaX boot/ (your /boot partition) #This step is not needed if you do not have a separate boot partition
    # chroot .
    # pacman -Syu udev mkinitcpio
    # mkinitcpio -p linux
    I've also tried performing the above, downgrading the kernel, updating my mirrorlist, reinstalling the kernel, and rebooting as mentioned here.
    I've alsa tried a few other things that I've read, but can no longer remember.
    Any help would be greatly appreciated! Thanks.
    Last edited by colton7909 (2012-05-25 02:09:36)

    Thank colton
    Same problem here, but on a mac book (not mine eyh )
    So, for those how have the problem (or need a live usb for mac or uefi systems),
    1) with a 32bits system
    - download gparted live cd
    - use it for the step 3
    2) with a 64bits system:
    - you need the gparted live cd too: mount it and copy the EFI directory somewhere; then umount it;
    - download a 64bits system (system rescue cd, as colton said is enough, follow the instructions for installation on their website first);
    - mount you live usb, install the 64bits system;
    - copy EFI system on the key
    - edit the grub.cfg in EFI/boot/ , add the following before the other entries:
    menuentry "System Rescue" {
    set gfxpayload=keep
    linux /syslinux/altker64 nomodeset efi
    initrd /syslinux/initram.igz
    3) repairing...
    - boot the broken computer with the live usb
    - mount the partition on which your system is (e.g. /dev/sda1 on /mnt)
    - chroot it, init the system as needed (mount /dev, /proc, etc. the easier way is using init scripts)
    % chroot /mnt /bin/bash
    % /etc/rc.sysinit
    % mkinitcpio -p linux

  • [SOLVED] ERROR: Can't find root device /dev/disk/by-uuid/...

    Yesterday I upgraded my Lenovo X100e
    # pacman -Syu
    and rebooted.  Upon reboot, I received the error
    ERROR: Cannot find root device '/dev/disk/by-uuid/[...]'
    just after kernel decompression. I got dropped into the recovery shell
    and could not boot.
    The problem persisted despite using different root device names (e.g. /dev/sda3, the actual root device).  After reading the instructions at https://wiki.archlinux.org/index.php/Chroot I used a core installation image (on a usb stick) to boot the machine, then chrooted into my installation.  I ran mkinitcpio and found that the udev hook was missing, i.e. not in /lib/initcpio/hooks.  Nor was there a file called 'udev' in /lib/initcpio/install.
    I copied these files from a friend's installation and then re-ran mkinitcpio:
    # mkinitcpio -p linux
    I was able to reboot successfully after that.
    The weird thing: I don't know how the udev hook script was deleted from /lib/initcpio/hooks.
    If someone else runs into this problem: try to run mkinitcpio (e.g. by using the chroot), and check for this problem.  I think the problem was that the root device could not be found because the udev hook had not run, and therefore /dev was unpopulated.

    Betwen udev-181-2 and udev-181-5, the hooks have moved from /lib/initcpio to /usr/lib/initcpio. But mkinitcpio -L should still list them.
    I have a similar problem since the last update. The kernel doesn't seem to load my raid driver anymore. Upon boot it throws some cryptic udev messages at me and then crashes. Haven't found out what that is about yet.

  • "Unable to find root device /dev/sda2"

    Hi!
    After an update - seemingly unsuccessfull - I get dropped into a recovery shell. The messages are:
    /usr/lib/suspend/resume: /usr/lib/libpng14: version `PNG14_0`not found (required by /usr/lib/libsplshrender.so.1)
    ERROR: unable to find root device '/dev/sda2'
    I read that now I'm supposed to run a LiveCD and chroot something... can someone please be a little more specific here? I don't want to lose that system and I have no idea why it doesn't find my disk anymore. I just performed a pacman4 uprade, but it seems pacman4 is rather immature, leaving a system unuseable like that.
    There is no sdaX in /dev any more. And I have very little experience with recovering Arch Linux. Until now
    Best,
    wishi

    I have some wild problems here
    1.) I used an Arch Live CD, did the chroot trick from the wiki (https://wiki.archlinux.org/index.php/Ch … nging_Root) and rebuild my initcpio (https://wiki.archlinux.org/index.php/Mkinitcpio). That ends successfull, and says it adds hooks for sata etc.
    -> But I had to remove the udev hook: http://bbs.archbang.org/viewtopic.php?pid=11304 - I guess that's the reason why it still doesn't find my /dev/sda2 - I'm not sure this is related though.
    2.) I ran pacman -Qk to ensure everything is sane. No errors.  I reinstalled linux and udev two minutes ago. No change.
    But I don't see how I can fix this. What's that voodoo with some udev hooks wandering around? The new kernel is 3.2.5-1 ARCH.

  • /dev entry doesn't exist but /devices does!

    I have a pseudo dd that seems to install and attach ok.
    There is an entry in /devices but none in /dev.
    I've tried modifying devlinks.tab and running devlinks, but this doesn't help.
    Its nearly there(I think) - any advice or pointers would be appreciated.

    I have a pseudo dd that seems to install and attach
    ok.
    There is an entry in /devices but none in /dev.
    I've tried modifying devlinks.tab and running
    devlinks, but this doesn't help.
    use correct syntax i.e tab space before /D and
    also give driver name and minor name correctly.
    no need to run devlinks when u say add_drv devlinks
    get automatically executed.
    Its nearly there(I think) - any advice or pointers
    would be appreciated.i too faced the same problem now very fine

  • [Solved] Root device doesn't exist

    Hi!
    EDIT SOLVED: Booted from a arch-core CD and did a;
    mv /etc/mkinitcpio.conf.pacnew /etc/mkinitcpio.conf
    pacman -U /var/cache/pacman/pkg/kernel26-2.6.25-4-1-i686.pkg.tar.gz
    Seems like a had a configuration error in my old mkinitcpio.conf file and kernel install failed.
    .. But should it install when the kernel install failes?
    For interested, here is my pacman.log
    [2008-05-24 20:04] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
    [2008-05-24 20:04] ==> Building image "default"
    [2008-05-24 20:04] ==> Running command: /sbin/mkinitcpio -k 2.6.25-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
    [2008-05-24 20:04] :: Begin build
    [2008-05-24 20:04] :: Parsing hook [base]
    [2008-05-24 20:04] :: Parsing hook [udev]
    [2008-05-24 20:04] :: Parsing hook [autodetect]
    [2008-05-24 20:04] :: Parsing hook [pata]
    [2008-05-24 20:04] :: Parsing hook [scsi]
    [2008-05-24 20:04] :: Parsing hook [sata]
    [2008-05-24 20:04] :: Parsing hook [usbinput]
    [2008-05-24 20:04] ==> FAIL
    [2008-05-24 20:04] ==> Building image "fallback"
    [2008-05-24 20:04] ==> Running command: /sbin/mkinitcpio -k 2.6.25-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26-fallback.img -S autodetect
    [2008-05-24 20:04] :: Begin build
    [2008-05-24 20:04] :: Parsing hook [base]
    [2008-05-24 20:04] :: Parsing hook [udev]
    [2008-05-24 20:04] :: Parsing hook [pata]
    [2008-05-24 20:04] :: Parsing hook [scsi]
    [2008-05-24 20:04] :: Parsing hook [sata]
    [2008-05-24 20:04] :: Parsing hook [usbinput]
    [2008-05-24 20:04] ==> FAIL
    [2008-05-24 20:04] upgraded kernel26 (2.6.25.4-1 -> 2.6.25.4-1)
    And old mkinitpcio.conf
    MODULES="ata_generic ahci"
    BINARIES=""
    FILES=""
    HOOKS="base udev autodetect pata scsi sata usbinput keymap filesystems"
    I think it was the keymap it complained about
    ---- Original message
    After the last upgrade with kernel 2.6.25, i get;
    Attempting to create root device '/dev/sda3'
    ERROR: Failed to parse block device name for '/dev/sda3' unknown
    ERROR: root fs cannot be detected
    Waiting for device to settle...done
    Root device '/dev/sda3' doesn't exist, attempting to create it
    ERROR: Failed to parse block device name for '/dev/sda3' unknown
    ERROR: Unable to create/detect root device, '/dev/sda3'
    Dropping to recovery shell.. type 'exit' to reboot
    at startup.
    The fallback entry at grub, gives the same message.
    When trying to modprobe a module, it gives me message:
    FATAL: Could not load /lib/modules/2.6.25-ARCH/modules.dep: No such file or directory
    Only /lib/modules/2.6.24-ARCH exists.
    Last edited by cybe-arch (2008-05-24 18:40:56)

    I have the same issue with kernel26-lts-2.6.32.41-1.
    Recent Arch updates made my favourite operating system of the worst kind: flashplugin freezez in 5 seconds, mozilla gets some freezes as well,
    copying files from one drive to another takes like 1.5h and many more weird things including some frequent performance abuses by the processes.
    I see Arch behaves like old Microshit products. Sad thing but I move to more stable distro very soon, because I have enough of fixing bugs 3 times a week, to make my Arch usable again. Before like 6 months ago updated were less frequent and surprises were once a month not twice a week. Outrageous.
    Perhaps Arch crew is overrun by the Apple guys, to compromise this distro, to encourage people to buy Apple products instead of using faulty Windowses or from day to day more troublesome Linuxes.
    Going to the point.
    So in response I wanted give LTS a try, but it drops me to recovery console (ramfs) saying that "Root device doesn't exist"

  • [Solved] kernel 2.6.27 - Root device not found (2.6.28 too)

    since the last kernel update, my ArchLinux won't boot anymore, as it seems to be unable to find the root partition "/dev/sda5". The exact output is:
    :: Loading root filesystem module...
    Attempting to create root device '/dev/sda5'
    ERROR: Failed to parse block device name for '/dev/sda5'
    unknown
    ERROR: root fs cannot be detected. Try using the rootfstype= kernel parameter.
    Waiting for devices to settle...done.
    Root device '/dev/sda5' doesn't exist, attempting to create it
    ERROR: Failed to parse block device name for '/dev/sda5'
    ERROR: Unable to create/detect root device '/dev/sda5'
    Dropping to a recovery shell... type 'exit' to reboot
    NOTE: klibc contains no 'ls' binary, use 'echo *' instead
    If the device '/dev/sda5' gets created while you are here,
    try adding 'rootdelay=8' or higher to the kernel command-line
    ramfs$
    What I have tried:
    1.- I have booted with an old Ubuntu LiveCD, and /dev/sda5 seems to be working and healthy, as it mounted flawlessly while in Ubuntu.
    2.- I have also found that not even /dev/sda is created from the fallback recovery shell so, obviously, there is no root device to create.
    3.- None of the suggested kernel command-line parameters worked: 'rootfstype=ext3' and/or 'rootdelay=8'(I mean, using them separately or both in the same kernel GRUB line) didn't give any positive result, or any behavior change.
    And now, two questions:
    1.- How can I fix this?
    2.- If it's not possible, how can I downgrade the kernel from a LiveCD? I suppose this is possible by booting an ArchLinux LiveCD, chrooting my '/dev/sda5' finding a 2.26.X kernel pacman package and installing, but I'm almost iliterate in kernel issues, and some help would be nice.
    Thank you all in advance!
    EDIT: Oh, I have also waited for some time to see if the hard disk gets ready after the failed booting proccess but it seems it doesn't, so 'rootdelay=8' wouldn't help anyway, just to give some more details about the problem.
    Last edited by 4s|m3tr|ko0 (2009-01-21 10:14:32)

    4s|m3tr|ko0 wrote:
    ballon wrote:It seems like my problems can be the same, however I haven't managed to solve it myself so if you can be more detailed that would be nice.
    Of course I can, it's quite easy.
    First of all, you have to boot from an Archlinux install CD, to have an usable environment. Once you have booted, I will assume a couple of things to make the examples, which are:
    "/dev/sda2" is the root partition where the system is currently installed but not booting.
    "/dev/sda1" is the boot partition (not needed if you don't have a separated boot partition, obviously).
    "/mnt/myarch" is the directory where sda1 will be mounted on the live session.
    The kernel version on sda2 is "2.6.27-ARCH", you can find which kernel versions are installed on sda2 by checking the directory names under "/lib/modules/"
    Next you have to mount your root partition on any directory and mount the "boot" partition if you have one too:
    mkdir /mnt/myarch #Creates the mount directory on the live session, you can use /mnt/ so this command is not neccesary
    mount -t auto /dev/sda2 /mnt/myarch #Mount the root partition on the live session
    mount -t auto /dev/sda1 /mnt/myarch/boot #Mount the boot partition, if you have to
    Now, you'll have to bind three system directories to their true locations on the root partition:
    mount -t proc proc /mnt/myarch/proc
    mount -t sysfs sys /mnt/myarch/sys
    mount -o bind /dev /mnt/myarch/dev
    Next step is to use the command "chroot <target> <consolebin>" to "move" the system root to the <target> directory, using the <consolebin> command interpreter:
    chroot /mnt/myarch/ /bin/bash
    Now, you will be using your system just like if you had actually booted from your hard disk, but running the kernel from the liveCD, so the only remaining step is to generate the initcpio image.
    In the example for this step, I will run the mkinitcpio twice, the first one to check that it's correctly generated, and the second to install it, using the parameter "-g". Another thing to keep in mind is that even before chrooting, the liveCD kernel is still running, so you will have tu use the "-k <kernelversion>" parameter to manually specify the kernel to use. Otherwise, mkinitcpio won't be able to find the correct modules to use:
    mkinitcpio -k 2.6.27-ARCH #This will simulate the generation, if it runs fine, run the next command
    mkinitcpio -g /boot/kernel26.img -k 2.6.27-ARCH #This will actually generate the image
    And that's all, this should regenerate a default image. More info about mkinitcpio: http://wiki.archlinux.org/index.php/Mkinitcpio
    Hope this heps
    PS: Sweden, nice country .
    I follow this guide and I saved my Arch installation. I don't know why the HOOKS array in my mkinitcpio.conf just contains "base" :-?
    So, just before regenerate the ramdisk image I edit my /etc/mkinitcpio.conf and add all the neccessary hooks and generate. I can bring my Arch box back to life

  • [SOLVED] Booting Arch off USB HDD fails - can't mount real root device

    I've installed Arch on the internal HDD (sda) of my laptop, and I attempted to install a second copy of Arch on partition sdb3 of an external USB HDD.  sdb3 is a primary partition that I had prepared beforehand with gparted and outfitted with the reiserfs filesystem.  I skipped section 3.2 (manually prepare hard drives) of the Arch installer.  There was no problem with section 3.3 (manually configure filesystems and mountpoints); I put all of / in sdb3.  Installing packages and configuring the system also went without a hitch.
    I wanted to boot this new install of Arch via the boot menu of GRUB that was installed in the MBR of sda with my primary install of Arch.  On the new install, I first did go through section 7 (install bootloader), thinking I would want to install GRUB in the root sector of partition sdb3 (not in the MBR of sdb where the GRUB of MintKDE resides, a boot menu that I want to keep) but that failed, so I then picked "no bootloader to be installed".  With that I exited the new install, since it appeared to have gone to completion.
    I then copied the appropriate stanza in the /boot/grub/menu.lst of this new Arch install to the /boot/grub/menu.lst of my primary Arch install on the internal HDD of my laptop.
    This stanza reads as follows:
    # (3) Arch Linux on WDPP60 blue (sdb3)
    title Arch Linux on WDPP60 blue (sdb3)
    root (hd1,2)
    kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/191cc027-43ce-443b-8846-f265d60555ec ro
    initrd /boot/kernel26.img
    However, I'm not able to boot the new Arch install when I pick this entry from the GRUB menu list.  The new install starts booting, finds sda but not sdb and stops with the following errors, dropping me to a recovery shell:
    Root device /dev/disk/by-uuid... doesn't exist. Attempting to create it.
    ERROR: Unable to determine major/minor number of root device '/dev/disk/by-uuid...'
    mounting /dev/disk/by-uuid... on /new_root failed: No such file ...
    ERROR: Failed to mount the real root device.
    Running "mount -t reiserfs /dev/sdb3 /new_root" at the ramfs prompt also fails.
    I've tried a number of edits of the menu.lst stanza from the grub> command prompt, such as adding rootfstype=reiserfs, replacing root=/dev/disk/by-uuid..etc. with root=/dev/sdb3 (booting then fails with "/dev/sdb3  No such file"), using "initrd /boot/kernel26-fallback.img" etc., but booting always fails at the same stage with equivalent error messages.
    I have no trouble booting half a dozen other Linux/BSD distros that reside on two different external USB HDD's by the same method, i.e. choosing an entry from the GRUB boot menu of my primary Arch install, after I placed the appropriate stanza in its /boot/grub/menu.lst.
    How can I get this new Arch install to boot?
    Last edited by RobF (2010-05-17 23:03:27)

    Yes, this was in fact the solution.  I stumbled upon it in this thread:
    http://bbs.archlinux.org/viewtopic.php?id=65844
    When one wants to boot from a USB mass storage device, the initrd needs to include the modules for accessing USB devices, and in Arch this is accomplished by adding "usb" to the HOOKS array.  I simply reinstalled Arch to the USB HDD and in the system configuration step now edited /etc/mkinitcpio.conf by adding the "usb" item.  Adding "rootdelay=10" and/or "rootfstype=reiserfs" to the kernel line in the appropriate stanza in Arch's /boot/grub/menu.lst wasn't necessary in this case.  I left the stanza exactly as I posted it above.
    Thanks for your input.

  • Yet another "unable to find root device" problem (pacman issue) SOLVED

    During this night I've been trying to solve a problem that let me without access to my ArchLinux partition.
    Booting the kernel.
    :: Starting udevd...
    done.
    :: Running Hook [udev]
    :: Triggering uevents...done.
    Waiting 10 seconds for device /dev/by-uuid ...
    ERROR: Unable to find root device '/dev/by-uuid'.
    You are being dropped to a recovery shell
    Type 'exit' to try and continue booting
    sh: can't access tty: job control turned off
    [rootfs /]#
    The thing is that I've read about chrooting, I did chroot following the steps described on the Wiki https://wiki.archlinux.org/index.php/Change_Root but I have a problem with pacman and it's that I can't use pacman on chroot, it says: command not found. I must've done something wrong but I have no clue.
    My disk is sda1 and I don't use a special partition for /boot or /home.
    Thank you in advance.
    Last edited by ffuentes (2012-08-17 04:33:38)

    I've solved the mystery.
    Well, I realised that I had another serious issue with filesystem (that was mentioned on the Archlinux's news https://www.archlinux.org/news/filesyst … equired-1/ and https://www.archlinux.org/news/the-lib- … a-symlink/ ) so I had to figure out which packages were using /lib to remove them. Also I had to disable pacman's signature checking system because as I said before it didn't seem to work.
    After removing every package that happened to use /lib  at that time I eventually could perform the command "pacman -Syu" and later on "mkinitcpio -p linux" worked out.
    Thanks DSpider.

  • Root device cannot be found after fresh installation

    I just made a fresh installation on my lenovo y500. Everything went well. I rebooted (without the usb), and I get the error:
    "ERROR: device '/dev/sdc2' not found. Skipping fsck.
    Error: Unable to find root device '/dev/sdc2"
    I figured I must have goofed somewhere in the installation process, so I thought I'd just boot back into my live USB and start all over, but now the USB is not being detected whatsoever.
    When I open my BIOS, I can't change my boot priorities to USB because the option isn't even present anymore. It's as if the USB isn't recognized.
    When I try to boot into my (apparently broken) arch installation, I get dropped to a recovery shell after the error. Is there anything I can do in this?
    I don't want to make a whole other LiveUSB because the only machines I have left to make it are windows. And I'm windows retarded...
    I have already done the following:
    1. Ensured that secure boot is disabled
    2. Enabled USB Boot (However it doesn't show up in my bootable devices. Only see HDD Device and Linux Boot Manager. Both bring me to the same error)
    3. Moved my USB stick to different ports. Still not able to be detected as a bootable device
    4. Booted into recovery mode. It brings me to the same error.
    Would switching my boot mode to legacy help at all? I'd rather not even try because I just don't even see how it could help.root device not found arch post installatin
    This is not a dual installation. It's a clean installation because I didn't want any silly boot errors (just my luck, I guess).
    Gummiboot was my chosen bootloader during installation. I only had 2 partitions made a root partition 'sdc2' and the efi partition 'sdc1' which was formatted and created with the ef00 esp code
    No notable errors arose during installation and I unmounted everything before I rebooted. I am truly at my wit's end...

    lknows wrote:2. /dev/sdc was the planned installation location (if that's what you're asking) When I booted into the live usb, the usb was named sda, and the command [ fdisk -l ] didn't reveal any sdb location at all.
    No wonder your bootloader's not finding anything. /dev/sdc was the right installation point when you were running the LiveUSB, but it isn't the right mount point when actually booting from the machine.
    Find the bootloader settings of the actual installation (inside the /boot folder) and change the /dev/sdc to either /dev/sdb or /dev/sda and then try booting in again (I suggest /dev/sdb first).
    I use UUIDs with GRUB, and you can probably do something similar with gummboot. I do it so I avoid being unable to boot when my internal hard disk (I only have one) isn't recognised as /dev/sda.
    Last edited by clfarron4 (2014-10-11 21:50:23)

  • [SOLVED]Failed to find root device after linux (3.6) upgrade on raid 1

    on a test machine pacman -Syu offers linux-3.6.2-1.
    After a successfull update the system won't boot anymore with the following error:
    [ 0.000000] tsc: Fast TSC calibration failed
    :: running early hook [udev]
    :: running hook [udev]
    :: triggering uevents...
    Waiting 10 seconds for device /dev/md1 ...
    ERROR: device '/dev/md1' not found. Skipping fsck.
    ERROR: Unable to find root device '/dev/md1.
    and the machine gets thrown to a recovery shell
    /boot/syslinux/syslinux.cfg entry:
    LABEL arch
    MENU LABEL Arch Linux
    LINUX ../vmlinuz-linux
    APPEND root=/dev/md1 ro md=0,/dev/sdb2,/dev/sdc2 md=1,/dev/sdb3,/dev/sdc3 md=2,/dev/sdb4,/dev/sdc4
    INITRD ../initramfs-linux.img
    any ideas?
    Last edited by whoop (2012-10-16 22:51:05)

    If I upgrade to linux 3.6 with this line:
    HOOKS="base udev autodetect pata scsi sata mdadm filesystems usbinput fsck"
    in /etc/mkinitcpio.conf, the system is able to boot.
    if I upfate to linux 3.6 with this line:
    HOOKS="base udev autodetect pata scsi sata mdadm_udev filesystems usbinput fsck"
    in /etc/mkinitcpio.conf the system is not able to boot.
    I gathered that the mdadm_udev hook was preferred but it seems to cause problems in this case.
    After I successfully upgrade (having "mdadm" in /mkinitcpio.conf) I can change "mdadm" to "mdadm_udev" and
    the system will still boot fine.
    Does somebody know what gives?
    Last edited by whoop (2012-10-16 00:13:07)

  • [Solved] - Root device not found - Unable to boot!

    Before posting links to other threads or to the pacman/mkinitcpio wiki page please go through the following.
    I know that many others are facing a similar problem, but I am posting this after spending 8+ hours (in 2 days) trying to get my system to boot.
    And worst of all I don't have a working CDROM so I have to boot via an iso on a pendrive which is very frustating.
    The exact message I get after the GRUB menu is:
    ERROR: resume: hibernation device '/dev/sda3' not found
    ERROR: Unable to find root device '/dev/disk/by-uuid/...'
    You are being dropped to a recovery shell.
    Type exit to try and continue booting
    Now I have already tried the following, by chrooting into my system:
    1. As per the pacman wiki page, boot via live arch, chroot and run full upgrade. Then reinstall udev followed by mkinitcpio and then remake the image.
    2. Downgrading to linux-3.3.4-2, udev-182-2x86-64 and mkinitcpio-0.8.8-1
    3. Rearranging hooks in mkinitcpio.conf (usbinput before udev), and adding ext4 to MODULES array. Done this in both downgraded version and new kernel version (3.3.8-1)
    After trying various permutations and combinations, I have failed and haven't been able to get past the first 8 lines after the grub menu.
    An important point to note:
    I had used the --force switch for 1 more package other than filesystem while updating which I don't remember now. I had to use it because some packages had gotten corrupted while downloading and I had to upgrade in parts. Also at no point during any of these trials did I get an error while rebuilding the initrd image.
    If I remove the resume hook in /etc/mkinitcpio.conf then the first line "ERROR: ... " changes  saying that "no hibernation device specified".
    Please suggest anything if you can!
    Last edited by theta (2012-06-15 15:44:15)

    ewaller wrote:
    Do you know the partition that is supposed to be your root partition?
    Grub cannot find it by its UUID.   Reboot, at the grub menu, highlight the kernel you want to boot, and press 'e'.  You are dropped into a simple editor which will allow you to change the boot command.  Replace references to /dev/disk/by-uuid/... with /dev/sdan, when n is the root partition number.
    One other possibility.  Does your system have multiple drives?  Any chance the BIOS could be swapping them ?  (On second thought, that would not break UUID, But... it is something to be aware of using the technique I proposed)
    If you do not know the partition arrangement, use that limited recover shell you mentioned to go look around and determine it.
    Hmm, Thanks for this advice but I can't help saying that I'm not a noob .
    Somehow the problem resolved itself with the new kernel update which came about half an hour ago (3.4.2-2). Suppose it will remain a mystery now!

  • [SOLVED]kexec into arch fails : root device not found

    Hello,
    I have a fresh arch install with only base, base-devel and openssh.
    I boot on penbuntu, at this point I can see my devices in /dev.
    Then I mount my root arch partition on /mnt/rootfs and do :
    kexec --load /mnt/rootfs/boot/vmlinuz-linux --initrd=/mnt/rootfs/boot/initramfs-linux.img --command-line="root=/dev/sda3 ro vesa video=vesafb"
    which returns :
    setup_linux_vesafb: 1280x720x32 @ 10028000 +708000
    I then do kexec -e, It seems to start loading the kernel since the screen is cleared and each time it does
    [0.845500] i8042: No controller found
    :: running early hook [udev]
    :: running hook [udev]
    :: Triggering uevents...
    Waiting 10 seconds for device /dev/sda3 ...
    ERROR: device '/dev/sda3' not found. Skipping fsck.
    ERROR: Unable to find root device '/dev/sda3' /
    You are being dropped to a recovery shell
    Type 'exit' to try and continue booting
    sh: can't access tty: job control turned off
    [rootfs /]#
    I tried everything as root in the kexec --command-line, root=LABEL, root=UUID but it always do exactly the same thing, waits for 10s for device and then ERROR and drops to the recovery shell.
    Any idea of what's going on ? Why can't it see devices ?
    EDIT : If that can help, the kernel from which I am kexecing is 2.6.24.3 and If I try to just chroot I notice :
    mount -t proc proc proc/
    mount -t sysfs sys sys/
    Works but when I :
    mount -o bind /dev dev/
    It returns :
    mount: mounting /dev on dev/ failed: Invalid argument
    So somehow I think when the kernel loads it has trouble passing the /dev along and therefore sees no devices. But I still can't figure out what to do.
    Thanks in advance
    Last edited by Nolhian (2012-07-28 17:47:30)

    I can't because I'm booting on penbuntu and not arch linux. Anyways the command used in the wiki is similar to the one I'm using.

Maybe you are looking for

  • Has anyone had a message come up on their iPad about icloud backup?

    Has anyone had a message come up on their iPad about icloud backup? The message on mine is"This iPad hasn't been backed up  in 3 weeks.Backups happen when this iPad is plugged in, locked, and connected to Wi-Fi."The message won't go away and the iPad

  • XML validation with DTD

    Hi Team, I want to validate the XML content with DTD refered in the XML. I have problem now is my DTD are present in a jar file. How do I need to set systemid to the input source so that it works. <!DOCTYPE test SYSTEM "test.dtd"> SAXParserFactory fa

  • Embedding a JFileChooser in a Panel

    is it possible to embed a file chooser in a JPanel?, i'm trying to get my program to look something like how CuteHTML does. Or should i just use a JTree to display the dirrectory, and contents?

  • After updates with  ios7 lost sound , did reset now I lost wifi, asking me password

    After updates now my wifi on iPad asking me for password

  • OSB Twitter REST Api notification!

    Hello, I need any help possible with the following: I am about to start working on a project that whenever there is a certain error in the database or errors in general that there will be a notification sent to twitter account where people following