Cannot boot into GoFlex ALARM

[viralbug]

I've been using Arch on my GoFlex for a little while now without any problems. I was trying to setup CUPS for my printer. I'm not sure what changes I've made, but I rebooted the GoFlex and no longer could connect to it. It does not receive an IP address, nothing shows up in my DHCP.

Here's what netconsole shows:

U-Boot
$this->bbcode_second_pass_code('', 'U-Boot 2010.09 (Feb 16 2011 - 18:44:23)
UBIT v0.6 by Jeff Doozan and Peter Carmichael
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 1 USB Device(s) found
scanning bus for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot: 0
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:fast", error -19
Error reading superblock on volume 'ubi:fast'!
UBIFS not mounted, use ubifs mount to mount volume first!
** Block device usb 0 not supported
** Block device usb 0 not supported

** Invalid boot device **

** Invalid boot device **
** Block device usb 1 not supported
** Block device usb 1 not supported

** Invalid boot device **

** Invalid boot device **
** Block device usb 2 not supported
** Block device usb 2 not supported

** Invalid boot device **

** Invalid boot device **
** Block device usb 3 not supported
** Block device usb 3 not supported

** Invalid boot device **

** Invalid boot device **

Reset IDE: Bus 0: OK Bus 1: not available
Device 0: Model: WDC WD10EADS-00L5B1 Firm: 01.01A01 Ser#: WD-############
Type: Hard Disk
Supports 48-bit addressing
Capacity: 953869.7 MB = 931.5 GB (1953525168 x 512)
Loading file "/boot/uImage" from ide device 0:1 (hda1)
2869736 bytes read
Loading file "/uInitrd" from ide device 0:1 (hda1)
** File not found /uInitrd
Loading file "/boot/uInitrd" from ide device 0:1 (hda1)
** File not found /boot/uInitrd
## Booting kernel from Legacy Image at 00680000 ...
Image Name: Linux-3.1.10-16-ARCH
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2869672 Bytes = 2.7 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...')

Kernel
$this->bbcode_second_pass_code('', '[ 13.599799] systemd[1]: Failed to mount Temporary Directory.
[ 13.799800] systemd[1]: Failed to mount POSIX Message Queue File System.
[ 13.879711] systemd[1]: Failed to mount Debug File System.
[ 14.989659] systemd[1]: Failed to mount /mnt/NAS.
[ 15.009646] systemd[1]: Dependency failed for Local File Systems.
[ 16.401006] systemd-udevd[112]: worker [134] did not accept message -1 (Connection refused), kill it
[ 16.410345] systemd-udevd[112]: worker [135] did not accept message -1 (Connection refused), kill it
[ 16.433773] systemd-udevd[112]: worker [138] did not accept message -1 (Connection refused), kill it
[ 17.775920] systemd-udevd[161]: worker [182] did not accept message -1 (Connection refused), kill it
[ 17.785270] systemd-udevd[161]: worker [183] did not accept message -1 (Connection refused), kill it
[ 17.823612] systemd-udevd[161]: worker [188] did not accept message -1 (Connection refused), kill it
[ 19.217239] systemd-udevd[214]: worker [233] did not accept message -1 (Connection refused), kill it
[ 19.227381] systemd-udevd[214]: worker [234] did not accept message -1 (Connection refused), kill it
[ 19.236689] systemd-udevd[214]: worker [235] did not accept message -1 (Connection refused), kill it
[ 19.275285] systemd-udevd[214]: worker [244] did not accept message -1 (Connection refused), kill it
[ 19.300054] systemd-udevd[214]: worker [248] did not accept message -1 (Connection refused), kill it
[ 19.309342] systemd-udevd[214]: worker [249] did not accept message -1 (Connection refused), kill it
[ 20.653935] systemd-udevd[270]: worker [290] did not accept message -1 (Connection refused), kill it
[ 20.665237] systemd-udevd[270]: worker [291] did not accept message -1 (Connection refused), kill it
[ 20.674555] systemd-udevd[270]: worker [292] did not accept message -1 (Connection refused), kill it
[ 20.704285] systemd-udevd[270]: worker [298] did not accept message -1 (Connection refused), kill it
[ 20.719797] systemd-udevd[270]: worker [301] did not accept message -1 (Connection refused), kill it
[ 22.145301] systemd-udevd[322]: worker [341] did not accept message -1 (Connection refused), kill it
[ 22.160750] systemd-udevd[322]: worker [342] did not accept message -1 (Connection refused), kill it
[ 22.180852] systemd-udevd[322]: worker [345] did not accept message -1 (Connection refused), kill it
[ 22.220098] systemd-udevd[322]: worker [350] did not accept message -1 (Connection refused), kill it
[ 22.229386] systemd-udevd[322]: worker [355] did not accept message -1 (Connection refused), kill it
[ 22.370640] systemd[1]: Failed to start Journal Service.
[ 22.380239] systemd[1]: Failed to start Journal Service.
[ 22.386459] systemd[1]: Failed to start Journal Service.
[ 22.397384] systemd[1]: Failed to start Journal Service.
[ 22.485189] systemd[1]: Failed to start Journal Service.
[ 22.492621] systemd[1]: Failed to start Journal Service.
[ 22.501026] systemd[1]: Failed to start Journal Service.
[ 22.509097] systemd[1]: Failed to start Journal Service.
[ 22.517392] systemd[1]: Failed to start Journal Service.
[ 22.524816] systemd[1]: Failed to start Journal Service.
[ 22.532366] systemd[1]: Failed to start Journal Service.
[ 22.538196] systemd[1]: Failed to start Journal Service.
[ 22.544059] systemd[1]: Failed to start Journal Service.
[ 22.550152] systemd[1]: Failed to start Journal Service.
[ 22.631103] systemd[1]: Failed to start Journal Service.
[ 22.637300] systemd[1]: Failed to start Journal Service.
[ 22.649440] systemd[1]: Failed to start Journal Service.
[ 22.698413] systemd[1]: Failed to start Journal Service.
[ 22.704971] systemd[1]: Failed to start Journal Service.
[ 22.711956] systemd[1]: Failed to start Journal Service.
[ 22.719381] systemd[1]: Failed to start Journal Service.
[ 22.726806] systemd[1]: Failed to start Journal Service.
[ 22.739464] systemd[1]: Failed to start Journal Service.
[ 22.791447] systemd[1]: Failed to start Setup Virtual Console.
[ 22.831484] systemd[1]: Failed to start Journal Service.
[ 22.836924] systemd[1]: Dependency failed for Trigger Flushing of Journal to Persistent Storage.
[ 22.850827] systemd[1]: Failed to start Apply Kernel Variables.
[ 22.859987] systemd[1]: Failed to start udev Coldplug all Devices.
[ 22.866885] systemd[1]: Failed to start udev Kernel Device Manager.
[ 22.956411] systemd[1]: Failed to start Journal Service.
[ 22.999641] systemd[1]: Failed to mount Debug File System.
[ 23.039629] systemd[1]: Failed to mount POSIX Message Queue File System.
[ 23.079628] systemd[1]: Failed to mount Temporary Directory.
[ 23.161326] systemd[1]: Failed to start Load Random Seed.
[ 23.167744] systemd[1]: Failed to start Journal Service.
[ 23.299630] systemd[1]: Failed to mount /mnt/NAS.
[ 23.304462] systemd[1]: Dependency failed for Local File Systems.
[ 23.319303] systemd[1]: Failed to start Emergency Shell.
[ 23.324775] systemd[1]: Dependency failed for Emergency Mode.
[ 23.333267] systemd[1]: Failed to start Journal Service.
[ 23.339914] systemd[1]: Failed to start Journal Service.
[ 23.346361] systemd[1]: Failed to start Journal Service.
[ 23.353606] systemd[1]: Failed to start Journal Service.
[ 23.361205] systemd[1]: Failed to start Journal Service.
[ 23.368921] systemd[1]: Failed to start Journal Service.
[ 23.376505] systemd[1]: Failed to start Journal Service.
[ 23.383986] systemd[1]: Failed to start Journal Service.
[ 23.391213] systemd[1]: Failed to start Journal Service.
[ 23.398350] systemd[1]: Failed to start Journal Service.
[ 23.404903] systemd[1]: Failed to start Journal Service.
[ 23.410986] systemd[1]: Failed to start Journal Service.
[ 23.416818] systemd[1]: Failed to start Journal Service.
')

How should I go about restoring it? I don't want to reinstall the OS nor lose my data.

[moonman]

Do you have another device to chroot from? something is wrong as it can't mount anything for some reason. Are all the drives attached that you had attached before (particularly the ones that you have in fstab)?

[viralbug]

I only had my SATA drive connected to the GoFlex before I was trying to connect my printer via USB, no other drive.
I can use a USB pendrive and possibly boot from it. I'll work on making one now.
EDIT: I have ALARM installed and booted from a USB drive. Unfortunately, I'm not aware of how to proceed further. I'll keep searching though.

[viralbug]

Any pointers on what I should do? My limited linux knowledge doesn't get me anywhere.

[viralbug]

Ok so after messing around with the bootloader and stuff, I finally found the problem.
I dunno why suddenly this issue came up coz this is how I was using the system until now.
To give you an idea, I have a 1tb hard drive connected to the SATA port. It is divided in 2 partitions, first being the OS and the remaining is being used as a NAS. The second partition is being mounted as /mnt/NAS. This is what my fstab looks like

$this->bbcode_second_pass_code('', '#
# /etc/fstab: static file system information
#
# <file system> <dir> <type> <options> <dump> <pass>
/dev/sda2 /mnt/NAS ext4 defaults 0 1
')

On commenting the line, the system boots up without any problems. Mounting sda2 after I boot into ALARM works fine.
How can I get it working back again?