OpenSolaris

Discussions Communities Projects Download Source Browser

Home » OpenSolaris Forums » indiana » discuss

Thread: Image-update from 95 to 96 - problem

Welcome, Guest Help
Login Login
Guest Settings Guest Settings
Reply to this Thread Reply to this Thread Search Forum Search Forum Back to Thread List Back to Thread List

Permlink Replies: 6 - Last Post: Sep 10, 2008 6:32 AM by: andrewk8
mnespen

Posts: 44
From: NO

Registered: 5/15/06
Image-update from 95 to 96 - problem
Posted: Sep 6, 2008 1:57 AM
To: Projects » indiana » discuss
  Click to reply to this thread Reply

Hi,
Now, I've lived through several updates, but now, when I should update my laptop from
95to 96, I get problems.

The image-update ends pretty soon in an error-message, and booting into the
new be gives me a lot of kernel-symbol errors. Then I reboot to the old BE, and destroys the
new one.

Any hinst?

Here's my output:

bash-3.2# beadm list

BE Active Active on Mountpoint Space
Name reboot Used
---- ------ --------- ---------- -----
opensolaris yes yes / 4.32G




esm@esmpc:~/bin$ BUILD=`uname -v | sed s/snv_//`
esm@esmpc:~/bin$ echo ${BUILD}
95
esm@esmpc:~/bin$ pfexec pkg refresh
esm@esmpc:~/bin$ pfexec pkg install SUNWipkg@0.5.11-0.${BUILD}
Nothing to install in this image (is this package already installed?)
esm@esmpc:~/bin$ pfexec pkg install entire@0.5.11-0.${BUILD}
Nothing to install in this image (is this package already installed?)
esm@esmpc:~/bin$ pfexec pkg image-update
Checking that SUNWipkg (in '/') is up to date...
DOWNLOAD PKGS FILES XFER (MB)
SUNWthunderbird 565/566 0/13 0.00/5.19 PHASE ACTIONS
Removal Phase 3367/3367
Install Phase 3337/3337
Update Phase 20846/85386 Action upgrade failed for 'var/svc/profile/inetd_generic.xml' (pkg:/SUNWcs):
OSError: [Errno 90] Number of symbolic links encountered during path name traversal exceeds MAXSYMLINKS: '/tmp/tmpYxNUva/var/svc/profile/inetd_generic.xml'
pkg:
An unexpected error happened during image-update: [Errno 90] Number of symbolic links encountered during path name traversal exceeds MAXSYMLINKS: '/tmp/tmpYxNUva/var/svc/profile/inetd_generic.xml'
The running system has not been modified. Modifications were only made to a clone of the running system. This clone is mounted at /tmp/tmpYxNUva should you wish to inspect it.
Traceback (most recent call last):
File "/usr/bin/pkg", line 1830, in ?
ret = main_func()
File "/usr/bin/pkg", line 1792, in main_func
return image_update(img, pargs)
File "/usr/bin/pkg", line 537, in image_update
img.imageplan.execute()
File "/usr/lib/python2.4/vendor-packages/pkg/client/imageplan.py", line 615, in execute
p.execute_update(src, dest)
File "/usr/lib/python2.4/vendor-packages/pkg/client/pkgplan.py", line 270, in execute_update
dest.install(self, src)
File "/usr/lib/python2.4/vendor-packages/pkg/actions/file.py", line 145, in install
os.chmod(temp, mode)
OSError: [Errno 90] Number of symbolic links encountered during path name traversal exceeds MAXSYMLINKS: '/tmp/tmpYxNUva/var/svc/profile/inetd_generic.xml'
pkg:

This is an internal error, please let the developers know about this
problem by filing a bug at http://defect.opensolaris.org and including the
above traceback and the output of 'pkg version'.
esm@esmpc:~/bin$
esm@esmpc:~/bin$ pfexec pkg version
bfe78d71dc9a



Yours
Espen Martinsen

herrib

Posts: 60
From: FR

Registered: 8/28/07
Re: Image-update from 95 to 96 - problem
Posted: Sep 6, 2008 4:46 AM   in response to: mnespen
To: Projects » indiana » discuss
  Click to reply to this thread Reply

Hello,

Have a look first to the following bug report: http://defect.opensolaris.org/bz/show_bug.cgi?id=3262

