[Solved] Zyxel NSA325v2 unreachable on network

Install Arch Linux ARM on other devices.

Re: Zyxel NSA325v2 unreachable on network

Postby WarheadsSE » Thu Aug 28, 2014 11:46 pm

Mounting the disk from another system, and doing operations on the root file system from there, which you have to do a number of file setups, and symlinking by hand and carefully.
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6727
Joined: Mon Oct 18, 2010 2:12 pm

Re: Zyxel NSA325v2 unreachable on network

Postby Socaltom » Sat Aug 30, 2014 2:02 pm

I had a similar experience last night. Once the arch install was complete, it came up on the router, I logged in and did pacman -Syu. and assorted other stuff. then I rebooted and got nothing. I pulled the drive over to my collection of pogoplugs and looked around. /boot on the 2nd partition had zImage in it. the first partition had uImage in it. I believe they need to be the same. So I reformated the #2 partition and reinstalled the rootfs. Then I edited fstab so that /dev/sda1 mounts as /boot.
Then it booted up just fine. I was able to do the pacman -Syu just fine after that.

Hope that helps.
Tom
Owned by me
Pink Pogo V2, Black Pogo V3, Zyxel NAS 325 v1,
Adminstrator for
Goflex net, Black V3, Black V2
Socaltom
 
Posts: 567
Joined: Thu Apr 07, 2011 2:21 pm
Location: The left side

Re: Zyxel NSA325v2 unreachable on network

Postby archon » Sat Aug 30, 2014 6:05 pm

@WarheadsSE
Beyond my ability then, I guess.

@Socaltom
Both partitions on my drive have uImage in the directories you mentioned, but they're of slightly different filesize. I'd love to know how you reinstalled the rootfs though.
archon
 
Posts: 11
Joined: Thu Aug 28, 2014 5:32 pm

Re: Zyxel NSA325v2 unreachable on network

Postby Socaltom » Sat Aug 30, 2014 6:18 pm

I put the drive on another linux box
then I used mkfs.ext3 to format the partition in question /dev/sdX2
Code: Select all
mkfs.ext3 /dev/sdX2

then I mounted the new partition
Code: Select all
mkdir /usb
mount /dev/sdX2 /usb
cd /usb

then I used wget to download the current Kirkwoodroot fs
Code: Select all
wget http://archlinuxarm.org/os/ArchLinuxARM-kirkwood-latest.tar.gz


then I used tar to extract it
Code: Select all
tar -xzvf ArchLinuxARM-kirkwood-latest.tar.gz


then edit /usb/etc/fstab
/dev/sda1 /boot ext2 noatime 0 0

sync

then
Code: Select all
 cd /
umount /usb


That replaces the rootfs and links the first partition.

Your description matches what I saw. I think it will boot if you reinstall the rootfs.
Tom
Owned by me
Pink Pogo V2, Black Pogo V3, Zyxel NAS 325 v1,
Adminstrator for
Goflex net, Black V3, Black V2
Socaltom
 
Posts: 567
Joined: Thu Apr 07, 2011 2:21 pm
Location: The left side

Re: Zyxel NSA325v2 unreachable on network

Postby pepedog » Sat Aug 30, 2014 6:37 pm

I don't think he needs to do this, possibly copy uImage from /boot on second partition to / of first partition
pepedog
Developer
 
Posts: 2431
Joined: Mon Jun 07, 2010 3:30 pm
Location: London UK

Re: Zyxel NSA325v2 unreachable on network

Postby archon » Sat Aug 30, 2014 10:38 pm

Just copying the file did the trick. Thanks a lot, guys.
archon
 
Posts: 11
Joined: Thu Aug 28, 2014 5:32 pm

Re: [Solved] Zyxel NSA325v2 unreachable on network

Postby pepedog » Sat Aug 30, 2014 11:45 pm

Before update next time mount, like this
Code: Select all
mount /dev/sda1 /boot

Or add a line in fstab that does this
pepedog
Developer
 
Posts: 2431
Joined: Mon Jun 07, 2010 3:30 pm
Location: London UK

Re: [Solved] Zyxel NSA325v2 unreachable on network

Postby archon » Sun Aug 31, 2014 3:57 pm

I already updated then rebooted before I read your post, and it worked anyway, so I'd rather not mess with it for now. If I start having problems again, I will.
archon
 
Posts: 11
Joined: Thu Aug 28, 2014 5:32 pm

Re: [Solved] Zyxel NSA325v2 unreachable on network

Postby Socaltom » Mon Sep 01, 2014 9:02 pm

I thought I would add a little info in case someone has this problem and is looking to restore their rootfs. I accidentally corrupted my rootfs while doing some test ( dd will get you if you aren't paying attention). Anyhow, I struggled all morning trying to get it to boot after trying to restore the rootfs.

Finally, I discovered that the housing I was using to attach the drive to another system was doing some sort of translation of the drive. I eventually plugged the drive into another housing and discovered that where I had made a 25G partition, it reported a 200M partition. I re-partitioned everything and re-installed and it booted right up. Lesson learned.
Tom
Owned by me
Pink Pogo V2, Black Pogo V3, Zyxel NAS 325 v1,
Adminstrator for
Goflex net, Black V3, Black V2
Socaltom
 
Posts: 567
Joined: Thu Apr 07, 2011 2:21 pm
Location: The left side

Previous

Return to [Please read announcement] Community-Supported Devices

Who is online

Users browsing this forum: No registered users and 2 guests