Thank you to all that did offer me helping hand, in particular to Peter Wallis who did pointed me to the clock problem on the system. I did change my time from "Fri Nov 26 04:50:15 EWT 1909" to "Tue Jul 6 11:15:00 EDT 2004" Then next step was to find alternate superblock and run fsck against that superblock on all the slices that I had on this hard drive. After this I was able to boot up my Solaris 2.8 and everything is working fine. Another option was suggested to boot up the system from CDROM, but bad part about this is that X1 did not have CD-ROM drive :( Anyway my system is back online. Regards, Chris -==================================== Executing last command: boot Boot device: disk File and args: SunOS Release 5.8 Version Generic_108528-11 64-bit Copyright 1983-2001 Sun Microsystems, Inc. All rights reserved. WARNING: Time-of-day chip unresponsive; dead batteries? configuring IPv4 interfaces: dmfe0 dmfe0:1 dmfe1. Type control-d to proceed with normal startup, (or give root password for system maintenance): single-user privilege assigned to /dev/console. Entering System Maintenance Mode Nov 26 04:50:12 su: 'su root' succeeded for root on /dev/console Sun Microsystems Inc. SunOS 5.8 Generic February 2000 # date Fri Nov 26 04:50:15 EWT 1909 # # date 070611152004 Tue Jul 6 11:15:00 EDT 2004 # # newfs -N /dev/dsk/c0t0d0s3 /dev/rdsk/c0t0d0s3: 4096320 sectors in 1004 cylinders of 16 tracks, 255 sectors 2000.2MB in 44 cyl groups (23 c/g, 45.82MB/g, 11264 i/g) super-block backups (for fsck -F ufs -o b=#) at: 32, 94128, 188224, 282320, 376416, 470512, 564608, 658704, 752800, 846896, 940992, 1035088, 1129184, 1223280, 1317376, 1411472, 1501472, 1595568, 1689664, 1783760, 1877856, 1971952, 2066048, 2160144, 2254240, 2348336, 2442432, 2536528, 2630624, 2724720, 2818816, 2912912, 3002912, 3097008, 3191104, 3285200, 3379296, 3473392, 3567488, 3661584, 3755680, 3849776, 3943872, 4037968, # fsck -o b=3661584 /dev/rdsk/c0t0d0s3 Alternate super block location: 3661584. ** /dev/rdsk/c0t0d0s3 ** Currently Mounted on ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups FREE BLK COUNT(S) WRONG IN SUPERBLK SALVAGE? y 6064 files, 137503 used, 1985478 free (14 frags, 248183 blocks, 0.0% fragmentation) ***** FILE SYSTEM WAS MODIFIED ***** # -----Original Message----- From: sunmanagers-bounces@sunmanagers.org [mailto:sunmanagers-bounces@sunmanagers.org] On Behalf Of Wianecki, Christopher Sent: Tuesday, July 06, 2004 10:46 AM To: sunmanagers@sunmanagers.org Subject: Cant boot X1 - fsck problem?!? I have Solaris 2.8 installed on my X1. I have problem booting that server up. Id does complain about disks / partitions. When I run fsck it does show everything is fine but still system complains about partition not ok and it does ask me to use fsck each time I try to boot it. Does anyone have any suggestions what could I do to force system to boot or somehow recognize those drives as fine? Here is output. After running fsck I do reboot the system or exit from maintenance mode and it still does complain about those partitions. Boot device: disk File and args: SunOS Release 5.8 Version Generic_108528-11 64-bit Copyright 1983-2001 Sun Microsystems, Inc. All rights reserved. WARNING: Time-of-day chip unresponsive; dead batteries? configuring IPv4 interfaces: dmfe0 dmfe0:1 dmfe1. Hostname: misty mount: the state of /dev/dsk/c0t0d0s0 is not okay and it was attempted to be mounted read/write mount: Please run fsck and try again NOTICE: dmfe0: PHY 1 link up 100 Mbps Full-Duplex NOTICE: dmfe1: PHY 1 link up 100 Mbps Full-Duplex mount: the state of /dev/dsk/c0t0d0s3 is not okay and it was attempted to be mounted read/write mount: Please run fsck and try again failed to open /etc/coreadm.confsyseventd: Unable to open daemon lock file '/etc/sysevent/syseventd_lock': 'Read-only file system'mount: the state of /dev/dsk/c0t0d0s4 is not okay and it was attempted to be mounted read/write mount: Please run fsck and try again mount: mount-point /var/run does not exist. INIT: Cannot create /var/adm/utmpx INIT: failed write of utmpx entry:" " INIT: failed write of utmpx entry:" " INIT: SINGLE USER MODE Type control-d to proceed with normal startup, (or give root password for system maintenance): single-user privilege assigned to /dev/console. Entering System Maintenance Mode Nov 26 04:58:54 su: 'su root' succeeded for root on /dev/console Sun Microsystems Inc. SunOS 5.8 Generic February 2000 # fsck ** /dev/rdsk/c0t0d0s0 ** Last Mounted on / ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 1667 files, 48878 used, 1934601 free (329 frags, 241784 blocks, 0.0% fragmentation) ** /dev/rdsk/c0t0d0s3 ** Currently Mounted on /usr ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 6064 files, 137503 used, 1845976 free (904 frags, 230634 blocks, 0.0% fragmentation) ** /dev/rdsk/c0t0d0s4 ** Last Mounted on /var ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 1727 files, 716454 used, 4319768 free (1816 frags, 539744 blocks, 0.0% fragmentation) www.sothebys.com ********************************************************************** _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers www.sothebys.com ********************************************************************** _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagersReceived on Tue Jul 6 16:32:08 2004
This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:43:34 EST