A workaround, I've used, consists of:

* deleting the existing /var/svc/profile/inetd_generic.xml and replacing it by an empty file
* then restarting the procedure (pfexec pkg image-update -v ....).

In case of failure, destroy the image that has been created (beadm unmount -f opensolaris-X and then beadm destroy -f opensolaris-X), reindex the packages (packages pkg build-index) and launch on more time pkg image-update -v.

mnespen

Posts: 44
From: NO

Registered: 5/15/06
Re: Image-update from 95 to 96 - problem
Posted: Sep 6, 2008 7:32 AM   in response to: herrib
To: Projects » indiana » discuss
  Click to reply to this thread Reply

Thanks, I'm embarrassed, should have read the error-message more carefully myself,
but my wife was shouting at me, I've promised to come with her shopping...

Thanks!

smiles

Posts: 2
From:

Registered: 9/8/08
Re: Image-update from 95 to 96 - problem
Posted: Sep 8, 2008 6:35 AM   in response to: mnespen
To: Projects » indiana » discuss
  Click to reply to this thread Reply

Hello.

I have lived through several updates too, and if there were errors i could find proper solution here (or at google).
But now i can't. The problem is:

The system crashed and rebooted every time the command pfexec pkg install SUNWipkg@0.5.11-0.${BUILD} starts.
(or pfexec pkg image-update, if omit previous command)


