Pogo hangs in boot loop after switching to systemd

This forum is for all other ARMv5 devices

Pogo hangs in boot loop after switching to systemd

Postby elzippo3480 » Mon Mar 04, 2013 8:27 pm

Hi,

my pogoplug with Arch Linux ARM hangs in a boot loop after switching to systemd.

i have installed it with
$this->bbcode_second_pass_code('', 'pacman -S systemd-sysvcompat')
and activate some deamons like sshd. But something went wrong and now i cant boot.

$this->bbcode_second_pass_code('', '
CE>> Stage-1 Bootloader XCE_STAGE1: 1.1: Tue Feb 8 01:40:26 PST 2011
Attempting to set PLLA to 700MHz ...
plla_ctrl0 : 0x0000000A
plla_ctrl1 : 0x000E0000
plla_ctrl2 : 0x001C01A0
plla_ctrl3 : 0x00000016
PLLA Set

Setup memory, testing
Reading NAND, Image 0
Hdr len: 0x0001C030
Hdr CRC: 0x39F6D832
OK


U-Boot 1.1.2 (Jul 29 2010 - 19:36:07)

U-Boot code: 60D00000 -> 60D1C030 BSS: -> 60D21800
RAM Configuration:
Bank #0: 60000000 128 MB
SRAM Configuration:
64KB at 0x50000000
NAND:128 MiB
In: serial
Out: serial
Err: serial
Setting Linux mem= boot arg value
Hit any key to stop autoboot: 0

Loading from device 0: 128MiB 3,3V 8-bit (offset 0x500000)
-- Using 1bit ECC style encoding
Image Name: Linux-2.6.31.6_SMP_820
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2345664 Bytes = 2.2 MB
Load Address: 60008000
Entry Point: 60008000
## Booting image at 60500000 ...
Image Name: Linux-2.6.31.6_SMP_820
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2345664 Bytes = 2.2 MB
Load Address: 60008000
Entry Point: 60008000
Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux.............................................................................................................................................. done, booting the kernel.
[ 0.000000] Linux version 2.6.31.6_SMP_820 (root@hunchback) (gcc version 4.7.0 20120505 (prerelease) (GCC) ) #7 SMP Thu Jun 14 20:31:06 CDT 2012
[ 0.000000] CPU: ARMv6-compatible processor [410fb025] revision 5 (ARMv7), cr=00c5387f
[ 0.000000] CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
[ 0.000000] Machine: Oxsemi NAS
[ 0.000000] 1 memory region
[ 0.000000] Ignoring unrecognised tag 0x00000000
[ 0.000000] Memory policy: ECC disabled, Data cache writealloc
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512
[ 0.000000] Kernel command line: root=/dev/sda1 ubi.mtd=2,512 rootfstype=ext3 console=ttyS0,115200 elevator=cfq mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 rootwait rw mem=128M poweroutage=yes
[ 0.000000] PID hash table entries: 512 (order: 9, 2048 bytes)
[ 0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.000000] Memory: 128MB = 128MB total
[ 0.000000] Memory: 125112KB available (4012K code, 316K data, 144K init, 0K highmem)
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] NR_IRQS:96
[ 0.000000] OX820_RPS_init_irq: interrupts 64 to 96
[ 0.010000] Console: colour dummy device 80x30
[ 0.010000] console [ttyS0] enabled
[ 0.020000] Calibrating delay loop... 279.34 BogoMIPS (lpj=1396736)
[ 0.260000] Security Framework initialized
[ 0.260000] Mount-cache hash table entries: 512
[ 0.270000] CPU: Testing write buffer coherency: ok
[ 0.270000] Calibrating local timer... 350.00MHz.
[ 0.340000] CPU1: Booted secondary processor
[ 0.440000] Calibrating delay loop... 279.34 BogoMIPS (lpj=1396736)
[ 0.670000] Brought up 2 CPUs
[ 0.680000] SMP: Total of 2 processors activated (558.69 BogoMIPS).
[ 0.690000] tmpfs: No value for mount option 'mode'
[ 0.690000] devtmpfs: initialized
[ 0.700000] NET: Registered protocol family 16
[ 0.700000] Number of DMA channels = 4, version = 4
[ 0.710000] Reserving a DMA channel for DirectRAID
[ 0.710000] Allocating 389 SRAM generic DMA descriptors
[ 1.220000] PCIeA version/deviceID 082510b5
[ 1.220000] PCIeB version/deviceID 082510b5
[ 4.250000] ox820_pci_preinit() PCIEB link up timeout (00001814)
[ 4.250000] ox820_pcie_setup_resources() Enabling PCIe Pre-Emphasis
[ 4.260000] ox820_pciea_setup_resources() resource c781b140
[ 4.260000] ox820_pciea_setup_resources() io: 0x4be00000 - 0x4befffff
[ 4.270000] ox820_pciea_setup_resources() non-pre: 0x48000000 - 0x49ffffff
[ 4.280000] ox820_pciea_setup_resources() pre: 0x4a000000 - 0x4bdfffff
[ 4.280000] PCI: bus0: Fast back to back transfers disabled
[ 4.290000] PCI: bus1: Fast back to back transfers enabled
[ 4.310000] bio: create slab <bio-0> at 0
[ 4.320000] SCSI subsystem initialized
[ 4.320000] usbcore: registered new interface driver usbfs
[ 4.330000] usbcore: registered new interface driver hub
[ 4.330000] usbcore: registered new device driver usb
[ 4.370000] NET: Registered protocol family 2
[ 4.370000] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 4.380000] Switched to NOHz mode on CPU #0
[ 4.380000] TCP established hash table entries: 4096 (order: 3, 32768 bytes)
[ 4.380000] Switched to NOHz mode on CPU #1
[ 4.390000] TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
[ 4.400000] TCP: Hash tables configured (established 4096 bind 4096)
[ 4.400000] TCP reno registered
[ 4.410000] NET: Registered protocol family 1
[ 4.410000] Create fragment cache
[ 4.440000] fuse init (API version 7.12)
[ 4.440000] msgmni has been set to 244
[ 4.450000] alg: No test for stdrng (krng)
[ 4.450000] io scheduler noop registered
[ 4.460000] io scheduler anticipatory registered
[ 4.460000] io scheduler deadline registered
[ 4.460000] io scheduler cfq registered (default)
[ 4.490000] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[ 4.500000] serial8250: ttyS0 at MMIO 0x44200000 (irq = 55) is a 16550A
[ 4.510000] brd: module loaded
[ 4.520000] loop: module loaded
[ 4.530000] ox820sata: OX820 sata core.
[ 4.530000] scsi0 : oxnassata
[ 4.540000] scsi1 : oxnassata
[ 4.540000] ata1: SATA max UDMA/133 irq 50
[ 4.540000] ata2: SATA max UDMA/133 irq 50
[ 4.550000] ox820sata: reseting SATA core
[ 4.910000] ata1: SATA link down (SStatus 0 SControl 300)
[ 4.910000] ox820sata: reseting SATA core
[ 5.270000] ata2: SATA link down (SStatus 0 SControl 300)
[ 5.270000] tun: Universal TUN/TAP device driver, 1.6
[ 5.280000] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[ 5.280000] NAND: Page read time 40ms
[ 5.290000] NAND device: Manufacturer ID: 0xad, Chip ID: 0xf1 (Hynix NAND 128MiB 3,3V 8-bit)
[ 5.300000] Scanning device for bad blocks
[ 5.340000] Bad eraseblock 604 at 0x000004b80000
[ 5.380000] Creating 2 MTD partitions on "NAND 128MiB 3,3V 8-bit":
[ 5.380000] 0x000000000000-0x000000e00000 : "boot"
[ 5.390000] 0x000000e00000-0x000008000000 : "rootfs"
[ 5.390000] UBI: attaching mtd2 to ubi0
[ 5.400000] UBI: physical eraseblock size: 131072 bytes (128 KiB)
[ 5.400000] UBI: logical eraseblock size: 129024 bytes
[ 5.410000] UBI: smallest flash I/O unit: 2048
[ 5.410000] UBI: sub-page size: 512
[ 5.420000] UBI: VID header offset: 512 (aligned 512)
[ 5.430000] UBI: data offset: 2048
[ 5.830000] UBI: attached mtd2 to ubi0
[ 5.840000] UBI: MTD device name: "rootfs"
[ 5.840000] UBI: MTD device size: 114 MiB
[ 5.850000] UBI: number of good PEBs: 911
[ 5.850000] UBI: number of bad PEBs: 1
[ 5.860000] UBI: max. allowed volumes: 128
[ 5.860000] UBI: wear-leveling threshold: 4096
[ 5.870000] UBI: number of internal volumes: 1
[ 5.870000] UBI: number of user volumes: 1
[ 5.870000] UBI: available PEBs: 0
[ 5.880000] UBI: total number of reserved PEBs: 911
[ 5.880000] UBI: number of PEBs reserved for bad PEB handling: 9
[ 5.890000] UBI: max/mean erase counter: 2/0
[ 5.890000] UBI: image sequence number: 0
[ 5.900000] UBI: background thread "ubi_bgt0d" started, PID 313
[ 5.900000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 5.900000] oxnas-ehci oxnas-ehci.0: OXNAS EHCI Host Controller
[ 5.900000] oxnas-ehci oxnas-ehci.0: new USB bus registered, assigned bus number 1
[ 5.930000] oxnas-ehci oxnas-ehci.0: irq 39, io mem 0x00000000
[ 5.950000] oxnas-ehci oxnas-ehci.0: USB 0.0 started, EHCI 1.00
[ 5.950000] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 5.960000] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 5.960000] usb usb1: Product: OXNAS EHCI Host Controller
[ 5.970000] usb usb1: Manufacturer: Linux 2.6.31.6_SMP_820 ehci_hcd
[ 5.980000] usb usb1: SerialNumber: usb
[ 5.980000] usb usb1: configuration #1 chosen from 1 choice
[ 5.990000] hub 1-0:1.0: USB hub found
[ 5.990000] hub 1-0:1.0: 2 ports detected
[ 6.000000] Initializing USB Mass Storage driver...
[ 6.000000] usbcore: registered new interface driver usb-storage
[ 6.010000] USB Mass Storage support registered.
[ 6.010000] usbcore: registered new interface driver libusual
[ 6.020000] mice: PS/2 mouse device common for all mice
[ 6.020000] usbcore: registered new interface driver hiddev
[ 6.030000] usbcore: registered new interface driver usbhid
[ 6.040000] usbhid: v2.6:USB HID core driver
[ 6.040000] TCP cubic registered
[ 6.040000] NET: Registered protocol family 10
[ 6.050000] lo: Disabled Privacy Extensions
[ 6.050000] NET: Registered protocol family 17
[ 6.060000] RPC: Registered udp transport module.
[ 6.060000] RPC: Registered tcp transport module.
[ 6.070000] Waiting for root device /dev/sda1...
[ 6.310000] usb 1-1: new high speed USB device using oxnas-ehci and address 2
[ 6.460000] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608
[ 6.460000] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 6.470000] usb 1-1: Product: USB2.0 Hub
[ 6.480000] usb 1-1: configuration #1 chosen from 1 choice
[ 6.480000] hub 1-1:1.0: USB hub found
[ 6.490000] hub 1-1:1.0: 4 ports detected
[ 6.770000] usb 1-1.1: new high speed USB device using oxnas-ehci and address 3
[ 6.880000] usb 1-1.1: New USB device found, idVendor=13fe, idProduct=1e23
[ 6.880000] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 6.890000] usb 1-1.1: Product: TDK Trans-it
[ 6.900000] usb 1-1.1: Manufacturer: TDK
[ 6.900000] usb 1-1.1: SerialNumber: 0700077A1A9417A8
[ 6.910000] usb 1-1.1: configuration #1 chosen from 1 choice
[ 6.910000] scsi2 : SCSI emulation for USB Mass Storage devices
[ 11.960000] scsi 2:0:0:0: Direct-Access TDK TDK Trans-it PMAP PQ: 0 ANSI: 0 CCS
[ 14.070000] sd 2:0:0:0: [sda] 4007936 512-byte logical blocks: (2.05 GB/1.91 GiB)
[ 14.080000] sd 2:0:0:0: [sda] Write Protect is off
[ 14.090000] sd 2:0:0:0: [sda] Assuming drive cache: write through
[ 14.100000] sd 2:0:0:0: [sda] Assuming drive cache: write through
[ 14.100000] sda: sda1
[ 14.170000] sd 2:0:0:0: [sda] Assuming drive cache: write through
[ 14.170000] sd 2:0:0:0: [sda] Attached SCSI removable disk
[ 18.050000] kjournald starting. Commit interval 5 seconds
[ 18.290000] EXT3 FS on sda1, internal journal
[ 18.290000] EXT3-fs: recovery complete.
[ 18.300000] EXT3-fs: mounted filesystem with writeback data mode.
[ 18.310000] VFS: Mounted root (ext3 filesystem) on device 8:1.
[ 18.320000] devtmpfs: mounted
[ 18.320000] Freeing init memory: 144K
[ 18.530000] <27>systemd[1]: Failed to enumerate cgroup controllers: No such file or directory
[ 18.540000] <30>systemd[1]: systemd 197 running in system mode. (+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ)

