Hi,
Since yesterday, a NetBSD 6.0.1/amd64 domU of mine can't mount its root fs
anymore:
boot device: xbd0
root on xbd0a dumps on xbd0b
Your machine does not initialize mem_clusters; sparse_dumps disabled
Supported file systems: union umap tmpfs smbfs puffs ptyfs procfs overlay null
ntfs nfs
On Thu, 30 May 2013 13:27:44 +0200 (CEST)
Emile `iMil' Heitor i...@home.imil.net wrote:
Hi,
Since yesterday, a NetBSD 6.0.1/amd64 domU of mine can't mount its root fs
anymore:
boot device: xbd0
root on xbd0a dumps on xbd0b
Your machine does not initialize mem_clusters; sparse_dumps
I suggest checking this from a dom0 perspective first before continuing the
hunt for weird and uncommon file system corruption issues in the domU.
In the dom0, make sure your lvm is active, e.g. marked with an 'a' rather than
a 'd'
in the output of lvm lvs. I suspect you couldn't even get a
Le 30/05/13 16:16, Emile `iMil' Heitor a écrit :
I suggest checking this from a dom0 perspective first before
continuing the hunt for weird and uncommon file system corruption
issues in the domU.
In the dom0, make sure your lvm is active, e.g. marked with an 'a'
rather than a 'd'
in the
I installed NetBSD on a HPNX9420 laptop with a dual core
CentrinoT2600/2.16GHzCPU
With the Generic kernel both cores revs up to maximum frequency and stays
there.
This result in high temperatures within a few minutes and the fan is constantly
on
max speed and noise. I installed estd-0.7 from
On Thu, 30 May 2013, Jean-Yves Migeon wrote:
Do you get the same output between disklabel /dev/xbd1 and disklabel -Ar
/dev/xbd1?
I would also try dd'ing the LV and pass it through vnconfig(8) (never did it,
YMMV).
I've seen weird behavior from domU when it falls on specific forbidden
On Thu, May 30, 2013 at 05:50:55PM +, Tim R wrote:
I installed NetBSD on a HPNX9420 laptop with a dual core
CentrinoT2600/2.16GHzCPU
With the Generic kernel both cores revs up to maximum frequency and stays
there.
This result in high temperatures within a few minutes and the fan is
On 2013-05-30, Dave B s...@y2013.dberg.net wrote:
Does lowering the clock speed manually via sysctl succeed? E.g.,
host# freqs=$(sysctl -n machdep.est.frequency.available)
host# minfreq=$(echo $freqs | rs 0 1 | sort -n | head -1)
host# sysctl -w
