Upadte broke something in systemd?

[Ethereal]

I did an install of parted and a system update and now my boot is borked. Here's what I updated:
$this->bbcode_second_pass_code('', '[root@alarm ~]# pacman -Suy parted
:: Synchronizing package databases...
core 40.6 KiB 252K/s 00:00 [######################################################] 100%
extra 453.4 KiB 679K/s 00:01 [######################################################] 100%
community 467.4 KiB 555K/s 00:01 [######################################################] 100%
alarm 5.0 KiB 101K/s 00:00 [######################################################] 100%
aur is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...
:: systemd and nss-myhostname are in conflict. Remove nss-myhostname? [y/N] y

Targets (8): iputils-20121221-1 kbd-1.15.5-2 nss-myhostname-0.3-3 [removal] pambase-20130113-1 shadow-4.1.5.1-3 systemd-197-4
systemd-sysvcompat-197-4 parted-3.1-1

Total Download Size: 4.09 MiB
Total Installed Size: 23.68 MiB
Net Upgrade Size: 2.57 MiB

Proceed with installation? [Y/n]
:: Retrieving packages from core...
iputils-20121221-1-arm 68.7 KiB 316K/s 00:00 [######################################################] 100%
kbd-1.15.5-2-arm 1015.8 KiB 694K/s 00:01 [######################################################] 100%
pambase-20130113-1-any 1016.0 B 6.92M/s 00:00 [######################################################] 100%
shadow-4.1.5.1-3-arm 999.3 KiB 325K/s 00:03 [######################################################] 100%
systemd-197-4-arm 1679.9 KiB 805K/s 00:02 [######################################################] 100%
systemd-sysvcompat-197-4-arm 5.3 KiB 2.17M/s 00:00 [######################################################] 100%
:: Retrieving packages from extra...
parted-3.1-1-arm 418.8 KiB 575K/s 00:01 [######################################################] 100%
(7/7) checking package integrity [######################################################] 100%
(7/7) loading package files [######################################################] 100%
(7/7) checking for file conflicts [######################################################] 100%
(8/8) checking available disk space [######################################################] 100%
(1/1) removing nss-myhostname [######################################################] 100%
(1/7) installing parted [######################################################] 100%
(2/7) upgrading iputils [######################################################] 100%
(3/7) upgrading kbd [######################################################] 100%
(4/7) upgrading pambase [######################################################] 100%
(5/7) upgrading shadow [######################################################] 100%
(6/7) upgrading systemd [######################################################] 100%
==> Persistent net naming rules have been shipped as disabled.
See /etc/udev/rules.d/80-net-name-slot.rules for more detail
(7/7) upgrading systemd-sysvcompat [######################################################] 100%
')
Should I perhaps not have said yes to remove nss-myhostname?

Netconsole log:
$this->bbcode_second_pass_code('', '...
[ 11.082644] netconsole: remote port 6666
[ 11.086584] netconsole: remote IP 10.0.1.119
[ 11.090952] netconsole: remote ethernet address 08:00:27:15:e8:06
[ 11.097132] netconsole: device eth0 not up yet, forcing it
[ 11.106912] scsi0 : usb-storage 1-1.1:1.0
[ 12.104642] scsi 0:0:0:0: Direct-Access Generic- SD/MMC 1.00 PQ: 0 ANSI: 0 CCS
[ 12.113964] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 12.864759] mv643xx_eth_port mv643xx_eth_port.0: eth0: link up, 100 Mb/s, full duplex, flow control disabled
[ 12.883217] console [netcon0] enabled
[ 12.886988] netconsole: network logging started
[ 12.891626] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[ 12.927827] sd 0:0:0:0: [sda] 3862528 512-byte logical blocks: (1.97 GB/1.84 GiB)
[ 12.936065] sd 0:0:0:0: [sda] Write Protect is off
[ 12.941565] sd 0:0:0:0: [sda] No Caching mode page present
[ 12.947268] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 12.956314] sd 0:0:0:0: [sda] No Caching mode page present
[ 12.961854] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 12.970881] sda: sda1
[ 12.975940] sd 0:0:0:0: [sda] No Caching mode page present
[ 12.981474] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 12.987792] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 12.993891] Freeing init memory: 172K
[ 13.046879] systemd-udevd[46]: starting version 196
')

So it says starting version 196, but the update installed version 197.4! Any ideas here? TIA

[Ethereal]

Well, I just pulled my usb drive out and did e2fsck on it; found some errors and that seemed to fix it. Any idea what might be the cause of something like that and/or how to prevent it? Is it possible to have uboot run fsck on my device on boot?

[moonman]

use ext3

[Ethereal]

$this->bbcode_second_pass_quote('moonman', 'u')se ext3

[Ethereal]

So I tried touching /forcefsck but that didn't actually do anything. I do see this odd message during boot, every time:
$this->bbcode_second_pass_code('', 'systemd-journald[86]: File /var/log/journal/5c49cb5bf08724338eb09a6900092bb0/system.journal corrupted or uncleanly shut down, renaming and replacing.
')

That doesn't look normal. Could I have a permanantly corrupted drive?

[moonman]

There's no initrd so fsck at boot won't work. Unless you actually get initrd and change fstab so it knows to check the rootfs

[Ethereal]

$this->bbcode_second_pass_quote('moonman', 'T')here's no initrd so fsck at boot won't work. Unless you actually get initrd and change fstab so it knows to check the rootfs

[moonman]

Keep in mind initrd is generic, for the plugs uou need uInitrd