Welcome to Arch Linux ARM!

[ 18.590000] <27>systemd[1]: Failed to insert module 'autofs4'
[ 18.600000] <30>systemd[1]: Set hostname to <samba-nas>.
[ 18.610000] <28>systemd[1]: CONFIG_CGROUPS was not set when your kernel was compiled. Systems without control groups are not supported. We will now sleep for 10s, and then continue boot-up. Expect breakage and please do not file bugs. Instead fix your kernel and enable CONFIG_CGROUPS. Consult http://0pointer.de/blog/projects/cgroups-vs-cgroups.html for more information.
[ 28.650000] <28>systemd[1]: No control group support available, not creating root group.
[ 29.150000] <28>systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. See system logs and 'systemctl status display-manager.service' for details.
[ 29.170000] <30>systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
[ 29.180000] <30>systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[ 29.190000] <30>systemd[1]: Starting Syslog Socket.
[ OK ] Listening on Syslog Socket.
[ 29.220000] <30>systemd[1]: Listening on Syslog Socket.
[ 29.220000] <30>systemd[1]: Expecting device sys-subsystem-net-devices-eth0.device...
Expecting device sys-subsystem-net-devices-eth0.device...
[ 29.250000] <30>systemd[1]: Starting Remote File Systems.
[ OK ] Reached target Remote File Systems.
[ 29.270000] <30>systemd[1]: Reached target Remote File Systems.
[ 29.270000] <30>systemd[1]: Starting Delayed Shutdown Socket.
[ OK ] Listening on Delayed Shutdown Socket.
[ 29.300000] <30>systemd[1]: Listening on Delayed Shutdown Socket.
[ 29.300000] <30>systemd[1]: Starting LVM2 metadata daemon socket.
[ OK ] Listening on LVM2 metadata daemon socket.
[ 29.330000] <30>systemd[1]: Listening on LVM2 metadata daemon socket.
[ 29.330000] <30>systemd[1]: Starting Device-mapper event daemon FIFOs.
[ OK ] Listening on Device-mapper event daemon FIFOs.
[ 29.360000] <30>systemd[1]: Listening on Device-mapper event daemon FIFOs.
[ 29.360000] <30>systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
[ OK ] Listening on /dev/initctl Compatibility Named Pipe.
[ 29.400000] <30>systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[ 29.400000] <30>systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
[ 29.410000] <30>systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[ 29.420000] <30>systemd[1]: Starting Encrypted Volumes.
[ OK ] Reached target Encrypted Volumes.
[ 29.450000] <30>systemd[1]: Reached target Encrypted Volumes.
[ 29.450000] <30>systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[ 29.460000] <30>systemd[1]: Starting udev Kernel Socket.
[ OK ] Listening on udev Kernel Socket.
[ 29.490000] <30>systemd[1]: Listening on udev Kernel Socket.
[ 29.490000] <30>systemd[1]: Starting udev Control Socket.
[ OK ] Listening on udev Control Socket.
[ 29.520000] <30>systemd[1]: Listening on udev Control Socket.
[ 29.520000] <30>systemd[1]: Starting Swap.
[ OK ] Reached target Swap.
[ 29.550000] <30>systemd[1]: Reached target Swap.
[ 29.550000] <30>systemd[1]: Starting Journal Socket.
[ OK ] Listening on Journal Socket.
[ 29.580000] <30>systemd[1]: Listening on Journal Socket.
[ 29.580000] <30>systemd[1]: Started File System Check on Root Device.
[ 29.590000] <30>systemd[1]: Mounting Temporary Directory...
Mounting Temporary Directory...
[ 29.620000] <30>systemd[1]: Started Set Up Additional Binary Formats.
[ 29.630000] <30>systemd[1]: Mounted Huge Pages File System.
[ 29.640000] <30>systemd[1]: Starting Apply Kernel Variables...
Starting Apply Kernel Variables...
[ 29.670000] <30>systemd[1]: Mounted POSIX Message Queue File System.
[ 29.670000] <30>systemd[1]: Starting udev Kernel Device Manager...
Starting udev Kernel Device Manager...
[ 29.700000] <30>systemd[1]: Starting Setup Virtual Console...
Starting Setup Virtual Console...
[ 29.730000] <30>systemd[1]: Starting udev Coldplug all Devices...
Starting udev Coldplug all Devices...
[ 29.760000] <30>systemd[1]: Started Load Kernel Modules.
[ 29.770000] <30>systemd[1]: Mounted Configuration File System.
[ 29.770000] <30>systemd[1]: Mounting FUSE Control File System...
Mounting FUSE Control File System...
[ 29.800000] <30>systemd[1]: Mounted Debug File System.
[ 29.800000] <30>systemd[1]: Starting Journal Service...
Starting Journal Service...
[ OK ] Started Journal Service.
[ 29.850000] <30>systemd[1]: Started Journal Service.
[ 29.850000] <30>systemd[1]: Starting Syslog.
[ OK ] Reached target Syslog.
[ 29.880000] <30>systemd[1]: Reached target Syslog.
[ 29.880000] <30>systemd[1]: Starting Remount Root and Kernel File Systems...
Starting Remount Root and Kernel File Systems...
[ 29.910000] <29>systemd[1]: tmp.mount mount process exited, code=exited status=213
[FAILED] Failed to mount Temporary Directory.
See 'systemctl status tmp.mount' for details.
[ 29.960000] <27>systemd[1]: Failed to mount Temporary Directory.
[ 29.960000] <29>systemd[1]: Unit tmp.mount entered failed state
[ 29.970000] <29>systemd[1]: systemd-sysctl.service: main process exited, code=exited, status=213/SECUREBITS
[FAILED] Failed to start Apply Kernel Variables.
See 'systemctl status systemd-sysctl.service' for details.
[ 30.020000] <27>systemd[1]: Failed to start Apply Kernel Variables.
[ 30.020000] <29>systemd[1]: Unit systemd-sysctl.service entered failed state
[ 30.030000] <29>systemd[1]: systemd-udevd.service: main process exited, code=exited, status=206/OOM_ADJUST
[FAILED] Failed to start udev Kernel Device Manager.
See 'systemctl status systemd-udevd.service' for details.
[ 30.080000] <27>systemd[1]: Failed to start udev Kernel Device Manager.
[ 30.080000] <29>systemd[1]: Unit systemd-udevd.service entered failed state
[ 30.090000] <29>systemd[1]: systemd-vconsole-setup.service: main process exited, code=exited, status=213/SECUREBITS
[FAILED] Failed to start Setup Virtual Console.
See 'systemctl status systemd-vconsole-setup.service' for details.
[ 30.140000] <27>systemd[1]: Failed to start Setup Virtual Console.
[ 30.140000] <29>systemd[1]: Unit systemd-vconsole-setup.service entered failed state
[ 30.150000] <29>systemd[1]: systemd-udev-trigger.service: main process exited, code=exited, status=213/SECUREBITS
[FAILED] Failed to start udev Coldplug all Devices.
See 'systemctl status systemd-udev-trigger.service' for details.
[ 30.200000] <27>systemd[1]: Failed to start udev Coldplug all Devices.
[ 30.200000] <29>systemd[1]: Unit systemd-udev-trigger.service entered failed state
[ 30.210000] <29>systemd[1]: sys-fs-fuse-connections.mount mount process exited, code=exited status=213
[FAILED] Failed to mount FUSE Control File System.
See 'systemctl status sys-fs-fuse-connections.mount' for details.
[ 30.260000] <27>systemd[1]: Failed to mount FUSE Control File System.
[ 30.260000] <29>systemd[1]: Unit sys-fs-fuse-connections.mount entered failed state
[ 30.270000] <29>systemd[1]: systemd-journald.service: main process exited, code=exited, status=218/CAPABILITIES
[ 30.280000] <29>systemd[1]: Unit systemd-journald.service entered failed state
[ 30.290000] <29>systemd[1]: systemd-remount-fs.service: main process exited, code=exited, status=213/SECUREBITS
[FAILED] Failed to start Remount Root and Kernel File Systems.
See 'systemctl status systemd-remount-fs.service' for details.
[ 30.340000] <27>systemd[1]: Failed to start Remount Root and Kernel File Systems.
[ 30.340000] <29>systemd[1]: Unit systemd-remount-fs.service entered failed state
[ 30.350000] <30>systemd[1]: Starting Local File Systems (Pre).
[ OK ] Reached target Local File Systems (Pre).
[ 30.380000] <30>systemd[1]: Reached target Local File Systems (Pre).
[ 30.380000] <30>systemd[1]: Starting Load Random Seed...
Starting Load Random Seed...
[ 30.410000] <30>systemd[1]: Starting Local File Systems.
[ OK ] Reached target Local File Systems.
[ 30.440000] <30>systemd[1]: Reached target Local File Systems.
[ 30.440000] <30>systemd[1]: Starting Recreate Volatile Files and Directories...
Starting Recreate Volatile Files and Directories...
[ 30.480000] <30>systemd[1]: Starting Trigger Flushing of Journal to Persistent Storage...
Starting Trigger Flushing of Journal to Persistent Storage...
[ 30.510000] <29>systemd[1]: systemd-random-seed-load.service: main process exited, code=exited, status=213/SECUREBITS
[FAILED] Failed to start Load Random Seed.
See 'systemctl status systemd-random-seed-load.service' for details.
[ 30.560000] <27>systemd[1]: Failed to start Load Random Seed.
[ 30.560000] <29>systemd[1]: Unit systemd-random-seed-load.service entered failed state
[ 30.570000] <29>systemd[1]: systemd-tmpfiles-setup.service: main process exited, code=exited, status=213/SECUREBITS
[FAILED] Failed to start Recreate Volatile Files and Directories.
See 'systemctl status systemd-tmpfiles-setup.service' for details.
[ 30.630000] <27>systemd[1]: Failed to start Recreate Volatile Files and Directories.
[ 30.630000] <29>systemd[1]: Unit systemd-tmpfiles-setup.service entered failed state
[ 30.640000] <29>systemd[1]: systemd-journal-flush.service: main process exited, code=exited, status=213/SECUREBITS
[FAILED] Failed to start Trigger Flushing of Journal to Persistent Storage.
See 'systemctl status systemd-journal-flush.service' for details.
[ 30.700000] <27>systemd[1]: Failed to start Trigger Flushing of Journal to Persistent Storage.
[ 30.700000] <29>systemd[1]: Unit systemd-journal-flush.service entered failed state
[ 30.710000] <30>systemd[1]: Starting System Initialization.
[ OK ] Reached target System Initialization.
[ 30.740000] <30>systemd[1]: Reached target System Initialization.
[ 30.740000] <30>systemd[1]: Starting D-Bus System Message Bus Socket.
[ OK ] Listening on D-Bus System Message Bus Socket.
[ 30.770000] <30>systemd[1]: Listening on D-Bus System Message Bus Socket.
[ 30.770000] <30>systemd[1]: Starting Sockets.
[[ 30.800000] <30>systemd[1]: Reached target Sockets.
[ 30.800000] <30>systemd[1]: Starting Daily Cleanup of Temporary Directories.
[ 30.810000] <30>systemd[1]: Started Daily Cleanup of Temporary Directories.
[ 30.810000] <30>systemd[1]: Starting Basic System.
[ OK ] Reached target Basic System.
[ 30.840000] <30>systemd[1]: Reached target Basic System.
[ 30.840000] <30>systemd[1]: Started SSH Key Generation.
[ 30.850000] <30>systemd[1]: Starting OpenSSH Daemon...
Starting OpenSSH Daemon...
[ OK ] Started OpenSSH Daemon.
[ 30.900000] <30>systemd[1]: Started OpenSSH Daemon.
[ 30.900000] <30>systemd[1]: Starting LEGACY unit for "set-oxnas-mac" rc script...
Starting LEGACY unit for "set-oxnas-mac" rc script...
[ 30.930000] <30>systemd[1]: Starting Login Service...
Starting Login Service...
[ 30.950000] <30>systemd[1]: Starting /etc/rc.local Compatibility...
Starting /etc/rc.local Compatibility...
[ 30.980000] <30>systemd[1]: Starting D-Bus System Message Bus...
Starting D-Bus System Message Bu[ 30.990000] <30>s...
[ systemdOK ] Starte[1]: d D-Bus System MStarted D-Bus System Message Bus.essage Bus.

[ 31.000000] <30>systemd[1]: Starting System Logger Daemon...
Starting System Logger Daemon...[ 31.010000] <30>
[ OK systemd] Started Sy[1]: stem Logger DaemStarted System Logger Daemon.on.

[ 31.020000] <30>systemd[1]: Starting Permit User Sessions...
Starting Permit User Sessions...[ 31.030000] <30>
systemd[1]: systemd-udevd.service holdoff time over, scheduling restart.
[ 31.040000] <30>systemd[1]: Stopping udev Kernel Device Manager...
Stopping udev Ke[ 31.040000] <30>rnel Device Manasystemdger...
[[1]: OK ] StopStarting udev Kernel Device Manager...ped udev Kernel
Device Manager.
Starti[ 31.060000] <30>ng udev Kernel Dsystemdevice Manager...[1]:
systemd-journald.service holdoff time over, scheduling restart.
[ OK 31.070000] <30>m] Stopped Triggsystemder Flushing of J[1]: ournal to PersisStopping Journal Service...tent Storage.

