Multiple issues after upgrading

[Mazdaspeed6]

I just ran a pacman -Syu and found that Kmod needing installing so i went ahead and it appeared to finish. I rebooted my V3 and now i can SSh into it i get the error "Server refused to allocate pty".
Also my mounted 2nd partition disappeared and wont let me mount it from webmin. The error is "Failed to save mount : The device file '/dev/sda2' does not exist" also the drop down list is missing where i can select the partiton to mount. Most other things like SAMBA appear to be broken as well. Any ideas? I can see the files from WEBMIN if you need me to retrieve a log.

[skealoha86]

I ran into the same issues, received the error "PTY allocation request failed on channel 0" during every SSH connection attempt. I don't really know what I'm doing...

However, I was able to get SSH working again, using this article as a reference: http://blog.asteriosk.gr/2009/02/20/pty ... channel-0/

You can get a limited shell through SSH with this command:

$this->bbcode_second_pass_code('', 'ssh user@host "/bin/bash -i"')

After doing this, do the following, which apparently fixes permissions on the system device files and allows SSH to work normally, as it did before the upgrade:

$this->bbcode_second_pass_code('', 'rm -rf /dev/ptmx
mknod /dev/ptmx c 5 2
chmod 666 /dev/ptmx
umount /dev/pts
rm -rf /dev/pts
mkdir /dev/pts
mount /dev/pts')

The last command didn't work for me until I added /dev/pts to /etc/fstab so I fixed that by doing this, as someone notes in the comments...

$this->bbcode_second_pass_code('', 'echo "none /dev/pts devpts defaults 0 0" >> /etc/fstab')

After doing this, mount /dev/pts and you should be good to go... this worked for me, but if this is bad advice, someone please say so.

I can't automount anything either though - haven't figured out how to fix this yet. One of the packages recently released is incompatible with something (great detective work, right? )

edit: arch has this news entry about kmod, but no details specific to this issue on ARM: http://www.archlinux.org/news/kmod-repl ... nit-tools/

edit2: the automounting issue is probably related to the udev update, same issue here?: viewtopic.php?f=29&t=2315

edit3: Fixed (for me). I downgraded udev to an earlier build that I had cached on my system, then overwrote it with udev-oxnas.

$this->bbcode_second_pass_code('', 'pacman -U /var/cache/pacman/pkg/udev-175-1-arm.pkg.tar.xz')

Y

$this->bbcode_second_pass_code('', 'pacman -S udev-oxnas')

Y

EDIT4: Don't downgrade udev... pacman -S udev-oxnas instead (read the rest of the thread to see why).

[scorp]

nice work skealoha86


i ran into the same troubles a few days ago and fixed it by restoring an old Version of my archlinuxarm, "stored" on an old usb stick.

[Mazdaspeed6]

I tried to run the first command and it says im out of disk space???? I have a 20 gb partition with the OS on it and only 2GB or so is used.

[cyberic]

which command? what message do you get? type 'mount' and check if your root directory (/) is mounted read only or not
or you could try mkdir /test && rmdir /test to see if you have write access
you can get remaining space with df -h

It is possible that a file (for instance a log file) filled the whole partition (look in /var/log)

[Mazdaspeed6]

Tried running "mount" from the webmin shell and i get "Failed to write to /etc/webmin/shell/previous.root when closing : No space left on device" i looked at the /var/log and nothing over a few MB in there that i can see

Edit: deleted the logs that were taking up the most space and freed up about 20mb and still even when i tried to edit the rc.local file it said there wasnt enough space. I have a feeling this is probably the main issue as to why nothing else is working but not sure why all of a sudden all the space is used up.

[pepedog]

udev-oxnas fixes the huge log file problem

[cyberic]

so it i solved, isn't it?

[Mazdaspeed6]

Still not working. I cant get ssh access still . I deleted ALL logs in the folder as a last resort and now i can edit the rc.local and other files but still cant get the ssh to work. I will probably just restore a disk image i created before the update and just not do the update.

[slycat]

To avoid the udev log-barfing I did what skealoha86 did with a helper
$this->bbcode_second_pass_code('', 'kill 'pidof syslog-ng' #Stops any logging
pacman -U /var/cache/pacman/pkg/udev-175-1-arm.pkg.tar.xz
pacman -S udev-oxnas
/etc/rc.d/syslog-ng start')

If you're already out of space before this clear the everything/messages/daemons/errors logs in /var/log/ directory

If you are afraid something else is going on in your drive,
$this->bbcode_second_pass_code('', 'du -hs /* #Gives size of each folder in root, could take a while on big folders')
Then you can narrow down where the space hog is.

Hope that helps.