Pogoplug E02 No SSH access after reboot Orange front LED

[makuab]

At first I successfully installed arch and created a user for myself, and installed sudo. I used /sbin/reboot a few times throughout and didn't have any problems. After editing the sudoers file and using /sbin/reboot, it wasn't connecting to the network. I looked at my router and didn't see it under the devices. I tried restarting the plug, and removing and reinserting the ethernet cable both without success.

I'm a newbie, so bear with me.

Thanks!

EDIT: Connected the USB to another linux machine of mine, and changed the sudoers file. Still not working. It doesn't have a network connection.

EDIT: When I take out the reboot and take out the USB drive the light flashes green a bit and then becomes a solid green. Still no network connection.

EDIT: After waiting a bit, I got ssh access. I can log in as root with the account I set up on the pogoplug site. How do I get arch to work now? This is without the USB stick and just the pogoplug shell or whatever.

EDIT: I tried putting the USB stick in another computer and booting from it, would that do anything? It didn't boot. Should I just go through the steps again to install arch and reinstall it? I want to fix it and learn something.

[moonman]

- You can't boot your x86/x86_64 based computer using an ARM rootfs, it also has a different boot mechanism.
- Don't just unplug the power cord from the plug, shut it down/reboot gracefully (I know you did in this case)
- Enable netconsole to see what the problem is, Link is in my signature (upgrading U-Boot), then post the output back here
- Likely the filesystem is corrupt, so run e2fsck -f on another linux machine (this you CAN do on x86)
- Finaly convert your boot device to ext3 and don't forget to change U-Boot (bootloader) variable "usb_rootfstype" to ext3
$this->bbcode_second_pass_code('', '/usr/sbin/fw_setenv usb_rootfstype 'ext3'')

[makuab]

$this->bbcode_second_pass_quote('moonman', '-') You can't boot your x86/x86_64 based computer using an ARM rootfs, it also has a different boot mechanism.
- Don't just unplug the power cord from the plug, shut it down/reboot gracefully (I know you did in this case)
- Enable netconsole to see what the problem is, Link is in my signature (upgrading U-Boot), then post the output back here
- Likely the filesystem is corrupt, so run e2fsck -f on another linux machine (this you CAN do on x86)
- Finaly convert your boot device to ext3 and don't forget to change U-Boot (bootloader) variable "usb_rootfstype" to ext3
$this->bbcode_second_pass_code('', '/usr/sbin/fw_setenv usb_rootfstype 'ext3'')

[makuab]

Am I allowed to bump?

[Socaltom]

Run fsck on the USB drive and post the command and output.
The likely problem is that the USB filesystem is corrupt, if you can't fix it with fsck, then you will need to reformat the usb drive and re-extract the rootfs tarball.
Tom

[makuab]

$this->bbcode_second_pass_quote('Socaltom', 'R')un fsck on the USB drive and post the command and output.
The likely problem is that the USB filesystem is corrupt, if you can't fix it with fsck, then you will need to reformat the usb drive and re-extract the rootfs tarball.
Tom

[moonman]

Did you change the usb_rootfstype to ext3? Reformat and reinstall. Use ext3 to format the drive. "How to reinstall" is linked in my signature.

The correct command is fsck /dev/sdb1
That error is normal if you don't specify a partition to check
Tom
$this->bbcode_second_pass_quote('makuab', '')$this->bbcode_second_pass_quote('Socaltom', 'R')un fsck on the USB drive and post the command and output.
The likely problem is that the USB filesystem is corrupt, if you can't fix it with fsck, then you will need to reformat the usb drive and re-extract the rootfs tarball.
Tom

$this->bbcode_second_pass_quote('Socaltom', 'T')he correct command is fsck /dev/sdb1
That error is normal if you don't specify a partition to check
Tom
$this->bbcode_second_pass_quote('makuab', '')$this->bbcode_second_pass_quote('Socaltom', 'R')un fsck on the USB drive and post the command and output.
The likely problem is that the USB filesystem is corrupt, if you can't fix it with fsck, then you will need to reformat the usb drive and re-extract the rootfs tarball.
Tom

[makuab]

Uh oh. Now it's not working again. I was trying to install a GUI and installed xorg and mesa, did /sbin/reboot again and now I'm having the same problem. I tried doing the same command on my other computer and it came back clean, but now I can't ssh into it and it's not connected to the network.