[ 31.080000] <30>Stopping Journalsystemd Service...
[1]: 1;32m OK ]Starting Journal Service... Stopped Journal
Service.
Starting Journal Servic[ 31.100000] <30>e...
[ systemdOK ] Starte[1]: d Journal ServicStarted Journal Service.e.

[ 31.110000] <30>systemd[1]: Starting Trigger Flushing of Journal to Persistent Storage...
Starting Trigger Flushing of Jou[ 31.120000] <29>rnal to Persistesystemdnt Storage...
[1]: sshd.service: main process exited, code=exited, status=213/SECUREBITS
[ 31.130000] <29>systemd[1]: Unit sshd.service entered failed state
[ 31.140000] <29>systemd[1]: set-oxnas-mac.service: control process exited, code=exited status=213
[FAILED 31.150000] <27>m] Failed to stasystemdrt LEGACY unit f[1]: or "set-oxnas-maFailed to start LEGACY unit for "set-oxnas-mac" rc script.c" rc script.
S
ee 'systemctl st[ 31.160000] <29>atus set-oxnas-msystemdac.service' for [1]: details.
Unit set-oxnas-mac.service entered failed state
[ 31.180000] <29>systemd[1]: systemd-logind.service: main process exited, code=exited, status=218/CAPABILITIES
[FAILED 31.190000] <27>m] Failed to stasystemdrt Login Service[1]: .
See 'systemctFailed to start Login Service.l status systemd
-logind.service'[ 31.200000] <29> for details.
systemd[1]: Unit systemd-logind.service entered failed state
[ 31.210000] <29>systemd[1]: dbus.service: main process exited, code=exited, status=206/OOM_ADJUST
[ 31.220000] <29>systemd[1]: Unit dbus.service entered failed state
[ 31.220000] <29>systemd[1]: syslog-ng.service: main process exited, code=exited, status=213/SECUREBITS
[ 31.230000] <29>systemd[1]: Unit syslog-ng.service entered failed state
[ 31.240000] <29>systemd[1]: systemd-user-sessions.service: main process exited, code=exited, status=213/SECUREBITS
[FAILED 31.250000] <27>m] Failed to stasystemdrt Permit User S[1]: essions.
See 'sFailed to start Permit User Sessions.ystemctl status
systemd-user-ses[ 31.260000] <29>sions.service' fsystemdor details.
[1]: Unit systemd-user-sessions.service entered failed state
[ 31.280000] <29>systemd[1]: systemd-udevd.service: main process exited, code=exited, status=206/OOM_ADJUST
[FAILED 31.290000] <27>m] Failed to stasystemdrt udev Kernel D[1]: evice Manager.
Failed to start udev Kernel Device Manager.See 'systemctl s
tatus systemd-ud[ 31.300000] <29>evd.service' forsystemd details.
[1]: Unit systemd-udevd.service entered failed state
[ 31.310000] <29>systemd[1]: systemd-journald.service: main process exited, code=exited, status=218/CAPABILITIES
[ 31.320000] <29>systemd[1]: Unit systemd-journald.service entered failed state
[ 31.330000] <29>systemd[1]: systemd-journal-flush.service: main process exited, code=exited, status=213/SECUREBITS
[FAILED 31.340000] <27>m] Failed to stasystemd[1]: Failed to start Trigger Flushing of Journal to Persistent Storage.
[ 31.350000] <29>systemd[1]: Unit systemd-journal-flush.service entered failed state
[ 31.360000] <29>systemd[1]: rc-local.service: main process exited, code=exited, status=213/SECUREBITS
[FAILED] Failed to start /etc/rc.local Compatibility.
See 'systemctl status rc-local.service' for details.
[ 31.410000] <27>systemd[1]: Failed to start /etc/rc.local Compatibility.
[ 31.410000] <29>systemd[1]: Unit rc-local.service entered failed state
[ 31.420000] <30>systemd[1]: Starting Getty on tty1...
Starting Getty on tty1...
[ OK ] Started Getty on tty1.
')

