Multiple issues after upgrading

[WarheadsSE]

...
scroll back up
....

[chaskito]

Hah! I have gotten too caught up in busting out my old dockstar, thanks warheadsse, sheesh.... I feel smart.

[gard]

Hi,

I am an archlinux noob and this is my first post here. Thanks for the excellent articles and posts on booting my pogoplug with archlinux. It started out smoothly, then ran in to issues around pacman conflicts with /etc/mtab and locale.sh, followed by ssh errors ("ssh PTY allocation request failed on channel 0"). I used the suggestions in bharath and skealoha86's posts to resolve those last few, and went back to /var/cache/pacman/pkg/initscripts-2011.07.3-1-arm.pkg.tar.xz. Now, my LED flashes at boot for about ~15 seconds and then settles in to a steady ON state. I am able to ssh in to the unit fine. Many many thanks!

I have an external hard drive and a flash drive connected over USB, but I don't see anything under /mnt. I presume that means these drives are not getting automounted. Is that correct?

$this->bbcode_second_pass_code('', '[root@alarm mnt]#
[root@alarm mnt]# cd /dev
[root@alarm dev]# ls -la sda*
brw-rw---- 1 root disk 8, 0 Dec 31 1969 sda
brw-rw---- 1 root disk 8, 1 Dec 31 1969 sda1
[root@alarm dev]#')

$this->bbcode_second_pass_code('', '[root@alarm ~]# cd /mnt
[root@alarm mnt]# ls -la
total 8
drwxr-xr-x 2 root root 4096 Dec 21 10:09 .
drwxr-xr-x 21 root root 4096 Feb 6 14:45 ..
[root@alarm mnt]#')

First, am I looking in the right places?

If I am, what should I do get them mounted? Is it safe to run "pacman -Sy udev-automount" to set up the udev rules again? Or, will running pacman mess up the initscripts again?

Thanks,
gard

[WarheadsSE]

Mounts, separate thread.

mount
cat /proc/partitions
and they auto-mount under /media not /mnt

[mu31tw]

This worked for me to fix ssh (I mounted the filesystem USB drive on another Linux machine at /media/usbstick; MAKE SURE you don't do all commands on /dev if doing it this way as you'll be fixing the wrong machine!)

First, I manually fixed the random and urandom devices as listed previously in this thread.

Next, I manually added the first twenty tty devices according to Philoo's post:
$this->bbcode_second_pass_quote('', '
') crw-rw-rw- 1 root tty 5, 0 Dec 31 1969 /dev/tty
crw--w---- 1 root tty 4, 0 Dec 31 1969 /dev/tty0
crw-rw---- 1 root tty 4, 1 Feb 3 22:14 /dev/tty1
crw--w---- 1 root tty 4, 10 Dec 31 1969 /dev/tty10
crw--w---- 1 root tty 4, 11 Dec 31 1969 /dev/tty11
crw--w---- 1 root tty 4, 12 Dec 31 1969 /dev/tty12
crw--w---- 1 root tty 4, 13 Dec 31 1969 /dev/tty13
crw--w---- 1 root tty 4, 14 Dec 31 1969 /dev/tty14
crw--w---- 1 root tty 4, 15 Dec 31 1969 /dev/tty15
crw--w---- 1 root tty 4, 16 Dec 31 1969 /dev/tty16
crw--w---- 1 root tty 4, 17 Dec 31 1969 /dev/tty17
crw--w---- 1 root tty 4, 18 Dec 31 1969 /dev/tty18
crw--w---- 1 root tty 4, 19 Dec 31 1969 /dev/tty19
crw-rw---- 1 root tty 4, 2 Feb 3 22:14 /dev/tty2

[mu31tw]

Another quick note for the interested; I tried downgrading udev, which I thought was the source of all my woes. By god did I regret that. The system wouldn't boot at all, and when I re-mounted the USB filesystem disk on another PC the size of errors.log was a little large, and full of nonsense. Pretty nasty. But, in fixing it, I found something out that might prove to be spectacularly useful: my day-to-day system is also Arch, so I begain to wonder if I could use pacman on my laptop to re-upgrade udev on my Arch Linux ARM install filesystem. And guess what? It only bloody worked! This was the command that I used:

$this->bbcode_second_pass_code('', 'sudo pacman -U /media/usbstick/var/cache/pacman/pkg/udev-oxnas-180-1-arm.pkg.tar.xz --root /media/usbstick/ --dbpath /media/usbstick/var/lib/pacman/ --arch arm')

Note the flags to specify 1) a different FS root, 2) the alternative database path, and 3) the alternative architecture.

And to think I used to find the tooltips in MS Word 6.0 impressive, all those years ago...

[WarheadsSE]

Now THAT is a solution.

Nicely done.

(we figured we'd let you all sort it out, after all there is reason there is a udev-oxnas package)

[mu31tw]

I just noticed something in my previous post: if you write 'Arch Linux ARM' (with a normal 'o') it automatically gets changed to "Arch Linux ARM install". Seems a little cheeky to me. Although it does remind me of another MS Word story from the old days: much fun was had at school with Word's autocorrect dictionary; my favourites were 'Jesus' being changed to 'Elvis' and 'The Bible' being converted to 'the big bumper book of lies'. And I went to a catholic school, so needless to say, these particular new entries received a fair bit of use (and caused a fair amount of unsolicited blasphemy from unwitting christian typists). Ahh, those sweet days when the kids knew more than the sysadmins...

Ok, that's the final word on, er, Word.

[bharath]

I was wondering what the current status of this issue, is it safe to upgrade initscripts?

I had the same "PTY allocation..." error after upgrading yesterday night. I found the same answer skealoha86 gives while doing my own searching for a solution (but I didn't know about the bash -i trick with ssh at the time and did it all via webmin )

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

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')

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