> On 2. Feb 2025, at 01:05, Paul Graff wrote:
>
>
>
> On 2/1/25 3:17 PM, Toomas Soome wrote:
>>
>>> On 1. Feb 2025, at 22:38, Paul Graff via openindiana-discuss
>>> wrote:
>>>
>>>
>>>
>>> On 2/1/25 8:14 AM, Toomas Soome via openindiana-discuss wrote:
> On 1. Feb 2025, at 13:12, Toom
On 2/1/25 3:17 PM, Toomas Soome wrote:
On 1. Feb 2025, at 22:38, Paul Graff via openindiana-discuss
wrote:
On 2/1/25 8:14 AM, Toomas Soome via openindiana-discuss wrote:
On 1. Feb 2025, at 13:12, Toomas Soome via openindiana-discuss
wrote:
On 1. Feb 2025, at 10:13, Paul Graff via
> On 1. Feb 2025, at 22:38, Paul Graff via openindiana-discuss
> wrote:
>
>
>
> On 2/1/25 8:14 AM, Toomas Soome via openindiana-discuss wrote:
>>
>>> On 1. Feb 2025, at 13:12, Toomas Soome via openindiana-discuss
>>> wrote:
>>>
>>>
>>>
On 1. Feb 2025, at 10:13, Paul Graff via open
On 2/1/25 8:14 AM, Toomas Soome via openindiana-discuss wrote:
On 1. Feb 2025, at 13:12, Toomas Soome via openindiana-discuss
wrote:
On 1. Feb 2025, at 10:13, Paul Graff via openindiana-discuss
wrote:
Hi, openindiana running on machine here is an i5 with 8 GiB ddr3 memory
(recently t
> On 1. Feb 2025, at 13:12, Toomas Soome via openindiana-discuss
> wrote:
>
>
>
>> On 1. Feb 2025, at 10:13, Paul Graff via openindiana-discuss
>> wrote:
>>
>> Hi, openindiana running on machine here is an i5 with 8 GiB ddr3 memory
>> (recently tested with memtest). openindiana on hdd dri
> On 1. Feb 2025, at 10:13, Paul Graff via openindiana-discuss
> wrote:
>
> Hi, openindiana running on machine here is an i5 with 8 GiB ddr3 memory
> (recently tested with memtest). openindiana on hdd drive was initially
> in Lenovo M90p with 4 GiB memory.
>
> I had just '# pkg update -vvv',
Hi,
Assertion failed is a bug, please file a bug at
https://www.illumos.org/issues/ under the zfs category. People will
instruct you how to provide additional details and the coredump if needed.
-Till
On 01.02.25 09:13, Paul Graff via openindiana-discuss wrote:
Hi, openindiana running on ma
Hi, openindiana running on machine here is an i5 with 8 GiB ddr3 memory
(recently tested with memtest). openindiana on hdd drive was initially
in Lenovo M90p with 4 GiB memory.
I had just '# pkg update -vvv', had another tab open in Mate terminal
and attempted to envoke TOR, in order to see error
Hello,
I did a full update and I confirm that now caja works as expected. Thank you so
much forresolving this problem at such short notice!
Kindest regards,Apostolos
--Apostolos Syropoulos
Xanthi, Greece
On Sunday, December 15, 2024 at 05:52:15 PM GMT+2, Till Wegmueller
FYI, Rebuild got triggered yesterday.
Package is updated and available for everybody to update.
-Till
On 15/12/2024 16.50, Jean-Pierre André via openindiana-discuss wrote:
Toomas Soome via openindiana-discuss wrote on 12/15/24 2:58 PM:
On 15. Dec 2024, at 15:43, Jean-Pierre André via openin
Toomas Soome via openindiana-discuss wrote on 12/15/24 2:58 PM:
On 15. Dec 2024, at 15:43, Jean-Pierre André via openindiana-discuss
wrote:
Marcel Telka wrote on 12/15/24 1:51 PM:
On Sun, Dec 15, 2024 at 11:57:22AM +0100, Jean-Pierre André via
openindiana-discuss wrote:
I however see tha
> On 15. Dec 2024, at 15:43, Jean-Pierre André via openindiana-discuss
> wrote:
>
> Marcel Telka wrote on 12/15/24 1:51 PM:
>> On Sun, Dec 15, 2024 at 11:57:22AM +0100, Jean-Pierre André via
>> openindiana-discuss wrote:
>>> I however see that /usr/kernel/fs/amd64/pcfs and
>>> /usr/kernel/fs/
Marcel Telka wrote on 12/15/24 1:51 PM:
On Sun, Dec 15, 2024 at 11:57:22AM +0100, Jean-Pierre André via
openindiana-discuss wrote:
I however see that /usr/kernel/fs/amd64/pcfs and
/usr/kernel/fs/amd64/fdfs which also have to index into
the vfssw table still do so assuming this is an array of
12
On Sun, Dec 15, 2024 at 11:57:22AM +0100, Jean-Pierre André via
openindiana-discuss wrote:
> I however see that /usr/kernel/fs/amd64/pcfs and
> /usr/kernel/fs/amd64/fdfs which also have to index into
> the vfssw table still do so assuming this is an array of
> 128 bytes records. I do not know whic
Hi Apostolos,
Please do a full update and retry, it should be ok now.
Jean-Pierre
Apostolos Syropoulos via openindiana-discuss wrote on 12/14/24 6:22 PM:
Hi,
To answer the previous question, I was trying to view the tree structure with
caja.As I said, in the past I have done this virtually mi
Hi Till,
I have done a full update, I get the updated fuse, and it
apparently behaves fine.
I however see that /usr/kernel/fs/amd64/pcfs and
/usr/kernel/fs/amd64/fdfs which also have to index into
the vfssw table still do so assuming this is an array of
128 bytes records. I do not know which pac
Hi Jean-Pierre
I put a PR for a Rebuild of FUSE into Review. If Andreas gets it before
me he will merge it otherwise I will after dinner.
-Till
On 14.12.24 18:42, Jean-Pierre André via openindiana-discuss wrote:
Hi Apostolos,
I consider this as solved now, and next week, I will make a pull
Hi Apostolos,
I consider this as solved now, and next week, I will make a pull
request for an unrelated feature which will force the needed
recompilation of the fuse module.
Note : the crash was outside of ntfs-3g, and your file system
is unlikely to have been damaged.
Jean-Pierre
Apostolos Sy
Hi,
To answer the previous question, I was trying to view the tree structure with
caja.As I said, in the past I have done this virtually millions of times with
no problem. From the discussion so far, I conclude that this is a bug that
others have managed to reproduce.Please let me know if I can
On Sat, Dec 14, 2024 at 05:58:19PM +0100, Jean-Pierre André via
openindiana-discuss wrote:
> The source of the issue is adding vfs_syncfs into "struct vfsops"
> which causes the extra size of "struct vfssw" (not in an
> vm/*.h as I said earlier).
>
> https://github.com/illumos/illumos-gate/commit
Hi again,
The source of the issue is adding vfs_syncfs into "struct vfsops"
which causes the extra size of "struct vfssw" (not in an
vm/*.h as I said earlier).
https://github.com/illumos/illumos-gate/commit/4763305e3243687c189d755d737d52205b2614ed
So what am I supposed to do for this not to hap
On Sat, Dec 14, 2024 at 05:22:53PM +0100, Jean-Pierre André via
openindiana-discuss wrote:
> I really cannot understand how this can happen. There must
Easily. Fuse is not in illumos-gate:
https://github.com/OpenIndiana/oi-userland/tree/oi/hipster/components/openindiana/fuse
> be a defect in t
Hi again,
The source argument of the strlcpy() is
vfssw[vfsp->vfs_fstype].vsw_name
and the problem is that "struct vfssw" is now 136 bytes long
instead of 128 in the compiled code, due to a recent change
in some vm/*.h which I have not identified.
So the fuse module has not been recompiled al
In message ,
=?utf-8?q?Jean-Pierre_Andr=C3=A9_via_
openindiana-discuss?= writes:
>On my computer I get :
>[root@openindiana amd64]# /usr/lib/fs/ntfs-3g/fstyp /dev/dsk/c5t2d0p1
>ntfs-3g
I replicated inside a VM:
https://www.illumos.org/issues/16974>
John
groenv...@acm.org
___
> On 14. Dec 2024, at 12:49, Jean-Pierre André via openindiana-discuss
> wrote:
>
> Hi,
>
> See below
>
> Jean-Pierre
>
> Toomas Soome via openindiana-discuss wrote on 12/14/24 9:11 AM:
>>> On 14. Dec 2024, at 09:32, Jean-Pierre André via openindiana-discuss
>>> wrote:
>>>
>>> Hi,
>>>
>
Hi again,
@Apostolos what is the file viewer you were using, and what in what
circumstances did the crash occur (displaying the file tree ?).
There is a patch awaiting for supporting SEEK_DATA and SEEK_HOLE,
which may be required to display sparse or compressed files.
In particular "cp" has no f
Hi,
See below
Jean-Pierre
Toomas Soome via openindiana-discuss wrote on 12/14/24 9:11 AM:
On 14. Dec 2024, at 09:32, Jean-Pierre André via openindiana-discuss
wrote:
Hi,
Please post the output of
fmdump -Vp -u c0c54af8-4972-4f2c-85ba-c20b0272ea0b
Also post the record from /var/adm/mess
> On 14. Dec 2024, at 09:32, Jean-Pierre André via openindiana-discuss
> wrote:
>
> Hi,
>
> Please post the output of
> fmdump -Vp -u c0c54af8-4972-4f2c-85ba-c20b0272ea0b
>
> Also post the record from /var/adm/messages similar to :
> fuse: [ID 295230 kern.info] Fuse kernel init at 0xff
>
Hi,
Please post the output of
fmdump -Vp -u c0c54af8-4972-4f2c-85ba-c20b0272ea0b
Also post the record from /var/adm/messages similar to :
fuse: [ID 295230 kern.info] Fuse kernel init at 0xff
Subsequent records related to ntfs-3g may also help.
Jean-Pierre
Apostolos Syropoulos via openindi
> On 14. Dec 2024, at 00:06, Apostolos Syropoulos via openindiana-discuss
> wrote:
>
> Hi,
> I have an external USB disk that has an NTFS file system. I am using
> the command
>
> # ntfs-3g /dev/dsk/c13t0d0p1 /mnt/
> to mount the file system and everything works just fine, However,when I
Hi,
I have an external USB disk that has an NTFS file system. I am using
the command
# ntfs-3g /dev/dsk/c13t0d0p1 /mnt/
to mount the file system and everything works just fine, However,when I try to
inspect the folder /mnt with the file viewer thesystem crashes (I am using
illumos-9d4bc241fd
oration and gfx-drm?
> > >
> > > С уважением,
> > > Александр Пыхалов,
> > > программист отдела телекоммуникационной инфраструктуры
> > > управления информационно-коммуникационной инфраструктуры ЮФУ
> > >
> > >
> > > ___
: Discussion list for OpenIndiana
> Тема: Re: [OpenIndiana-discuss] Kernel panic after pkg update
>
> The only outstanding things since May were switching gfx-drm to gcc-
> 7
> and
> cherry-picking gcc-10 patches from upstream.
>
>
> On Tue, Aug 18, 2020 at 9:43 AM Tony Bria
Пыхалов,
>> программист отдела телекоммуникационной инфраструктуры
>> управления информационно-коммуникационной инфраструктуры ЮФУ
>>
>>
>>
>> От: Aurélien Larcher
>> Отправлено: 18 августа 2020 г. 11:29
>> Ко
: Discussion list for OpenIndiana
> Тема: Re: [OpenIndiana-discuss] Kernel panic after pkg update
>
> The only outstanding things since May were switching gfx-drm to gcc-
> 7
> and
> cherry-picking gcc-10 patches from upstream.
>
>
> On Tue, Aug 18, 2020 at 9:43 AM Tony Bria
От: Aurélien Larcher
> Отправлено: 18 августа 2020 г. 11:29
> Кому: Discussion list for OpenIndiana
> Тема: Re: [OpenIndiana-discuss] Kernel panic after pkg update
>
> The only outstanding things since May were switching gfx-drm to gcc-7 and
> cherry-picking gcc-10 patches from u
От: Aurélien Larcher
Отправлено: 18 августа 2020 г. 11:29
Кому: Discussion list for OpenIndiana
Тема: Re: [OpenIndiana-discuss] Kernel panic after pkg update
The only outstanding things since May were switching gfx-drm to gcc-7 and
cherry-picking gcc-10 patches from upstream.
On Tue, Aug 18
t; управления информационно-коммуникационной инфраструктуры ЮФУ
> >
> >
> >
> > От: Tony Brian Albers
> > Отправлено: 18 августа 2020 г. 10:14
> > Кому: openindiana-discuss@openindiana.org
> > Тема: Re: [OpenIndiana-discuss] Kernel p
оммуникационной инфраструктуры
> управления информационно-коммуникационной инфраструктуры ЮФУ
>
>
>
> От: Tony Brian Albers
> Отправлено: 18 августа 2020 г. 10:14
> Кому: openindiana-discuss@openindiana.org
> Тема: Re: [OpenIndiana-discuss]
инфраструктуры
> управления информационно-коммуникационной инфраструктуры ЮФУ
>
>
>
> От: Tony Brian Albers
> Отправлено: 18 августа 2020 г. 10:14
> Кому: openindiana-discuss@openindiana.org
> Тема: Re: [OpenIndiana-discuss] Kernel
Кому: openindiana-discuss@openindiana.org
Тема: Re: [OpenIndiana-discuss] Kernel panic after pkg update
FYI
I removed and reinstalled all xorg-related pkgs. I also ran pkg update
again.
Now Xorg loads more driver modules and there are no errors in Xorg.log,
but the system still panics.
Kernel
FYI
I removed and reinstalled all xorg-related pkgs. I also ran pkg update
again.
Now Xorg loads more driver modules and there are no errors in Xorg.log,
but the system still panics.
Kernel illumos-0d54f452f4
The panic message in /var/adm/messages seems to be exactly the same.
/tony
On Tu
Hi guys,
I'm trying to get my workstation to run the latest OI. Installation of
the desktop-image went fine, and after reboot everything is still ok.
Then I did a pkg update. Now running kernel illumos-06260e34c2
Now, everytime I try to start X, it panics and reboots. I've disabled
the displayma
Can you post the core dump somewhere?
Cheers,
Adam
> On 4 Oct 2016, at 14:33, Apostolos Syropoulos via openindiana-discuss
> wrote:
>
> Today I saw the following:
>
>
>
> Oct 4 15:26:18 adalind savecore: [ID 570001 auth.error] reboot after panic:
>
> assertion failed: (vp->v_count > 0) &
Today I saw the following:
Oct 4 15:26:18 adalind savecore: [ID 570001 auth.error] reboot after panic:
assertion failed: (vp->v_count > 0) && (vp->v_count_dnlc > 0), file:
../../common/fs/vnode.c, line: 852
Does anybody have any idea what this is about?
A.S.
--
Aposto
Sent from my iPhone
> On Sep 16, 2015, at 11:49 AM, Watson, Dan wrote:
>
> I've noticed that drives with a labeled WWN tend to be less error prone, and
> only when a driv
This a distinction that only exists in your head. :)
I have only 768 HGST 600gb sas drives in spinning in production at
On 09/16/15 10:42 PM, Andrew Gabriel wrote:
Also what OI/illumos is that, because I was reading long ago there
were some bugs solved in illumos for mpt_sas.
Somewhere around 18 months ago IIRC, Nexenta pushed a load of fixes
for this into their git repo. I don't think I've seen these picked up
On 16/09/2015 19:24, Nikola M wrote:
On 09/11/15 08:57 PM, Watson, Dan wrote:
I'm using mpt_sas with SATA drives, and I_DO_ have error counters
climbing for some of those drives, is it probably that?
Any other ideas?
It is generally strongly advised to use SATA disks on SATA controllers
and
nly import option
> mentioned previously and it seems to be working fine. I'm betting I just
> did not have enough RAM available to do dedupe.
>
> Thanks!
> Dan
>
> -Original Message-
> From: Nikola M [mailto:minik...@gmail.com]
> Sent: September 16, 2015 11:2
Thanks!
> Dan
>
> -----Original Message-----
> From: Nikola M [mailto:minik...@gmail.com]
> Sent: September 16, 2015 11:25 AM
> To: Discussion list for OpenIndiana
> Subject: Re: [OpenIndiana-discuss] Kernel panic on hung zpool accessed via
> lofi
>
> On 09/11/15 08:57 P
27;m betting I just did
not have enough RAM available to do dedupe.
Thanks!
Dan
-Original Message-
From: Nikola M [mailto:minik...@gmail.com]
Sent: September 16, 2015 11:25 AM
To: Discussion list for OpenIndiana
Subject: Re: [OpenIndiana-discuss] Kernel panic on hung zpool accessed vi
On 09/11/15 08:57 PM, Watson, Dan wrote:
I'm using mpt_sas with SATA drives, and I_DO_ have error counters climbing for
some of those drives, is it probably that?
Any other ideas?
It is generally strongly advised to use SATA disks on SATA controllers
and SAS disks on SAS controllers. And to
14 сентября 2015 г. 20:23:18 CEST, "Watson, Dan"
пишет:
>>-Original Message-
>>From: Jim Klimov [mailto:jimkli...@cos.ru]
>>Sent: September 12, 2015 10:31 AM
>>To: Discussion list for OpenIndiana; Watson, Dan;
>openindiana-discuss@openindiana.or
>-Original Message-
>From: Jim Klimov [mailto:jimkli...@cos.ru]
>Sent: September 12, 2015 10:31 AM
>To: Discussion list for OpenIndiana; Watson, Dan;
>openindiana-discuss@openindiana.org
>Subject: Re: [OpenIndiana-discuss] Kernel panic on hung zpool accessed via lofi
&
11 сентября 2015 г. 20:57:46 CEST, "Watson, Dan"
пишет:
>Hi all,
>
>I've been enjoying OI for quite a while butI'm running into a problem
>with accessing zpool on disk image files sitting on zfs accessed via
>lofi that I hope someone can give me a hint on.
>
>To recover data from a zpool I've cop
Hi all,
I've been enjoying OI for quite a while butI'm running into a problem with
accessing zpool on disk image files sitting on zfs accessed via lofi that I
hope someone can give me a hint on.
To recover data from a zpool I've copied slice 0 off of all the disks to a
different host under /al
Thanks Gordon.
Any idea if that has been merged into illumos gate yet?
On 14-04-21 06:04 PM, Gordon Ross wrote:
You need this fix:
https://github.com/Nexenta/illumos-nexenta/commit/9a60a9d168313d9c350f813abccc6320879ad9b5
On Thu, Apr 17, 2014 at 5:05 PM, Geoff Nordli wrote:
On 14-04-17 0
You need this fix:
https://github.com/Nexenta/illumos-nexenta/commit/9a60a9d168313d9c350f813abccc6320879ad9b5
On Thu, Apr 17, 2014 at 5:05 PM, Geoff Nordli wrote:
> On 14-04-17 01:20 PM, Geoff Nordli wrote:
>>
>> I am running OI 151a8.
>>
>> I had a kernel panic today. I have the dump file so
On 14-04-17 01:20 PM, Geoff Nordli wrote:
I am running OI 151a8.
I had a kernel panic today. I have the dump file so I can provide
more detail if needed.
Should I send this over to the illumos list or can someone help me here?
thanks,
Geoff
TIME UUID SUNW-MSG-
I am running OI 151a8.
I had a kernel panic today. I have the dump file so I can provide more
detail if needed.
Should I send this over to the illumos list or can someone help me here?
thanks,
Geoff
TIME UUID SUNW-MSG-ID
Apr 17 2014 12:19:26.324813000 dabd95a4-
On Thu, Dec 12, 2013 at 02:48:21PM -0800, Reginald Beardsley wrote:
> I didn't find anything in the wiki about reporting kernel panics. Is there a
> documented procedure? The dump is ~285 MB.
http://wiki.illumos.org/display/illumos/How+To+Report+Problems
--
+
FWIW My system just went down w/ a kernel panic caused by a null reference in
genunix. I'm running oi_151a8. I had just unmounted an SDHC card w/ a FAT
filesystem used in my Canon camera and when I came back from putting the
camera away found the system at the grub menu.
I didn't find anythi
Hi Geoff,
Geoff Simmons píše v po 13. 02. 2012 v 19:39 +0100:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 02/13/12 06:44 PM, Bryan N Iotti wrote:
> > Maybe you could try disabling ACPI in BIOS if possible, or otherwise use
> > the acpi-user-options=0x2 at boot.
> >
> > Read here f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02/13/12 06:44 PM, Bryan N Iotti wrote:
> Maybe you could try disabling ACPI in BIOS if possible, or otherwise use
> the acpi-user-options=0x2 at boot.
>
> Read here for more info on disabling ACPI on boot:
>
> https://blogs.oracle.com/danasblog
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02/13/12 06:51 PM, Jason Matthews wrote:
> i would start even more conservatively and disable speed step in the
> bios first and then more on to the other suggestions. i am not a fan of
> speedstep in general.
> On Feb 13, 2012, at 9:44 AM, Bryan
i would start even more conservatively and disable speed step in the bios first
and then more on to the other suggestions. i am not a fan of speedstep in
general.
j.
Sent from Jasons' hand held
On Feb 13, 2012, at 9:44 AM, Bryan N Iotti wrote:
> Maybe you could try disabling ACPI in BIOS
Maybe you could try disabling ACPI in BIOS if possible, or otherwise use
the acpi-user-options=0x2 at boot.
Read here for more info on disabling ACPI on boot:
https://blogs.oracle.com/danasblog/entry/configuring_solaris_acpi_at_boot
BTW and OT, I hadn't even thought that attaching an image to
>> From: "Geoff Simmons"
>
> A colleague attempted to boot oi_151a from CD on an HP EliteBook 8560w
> laptop:
>
> http://h10010.www1.hp.com/wwpc/us/en/sm/WF06a/321957-321957-64295-3740645-4307559-5071171.html
>
>
> ... the variant with Intel i7-2670QM. He got an immediate kernel panic
I'v
em;
> that I can reliably crash our build machine with the -j(n) option to gcc.
>
> More to follow...
>
> Lou Picciano
>
> - Original Message -
> From: "Geoff Simmons"
> To: openindiana-discuss@openindiana.org
> Cc: "Nils Goroll"
&g
diana.org
Cc: "Nils Goroll"
Sent: Tuesday, February 7, 2012 7:55:22 AM
Subject: [OpenIndiana-discuss] Kernel panic with Intel i7-2670QM CPU (HP
EliteBook 8560w)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello all,
A colleague attempted to boot oi_151a from CD on an HP E
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02/ 7/12 05:15 PM, Jerry Kemp wrote:
> I have the same issue/problem with my MacBook Pro 17" i7 and also with a 2010
> Mac Mini server.
>
> Solaris runs fine though from my 2007 Mac Mini.
>
> Jerry
>
>
> On 02/ 7/12 07:37 AM, Bryan N Iotti wro
I have the same issue/problem with my MacBook Pro 17" i7 and also with a 2010
Mac Mini server.
Solaris runs fine though from my 2007 Mac Mini.
Jerry
On 02/ 7/12 07:37 AM, Bryan N Iotti wrote:
> I had a MacBook Pro 17" i7 that would not boot OI, either through rEFIt or
> MBR emulation.
>
> Bry
oroll
Subject: [OpenIndiana-discuss] Kernel panic with Intel i7-2670QM CPU (HP
EliteBook 8560w)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello all,
A colleague attempted to boot oi_151a from CD on an HP EliteBook 8560w
laptop:
http://h10010.www1.hp.com/wwpc/us/en/sm/WF06a/321957-3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello all,
A colleague attempted to boot oi_151a from CD on an HP EliteBook 8560w
laptop:
http://h10010.www1.hp.com/wwpc/us/en/sm/WF06a/321957-321957-64295-3740645-4307559-5071171.html
... the variant with Intel i7-2670QM. He got an immediate kern
On 06/30/2011 09:22 AM, Michael Schuster wrote:
with dd, use "bs=" to increase the block size dd reads and
writes in one go - as you quote it, dd wrote 512 bytes at a time. A
good value to start with would be 1048576 (1MB).
Also, you may have "stopped" the command in an unintended way - Ctl-Z
do
On Thu, Jun 30, 2011 at 08:01, Johan Guldmyr wrote:
> On 06/28/2011 09:32 PM, Gordon Ross wrote:
>>>
>>> Here is the ::stack
>>> > http://img220.imageshack.us/i/oi148stack.jpg/
>>
>> If you look at what the other threads are doing
>> ::walk thread | ::findstack -v
>> I suspect you'll see that Z
On 06/28/2011 09:32 PM, Gordon Ross wrote:
Here is the ::stack
> http://img220.imageshack.us/i/oi148stack.jpg/
If you look at what the other threads are doing
::walk thread | ::findstack -v
I suspect you'll see that ZFS is still trying to import.
I would suggest you dd if=/dev/zero of=/your
On Tue, Jun 28, 2011 at 2:51 AM, Johan Guldmyr wrote:
> On 06/27/2011 04:42 PM, Steve Gonczi wrote:
[...]
>> - Original Message -
>> Now with the pictures, hope this works:
>>
>> http://imageshack.us/photo/my-images/402/oi151paniccdollarstatus.jpg/
>> http://img3.imageshack.us/i/oi151panic
On 06/27/2011 04:42 PM, Steve Gonczi wrote:
Hello,
This should be analyzed and root caused.
A ::stack woudl be useful to see the call parameters.
Without disassembling zio_buf_alloc() I can only guess that
the mutex_enter you see crashing is really in kmem_cache_alloc()
If that proves to be th
Hello,
This should be analyzed and root caused.
A ::stack woudl be useful to see the call parameters.
Without disassembling zio_buf_alloc() I can only guess that
the mutex_enter you see crashing is really in kmem_cache_alloc()
If that proves to be the case, I would verify the offset of cc_l
On 06/27/2011 10:52 AM, Mark wrote:
Have you tried deleting the solaris partition from the hard disk (via
format) ?
It can help prevent detection of an existing, broken filesystem.
Mark.
Hello Mark,
I deleted the partition via format, created a new one of 50% and then in
install I chose to
On 27/06/2011 7:11 p.m., Johan Guldmyr wrote:
On 06/27/2011 10:01 AM, Johan Guldmyr wrote:
When I try to install it, it kernel panics at 0%. By adding -k to the
grub line I got the the :msgbuf (attached in .zip file - several .jpg
files), but I don't understand most of it. If anybody could help
On 06/27/2011 10:01 AM, Johan Guldmyr wrote:
When I try to install it, it kernel panics at 0%. By adding -k to the
grub line I got the the :msgbuf (attached in .zip file - several .jpg
files), but I don't understand most of it. If anybody could help me shed
some light in this I would appreciate i
Hello! A bit of a long e-mail and large attachment but I want to be as
thorough as possible.
It says that the blade is pending HP-support for Solaris 10 Update 9 -
has anybody got it working?
We have several bl460c g1 running SunOS 5.11 snv_134.
When I try to install it, it kernel panics at 0
On Fri, Oct 22, 2010 at 3:28 AM, russell wrote:
> Hi Thorsten,
>
> I found that I experienced a similar kernel panic when attempting to perform
> a clean install of OpenIndiana which would occur at around 2% of the
> installation on a consistent basis.
>
> I eventually worked out that I had to us
Hi Thorsten,
I found that I experienced a similar kernel panic when attempting to
perform a clean install of OpenIndiana which would occur at around 2% of
the installation on a consistent basis.
I eventually worked out that I had to use GParted to delete any
partitions on the boot disc prio
Edit your boot line which has console=graphic ( Sorry, I may be paraphrasing,
I forget the exact wording)
to disable graphic console, replace console=graphic with -kd ( I think, the
intent is to
load mdb "early" ) .
You will have to delete the "splash image" line from the boot stanza as well.
Hi,
some time ago I tried to upgrade from OpenSolaris b134 to OpenIndiana, but
rebooting into OI always resulted in a kernel panic; see
http://openindiana.org/pipermail/openindiana-discuss/2010-September/000504.html
In another attempt today I booted the OI live USB image and tried
installing O
On Mon, Oct 4, 2010 at 12:05 PM, Thorsten Heit wrote:
> Hi,
>
>> It seems very easy to overlook, but it is my understanding that you
>> always need to run these steps in a specific order:
>> first just run import by itself
>>
>> pfexec zpool import
>>
>
> Great, didn't know about that. Thanks
Hi,
> It seems very easy to overlook, but it is my understanding that you
> always need to run these steps in a specific order:
> first just run import by itself
>
> pfexec zpool import
>
Great, didn't know about that. Thanks :-)
> Just run import by itself first and all should be well.
Michael schrieb am 04.10.2010 12:12:13:
> On Mon, Oct 4, 2010 at 12:05 PM, Thorsten Heit
wrote:
> > Hi,
> >
> >> It seems very easy to overlook, but it is my understanding that you
> >> always need to run these steps in a specific order:
> >> first just run import by itself
> >>
> >> pfexec zpo
*j...@opensolaris:~$ pfexec zpool import -f rpool
cannot import 'rpool': invalid vdev configuration
* It seems very easy to overlook, but it is my understanding that you always
need to run these steps in a specific order:
first just run import by itself
pfexec zpool import
pfexec zpool impo
Hi,
> This appears very similar to another issue with the bootfs
> specification which is normally transparent:
> http://opensolaris.org/jive/thread.jspa?messageID=315743
>
> Also make sure you have the current version of GRUB installed on
> *both* disks in your mirror, as it's responsible for sp
This appears very similar to another issue with the bootfs
specification which is normally transparent:
http://opensolaris.org/jive/thread.jspa?messageID=315743
Also make sure you have the current version of GRUB installed on
*both* disks in your mirror, as it's responsible for specifying the
boot
> I actually even reinstalled OI, but that didn't change anything.
> There's only a slight difference in the message after the "NOTICE:" line:
>
> "Cannot mount root on rpool/95 fstype zfs"
can you show the output of "zfs list -tall" as run from a different BE
(at least the relevant parts)? Maybe
> I actually even reinstalled OI, but that didn't change anything.
> There's only a slight difference in the message after the "NOTICE:" line:
>
> "Cannot mount root on rpool/95 fstype zfs"
can you show the output of "zfs list -tall" as run from a different BE
(at least the relevant parts)? Maybe
Hi,
> Sorry you are having trouble. Just a couple probing questions to open
up
> everyones mind. Before I forget, make sure you have burned a OS b134
live
> cd and a OI b147 live dvd before you do anything.
>
> The first thing I would try is booting into your b134 BE. Then export
all
> the
Sorry you are having trouble. Just a couple probing questions to open up
everyones mind. Before I forget, make sure you have burned a OS b134 live
cd and a OI b147 live dvd before you do anything.
The first thing I would try is booting into your b134 BE. Then export all
the pools besides rpool.
Hi,
by following the instructions on the wiki I just upgraded from OpenSolaris
b134 to OpenIndiana. Unfortunately booting into the new BE results in a
kernel panic:
...
NOTICE: zfs_parse_bootfs: error 22
Cannot mount root on rpool/101 fstype zfs
panic[cpu0]/thread=fbc2f260: vs_mountroo
99 matches
Mail list logo