and then it loops endless with

$this->bbcode_second_pass_code('', '[ 81.970000] <27>systemd[1]: Failed to start Journal Service.
[ 81.970000] <30>systemd[1]: Starting D-Bus System Message Bus...
Starting D-Bus System Message Bus...
[ 82.000000] <28>systemd[1]: dbus.service start request repeated too quickly, refusing to start.
[FAILED] Failed to start D-Bus System Message Bus.
See 'systemctl status dbus.service' for details.
[ 82.050000] <27>systemd[1]: Failed to start D-Bus System Message Bus.
[ 82.050000] <30>systemd[1]: Starting Journal Service...
Starting Journal Service...
[ 82.080000] <28>systemd[1]: systemd-journald.service start request repeated too quickly, refusing to start.
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ 82.130000] <27>systemd[1]: Failed to start Journal Service.
[ 82.130000] <30>systemd[1]: Starting D-Bus System Message Bus...
Starting D-Bus System Message Bus...
[ 82.160000] <28>systemd[1]: dbus.service start request repeated too quickly, refusing to start.
[FAILED] Failed to start D-Bus System Message Bus.
See 'systemctl status dbus.service' for details.
[ 82.210000] <27>systemd[1]: Failed to start D-Bus System Message Bus.
[ 82.210000] <30>systemd[1]: Starting Journal Service...
Starting Journal Service...
[ 82.240000] <28>systemd[1]: systemd-journald.service start request repeated too quickly, refusing to start.
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ 82.290000] <27>systemd[1]: Failed to start Journal Service.
[ 82.290000] <30>systemd[1]: Starting D-Bus System Message Bus...
')

