|
|
Sponsored Content
Top Forums
UNIX for Dummies Questions & Answers
Bad magic number in super-block
Post 43188 by Jay on Wednesday 12th of November 2003 06:22:45 PM
11-12-2003
|
|
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
when installing a piece of third part software I get the error "Bad magic number" at one point when it tries to use libraries from the bea tuxedo server. Am I correct that this means that the software is expecting 32bit while I'm on 64bit? Is there a way around it or can it only be solved... (5 Replies)
Discussion started by: rein
5 Replies
2. Filesystems, Disks and Memory
Dear All,
i have a SCSI hard disk drive i'm installing on it solaris 5 and the workstation is sun sparc, i made an image of this H.D using Norton Ghost 6, so i took off the SCSI H.D from the sun workstation and put it on a Compaq server then i booted the server from the Norton Ghost floppy disk... (0 Replies)
Discussion started by: wesweshahaha
0 Replies
3. HP-UX
Error received when I tried to restore a blank disk with an 'auto recovery' DDS tape via HP-UX recovery system 2.0 onto a 1Gb SCSI. I assumed it would do the setup, wrong. Could someone tell me the procedure to initial disk for recovering files using cpio. The system is a HP-UX 9.04 version on a... (1 Reply)
Discussion started by: admin wanabee
1 Replies
4. Filesystems, Disks and Memory
I had a power outage a day ago and when the power came back on my FreeBSD 4.6 webserver had problems. It said it was unable to mount /var and made me start in single user mode and said to run fsck MANUALY. So i did and this is now what i get.
www# fsck /dev/ad0s1e
** /dev/ad0s1e
BAD SUPER... (4 Replies)
Discussion started by: matthewbane
4 Replies
5. Solaris
I want mount a disk. I have this error. I'm trying to correct with the superblock but i have the same error. Look my procedure.
bash-2.03# fsck -F ufs /dev/rdsk/c0t1d0s0
Alternate super block location: 9423392.
** /dev/rdsk/c0t1d0s0
BAD SUPER BLOCK: MAGIC NUMBER WRONG
USE AN ALTERNATE... (1 Reply)
Discussion started by: simquest
1 Replies
6. Filesystems, Disks and Memory
Whenever i run,
# fsck -F ufs /dev/dsk/c0t0d0s7
The following error prompt out:-
** /dev/dsk/c0t0d0s7
BAD SUPER BLOCK: MAGIC NUMBER WRONG
USE AN ALTERNATE SUPER-BLOCK TO SUPPLY NEEDED INFORMATION;
eg. fsck -o b=#
where # is the alternate super block. SEE fsck_ufs(1M).
... (3 Replies)
Discussion started by: beginningDBA
3 Replies
7. Solaris
I'll keep it fairly straight forward. I work with a Solaris server and magically today it decided to take a dump on me. At first it give a long list of files that couldn't be acessed before terminating the boot process and returning to the 'ok' prompt. Booting in single-user mode allowed me to run... (4 Replies)
Discussion started by: Aon
4 Replies
8. Filesystems, Disks and Memory
Hello all,
I have a hard drive that I can't repair.
The drive is WD15EARS - Filesystem ext4 ( not 100% sure )
It's used in a Synology DS110j NAS.
I try to run fsck -p /dev/sdb on the HD and I get this:
Bad magic number in super-block while trying to open /dev/sdb
/dev/sdb:
The superblock... (4 Replies)
Discussion started by: dallasw1983
4 Replies
9. Solaris
So we have a new to us v240 server with no OS installed. It has an outdated version of OB and ALOM so before we install the OS we want to update both. We have a DVD with the latest OB patch burned on it.
We do the boot cdrom command but receive the Bad Magic Number Error. Does an OS need to... (2 Replies)
Discussion started by: dunkpancakes
2 Replies
10. Solaris
This is first time post...found this forum when looking for possible solution to fix my sun pc. Just one day can't boot it already showing the following:
Boot device: disk File args:
Bad magic number in disk label
Can't open disk label package
Evaluating: boot
Can't open boot device... (40 Replies)
Discussion started by: SHuKoSuGi
40 Replies
LEARN ABOUT SUSE
ntfs-3g.probe
NTFS-3G.PROBE(8) System Manager's Manual NTFS-3G.PROBE(8) NAME
ntfs-3g.probe - Probe an NTFS volume mountability SYNOPSIS
ntfs-3g.probe <--readonly|--readwrite> volume DESCRIPTION
The ntfs-3g.probe utility tests a volume if it's NTFS mountable read-only or read-write, and exits with a status value accordingly. The volume can be a block device or image file. OPTIONS
Below is a summary of the options that ntfs-3g.probe accepts. -r, --readonly Test if the volume can be mounted read-only. -w, --readwrite Test if the volume can be mounted read-write. -h, --help Display help and exit. EXAMPLE
Test if /dev/sda1 can be mounted read-write: ntfs-3g.probe --readwrite /dev/sda1 EXIT CODES
The exit codes are as follows: 0 Volume is mountable. 11 Syntax error, command line parsing failed. 12 The volume doesn't have a valid NTFS. 13 Inconsistent NTFS, hardware or device driver fault, or unsetup SoftRAID/FakeRAID hardware. 14 The NTFS partition is hibernated. 15 The volume was not cleanly unmounted. 16 The volume is already exclusively opened and in use by a kernel driver or software. 17 Unsetup SoftRAID/FakeRAID hardware. 18 Unknown reason. 19 Not enough privilege to mount. 20 Out of memory. 21 Unclassified FUSE error. KNOWN ISSUES
Please see http://ntfs-3g.org/support.html for common questions and known issues. If you think you have found an undocumented problem in the latest release of the software then please send an email describing it in detail. You can contact the development team on the ntfs-3g-devel@lists.sf.net address. AUTHORS
ntfs-3g.probe was written by Szabolcs Szakacsits (szaka@ntfs-3g.org). THANKS
Alon Bar-Lev has integrated the utility into the NTFS-3G build process and tested it with Erik Larsson before the public release. SEE ALSO
ntfs-3g(8) ntfs-3g.probe 2010.3.6 January 2008 NTFS-3G.PROBE(8)