Re: BAD SUPER BLOCK: MAGIC NUMBER WRONG

From: Mr Ping (_NO_SPAM__at_telia.com)
Date: 02/23/04


Date: Mon, 23 Feb 2004 15:58:38 +0100

Mr Ping wrote:
> pidbel wrote:
>> "Mr Ping" <_NO_SPAM_@telia.com> wrote in message
>> news:c1cqs5$1hhs19$1@ID-101404.news.uni-berlin.de...
>>> Tony Walton wrote:
>>>> Mr Ping wrote:
>>>>> Hi !
>>>>>
>>>>> I have add a new disk to my sparc 10, with Solaris 8.
>>>>>
>>>>> I have mounted this:
>>>>
>>>> No you haven't. /dev/rdsk/c0t1d0s0 doesn't feature in the output
>>>> below.
>>>>
>>>>>
>>>>> / (/dev/dsk/c0t0d0s0 ): 31064 blocks 20857
>>>>> files /usr (/dev/dsk/c0t0d0s6 ): 172902 blocks
>>>>> 192672 files /proc (/proc ): 0
>>>>> blocks 932 files /dev/fd (fd ): 0
>>>>> blocks 0 files /etc/mnttab (mnttab ): 0
>>>>> blocks 0 files /var (/dev/dsk/c0t1d0s6 ): 554710
>>>>> blocks 161273 files /var/run (swap ):
>>>>> 310560 blocks 9609 files /tmp (swap ):
>>>>> 310560 blocks 9609 files /opt (/dev/dsk/c0t0d0s5 ):
>>>>> 47564 blocks 13368 files /export/home (/dev/dsk/c0t0d0s7 ):
>>>>> 1302516 blocks 253743 files /usr/openwin (/dev/dsk/c0t0d0s1
>>>>> ): 167084 blocks 116062 files
>>>>>
>>>>> But i get error when i reboot.
>>>>>
>>>>> ** /dev/rdsk/c0t1d0s0
>>>>> BAD SUPER BLOCK: MAGIC NUMBER WRONG
>>>>> USE AN ALTERNATE SUPER-BLOCK TO SUPPLY NEEDED INFORMATION;
>>>>> eg. fsck [-F ufs] -o b=# [special ...]
>>>>> where # is the alternate super block. SEE fsck_ufs(1M).
>>>>>
>>>>> If try to run fsck -F ufs /dev/rdsk/c0t1d0s0 i still get magic
>>>>> number wrong.
>>>>>
>>>>> Any sugestion, for my problem "please" ?
>>>>
>>>>
>>>> Did you actually *create* a filesystem on that partition after you
>>>> added the disk? Before doing so, make sure that partition 0 doesn't
>>>> overlap anything else, though!
>>>
>>> I did a format on the new disk.
>>> This disk have been in a other sun, before.
>>> And i did a newfs also.
>>>
>>> If i do a verify from the the format is show this:
>>>
>>> format> ver
>>>
>>> Primary label contents:
>>>
>>> Volume name = < >
>>> ascii name = <SUN0424 cyl 1151 alt 2 hd 9 sec 80>
>>> pcyl = 2500
>>> ncyl = 1151
>>> acyl = 2
>>> nhead = 9
>>> nsect = 80
>>> Part Tag Flag Cylinders Size Blocks
>>> 0 root wm 0 - 91 32.34MB (92/0/0)
>>> 66240 1 swap wu 92 - 183 32.34MB (92/0/0)
>>> 66240 2 backup wu 0 - 1150 404.65MB
>>> (1151/0/0) 828720 3 unassigned wm 0 0
>>> (0/0/0) 0 4 unassigned wm 0 0
>>> (0/0/0) 0 5 unassigned wm 0 0
>>> (0/0/0) 0 6 var wm 184 - 1150 339.96MB
>>> (967/0/0) 696240 7 unassigned wm 0 0
>>> (0/0/0) 0
>>>
>>> //Jan
>>>
>>>
>>
>> Try fsck -n 32 /dev/rdsk/.....
>
> On what part ?
> As you see i have already use the c0t1d0s6 fot /var.
>
> //Jan

I try the fsck -n 32 on c0t1d0s0.

#fsck -n 32 /dev/rdsk/c0t1d0s0
fsck: operation not applicable to FSType nfs
fsck: operation not applicable to FSType nfs

//Jan



Relevant Pages

  • Re: Corrupt file system help
    ... I could not access it via console or ... > although I could still ping it. ... It sits on it for days trying to fsck. ...
    (comp.unix.bsd.freebsd.misc)
  • RE: how to run fsck on corrupted / drive?
    ... I also found fsck in /usr/sbin/ ... fsck not applicable for FSType nfs" ... drive with / on it is failing to auto-recover. ... booted the machine off cdrom. ...
    (SunManagers)