35 replies to this topic

[Gennar1]

I can confirm that eliminating the redirection to /dev/null in mdev-mount.sh solves the problem, and after a reboot /dev/null is OK, as well as ssh.

original code (in /etc/mdev/mdev-mount.sh):

			    # first allow fstab to determine the mountpoint
			    if ! mount /dev/$MDEV > /dev/null 2>&1
			    then
					    # no fstab entry, use automatic mountpoint

fixed:

			    # first allow fstab to determine the mountpoint
			    if ! mount /dev/$MDEV
			    then
					    # no fstab entry, use automatic mountpoint

Edited by Gennar1, 1 November 2011 - 19:02.

[hemispherical1]

Updated 5 mins ago, same issue here on my not modified dm800hd pvr.
Going to use telnet for the time being

I may be wrong, but I think when fixes are committed, unless you build your own image, they aren't available until the nightly image build is run. Then I would guess an online update would pick up the fix...

--
hemi

Ps. Removing the /dev/null redirection also appears to have worked here. Thanks to all who helped...

Edited by hemispherical1, 1 November 2011 - 19:52.

[pieterg]

mdev-mount.sh gets called for all /dev/sdXX devices, and seems to beat /dev/null to the punch.

indeed, I overlooked that.
Guess I'll have to find another way to silent the fstab mount check

[theparasol]

output naar file en dan rm file of is dat te eenvoudig gedacht?

[pieterg]

that's not a very nice solution.
And mount also doesn't have a 'quiet' option, so I guess I'll just revert the commit for now.

[theparasol]

Tried it with > /dev/zero instead of > /dev/null and it works here fine.
I can use SSH again!

[pieterg]

yes, but you'll have lost /dev/zero now, instead of /dev/null

[theparasol]

I think i prefer losing /dev/zero instead of /dev/null

[Gennar1]

There are other 2 normal files in /dev/ :

/dev/.udev
/dev/mdev.seq

both are created by /etc/init.d/mdev
is this intentional or are they affected by the same bug?

[pieterg]

that's intentional
.udev tells userspace that /dev/ is managed by udev (or mdev in our case)
mdev.seq tells mdev to handle hotplug events sequentially

[Gennar1]

Roger, thanks.

[Erik Slagter]

How about making a temporary alternative device node for null in /tmp and remove that on exit of the script?

[pieterg]

The script runs many times (once for each blockdevice), so that would give some overhead

[Erik Slagter]

mknod and rm? I think that would be overcomable?

[blzr]

I know it's not the case anymore but just curious:
why I haven't been affected with this issue here on my vuduo?
ssh worked fine, /dev/null was ok (device) of course as well...
?

[pieterg]

It's timing related