What can i do? i have no idea anymore.
elzippo3480
 
Posts: 5
Joined: Mon Mar 04, 2013 8:18 pm

Re: Pogo hangs in boot loop after switching to systemd

Postby Geoff » Mon Mar 04, 2013 9:13 pm

In addition to trying the suggestions in this thread, you may have to edit the "src" stanza in /etc/syslog-ng/syslog-ng.conf
$this->bbcode_second_pass_code('', '
source src {
# unix-dgram("/run/systemd/journal/syslog");
unix-dgram("/dev/log");
internal();
file("/proc/kmsg");
};')
Geoff
 
Posts: 231
Joined: Wed Mar 09, 2011 5:14 pm

Re: Pogo hangs in boot loop after switching to systemd

Postby WarheadsSE » Mon Mar 04, 2013 9:21 pm

Then there is the whole, kernel doesn't support necessary c-groups & journal requirements flat "DON'T TRY THIS" warning...
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: Pogo hangs in boot loop after switching to systemd

Postby elzippo3480 » Mon Mar 04, 2013 10:40 pm

Hi WarheadSE,

in the Thread Geoff had linked you said "My latest oxnas rootfs is NOT made for systemd." would it be better to turn back to sysVInit? And how could i do this?
elzippo3480
 
Posts: 5
Joined: Mon Mar 04, 2013 8:18 pm

Re: Pogo hangs in boot loop after switching to systemd

Postby elzippo3480 » Mon Mar 04, 2013 10:55 pm

Hi Geoff, Thannks for your help.

My /etc/syslog-ng/syslog-ng.conf looks like your post. What i have to modify in the source?
elzippo3480
 
Posts: 5
Joined: Mon Mar 04, 2013 8:18 pm

Re: Pogo hangs in boot loop after switching to systemd

Postby Geoff » Mon Mar 04, 2013 11:19 pm

You won't be able to boot up unless initscripts, sysvinit and sysvinit-tools are installed and configured properly, AFAIK. If you have another bootable Arch system (e.g., a backup), you may be able to find a way to reinstall these. After that, reconfiguring the initscripts could be tricky. If you can't get all this to work, you'll just have to start over from a system tarball.
Geoff
 
Posts: 231
Joined: Wed Mar 09, 2011 5:14 pm

Re: Pogo hangs in boot loop after switching to systemd

Postby elzippo3480 » Tue Mar 05, 2013 8:11 am

Hi @all,

this was a new installation i did yesterday. For me its no problem to do a new fresh installation. But i dont know how because i have no ssh access?
elzippo3480
 
Posts: 5
Joined: Mon Mar 04, 2013 8:18 pm

Re: Pogo hangs in boot loop after switching to systemd

Postby Geoff » Tue Mar 05, 2013 3:55 pm

The installation instructions have a section with the title "Help! It stopped working!" Just follow the instructions there, and you'll have your fresh installation back.
Geoff
 
Posts: 231
Joined: Wed Mar 09, 2011 5:14 pm

Re: Pogo hangs in boot loop after switching to systemd

Postby elzippo3480 » Tue Mar 05, 2013 7:53 pm

Live could be so easy :P

now i have a working env with initscript and have startet samba wtih /etc/rc.d/samba startup script.

THX to all
elzippo3480
 
Posts: 5
Joined: Mon Mar 04, 2013 8:18 pm


Return to Community Supported

Who is online

Users browsing this forum: No registered users and 9 guests