/var/adm/messages:
Sep 8 13:29:52 smiles unix: [ID 836849 kern.notice]
Sep 8 13:29:52 smiles ^Mpanic[cpu0]/thread=ffffff014e3f47c0:
Sep 8 13:29:52 smiles genunix: [ID 335743 kern.notice] BAD TRAP: type=e (#pf Page fault) rp=ffffff0004a50620 addr=220 occurred in module "unix" due to a
NULL pointer dereference
Sep 8 13:29:52 smiles unix: [ID 100000 kern.notice]
Sep 8 13:29:52 smiles unix: [ID 839527 kern.notice] packagemanager:
Sep 8 13:29:52 smiles unix: [ID 753105 kern.notice] #pf Page fault
Sep 8 13:29:52 smiles unix: [ID 532287 kern.notice] Bad kernel fault at addr=0x220
Sep 8 13:29:52 smiles unix: [ID 243837 kern.notice] pid=648, pc=0xfffffffffb842a1b, sp=0xffffff0004a50718, eflags=0x10246
Sep 8 13:29:52 smiles unix: [ID 211416 kern.notice] cr0: 80050033<pg,wp,ne,et,mp,pe> cr4: 6f8<xmme,fxsr,pge,mce,pae,pse,de>
Sep 8 13:29:52 smiles unix: [ID 624947 kern.notice] cr2: 220
Sep 8 13:29:52 smiles unix: [ID 625075 kern.notice] cr3: 35c7000
Sep 8 13:29:52 smiles unix: [ID 625715 kern.notice] cr8: c
Sep 8 13:29:52 smiles unix: [ID 100000 kern.notice]
Sep 8 13:29:52 smiles unix: [ID 592667 kern.notice] rdi: 220 rsi: 4 rdx: ffffff014e3f47c0
Sep 8 13:29:52 smiles unix: [ID 592667 kern.notice] rcx: 0 r8: 1d0 r9: 10ed7
Sep 8 13:29:52 smiles unix: [ID 592667 kern.notice] rax: 0 rbx: 4 rbp: ffffff0004a50770
Sep 8 13:29:52 smiles unix: [ID 592667 kern.notice] r10: 0 r11: 0 r12: 220
Sep 8 13:29:52 smiles unix: [ID 592667 kern.notice] r13: 0 r14: 0 r15: ffffff0147cec580
Sep 8 13:29:52 smiles unix: [ID 592667 kern.notice] fsb: 0 gsb: fffffffffbc2a7f0 ds: 4b
Sep 8 13:29:52 smiles unix: [ID 592667 kern.notice] es: 4b fs: 0 gs: 1c3
Sep 8 13:29:52 smiles unix: [ID 592667 kern.notice] trp: e err: 2 rip: fffffffffb842a1b
Sep 8 13:29:52 smiles unix: [ID 592667 kern.notice] cs: 30 rfl: 10246 rsp: ffffff0004a50718
Sep 8 13:29:52 smiles unix: [ID 266532 kern.notice] ss: 38
Sep 8 13:29:52 smiles unix: [ID 100000 kern.notice]


Any suggestion?

andrewk8

Posts: 595
From:

Registered: 3/12/08
Re: Image-update from 95 to 96 - problem
Posted: Sep 9, 2008 11:30 AM   in response to: smiles
To: Projects » indiana » discuss
  Click to reply to this thread Reply

Can you scrub the root pool and see if it detects any errors (pfexec zpool scrub rpool)? It could be a hardware fault.

Cheers

Andrew.

smiles

Posts: 2
From:

Registered: 9/8/08
Re: Image-update from 95 to 96 - problem
Posted: Sep 10, 2008 5:20 AM   in response to: andrewk8
To: Projects » indiana » discuss
  Click to reply to this thread Reply

Thank you. The scrubbing detected one permanent error, continued to 100% and crashed the system. After reboot the scrubbing resumed and crashed again at 100%. Ans so on until i terminate the scrubbing.

Sep 10 15:41:47 smiles unix: [ID 836849 kern.notice]
Sep 10 15:41:47 smiles ^Mpanic[cpu0]/thread=ffffff0004189c80:
Sep 10 15:41:47 smiles genunix: [ID 335743 kern.notice] BAD TRAP: type=e (#pf Page fault) rp=ffffff0004188d30 addr=4e8 occurred in module "
unix" due to a NULL pointer dereference
Sep 10 15:41:47 smiles unix: [ID 100000 kern.notice]
Sep 10 15:41:47 smiles unix: [ID 839527 kern.notice] sched:
Sep 10 15:41:47 smiles unix: [ID 753105 kern.notice] #pf Page fault
Sep 10 15:41:47 smiles unix: [ID 532287 kern.notice] Bad kernel fault at addr=0x4e8
Sep 10 15:41:47 smiles unix: [ID 243837 kern.notice] pid=0, pc=0xfffffffffb842a1b, sp=0xffffff0004188e28, eflags=0x10246
Sep 10 15:41:47 smiles unix: [ID 211416 kern.notice] cr0: 8005003b<pg,wp,ne,et,ts,mp,pe> cr4: 6f8<xmme,fxsr,pge,mce,pae,pse,de>
Sep 10 15:41:47 smiles unix: [ID 624947 kern.notice] cr2: 4e8
Sep 10 15:41:47 smiles unix: [ID 625075 kern.notice] cr3: 3400000
Sep 10 15:41:47 smiles unix: [ID 625715 kern.notice] cr8: c
Sep 10 15:41:47 smiles unix: [ID 100000 kern.notice]
Sep 10 15:41:47 smiles unix: [ID 592667 kern.notice] rdi: 4e8 rsi: 4c008900 rdx: ffffff0004189c80
Sep 10 15:41:47 smiles unix: [ID 592667 kern.notice] rcx: 2 r8: ffffff01484c9a80 r9: 0
Sep 10 15:41:47 smiles unix: [ID 592667 kern.notice] rax: 0 rbx: 0 rbp: ffffff0004188ea0
Sep 10 15:41:47 smiles unix: [ID 592667 kern.notice] r10: ffffff01711c42d0 r11: 5042474650454f r12: ffffff014d39a040
Sep 10 15:41:47 smiles unix: [ID 592667 kern.notice] r13: ffffff014d39a040 r14: ffffff0147cec580 r15: 0
Sep 10 15:41:47 smiles unix: [ID 592667 kern.notice] fsb: fffffd7fff000200 gsb: fffffffffbc2a7f0 ds: 4b
Sep 10 15:41:47 smiles unix: [ID 592667 kern.notice] es: 4b fs: 0 gs: 0
Sep 10 15:41:47 smiles unix: [ID 592667 kern.notice] trp: e err: 2 rip: fffffffffb842a1b
Sep 10 15:41:47 smiles unix: [ID 592667 kern.notice] cs: 30 rfl: 10246 rsp: ffffff0004188e28
Sep 10 15:41:47 smiles unix: [ID 266532 kern.notice] ss: 38
Sep 10 15:41:47 smiles unix: [ID 100000 kern.notice]
Sep 10 15:41:47 smiles genunix: [ID 655072 kern.notice] ffffff0004188c10 unix:die+c8 ()
Sep 10 15:41:47 smiles genunix: [ID 655072 kern.notice] ffffff0004188d20 unix:trap+13b9 ()
Sep 10 15:41:47 smiles genunix: [ID 655072 kern.notice] ffffff0004188d30 unix:cmntrap+e9 ()
Sep 10 15:41:47 smiles genunix: [ID 655072 kern.notice] ffffff0004188ea0 unix:mutex_enter+b ()
Sep 10 15:41:47 smiles genunix: [ID 655072 kern.notice] ffffff0004188fb0 zfs:scrub_visitbp+47f ()
Sep 10 15:41:47 smiles genunix: [ID 655072 kern.notice] ffffff00041890c0 zfs:scrub_visitbp+42c ()
Sep 10 15:41:47 smiles genunix: [ID 655072 kern.notice] ffffff00041891d0 zfs:scrub_visitbp+1bd ()
Sep 10 15:41:47 smiles genunix: [ID 655072 kern.notice] ffffff00041892e0 zfs:scrub_visitbp+1bd ()
Sep 10 15:41:47 smiles genunix: [ID 655072 kern.notice] ffffff00041893f0 zfs:scrub_visitbp+1bd ()
Sep 10 15:41:47 smiles genunix: [ID 655072 kern.notice] ffffff0004189500 zfs:scrub_visitbp+1bd ()
Sep 10 15:41:47 smiles genunix: [ID 655072 kern.notice] ffffff0004189610 zfs:scrub_visitbp+1bd ()
Sep 10 15:41:47 smiles genunix: [ID 655072 kern.notice] ffffff0004189720 zfs:scrub_visitbp+1bd ()
Sep 10 15:41:47 smiles genunix: [ID 655072 kern.notice] ffffff0004189830 zfs:scrub_visitbp+2ea ()
Sep 10 15:41:47 smiles genunix: [ID 655072 kern.notice] ffffff0004189880 zfs:scrub_visit_rootbp+4e ()
Sep 10 15:41:47 smiles genunix: [ID 655072 kern.notice] ffffff00041898f0 zfs:scrub_visitds+82 ()
Sep 10 15:41:47 smiles genunix: [ID 655072 kern.notice] ffffff0004189aa0 zfs:dsl_pool_scrub_sync+109 ()
Sep 10 15:41:47 smiles genunix: [ID 655072 kern.notice] ffffff0004189b10 zfs:dsl_pool_sync+158 ()
Sep 10 15:41:47 smiles genunix: [ID 655072 kern.notice] ffffff0004189bb0 zfs:spa_sync+254 ()
Sep 10 15:41:47 smiles genunix: [ID 655072 kern.notice] ffffff0004189c60 zfs:txg_sync_thread+226 ()
Sep 10 15:41:47 smiles genunix: [ID 655072 kern.notice] ffffff0004189c70 unix:thread_start+8 ()
Sep 10 15:41:47 smiles unix: [ID 100000 kern.notice]
Sep 10 15:41:47 smiles genunix: [ID 672855 kern.notice] syncing file systems...
Sep 10 15:41:47 smiles genunix: [ID 904073 kern.notice] done
Sep 10 15:41:48 smiles genunix: [ID 111219 kern.notice] dumping to /dev/dsk/c8d0s1, offset 429391872, content: kernel
Sep 10 15:42:00 smiles genunix: [ID 409368 kern.notice] ^M100% done: 194442 pages dumped, compression ratio 3.52,
Sep 10 15:42:00 smiles genunix: [ID 851671 kern.notice] dump succeeded

andrewk8

Posts: 595
From:

Registered: 3/12/08
Re: Image-update from 95 to 96 - problem
Posted: Sep 10, 2008 6:32 AM   in response to: smiles
To: Projects » indiana » discuss
  Click to reply to this thread Reply

Your hard disk may or memory may be faulty. Back up the data off this disk, then try re-installing to a different hard disk. If you still have problems, runa memory checker on this system, for example memtest86.

Cheers

Andrew.




Terms of Use | Privacy | Trademarks | Copyright Policy | Site Guidelines
Your use of this web site or any of its content or software indicates your agreement to be bound by these Terms of Use.
Copyright © 1995-2005 Sun Microsystems, Inc.