11-12-2003
Ok I'm getting really confused what has gone on with my system. I have been running mandrake on my system for over 6 months with no problem using the following fstab configeration:
/dev/hda5 / ext3 defaults 1 1
none /dev/pts devts mode 0620 00
none /dev/shm tmpfs defaults 0 0
/dev/hda8 /home ext3 defaults 1 2
/dev/hda1 /home/jay/windows/c: ntfs
/dev/hda6 /home/jay/windows/e: ntfs
/mnt/cdrom (etc)
/mnt/floppy (etc)
none /proc proc defaults 0 0
/dev/hda7 swap swap defaults 0 0
As I was getting the super-block error against hda8 I commented it out of the fstab.
As a last ditch attempt to get it working for some reason I decided to mount hda8 manually. I tried manually mounting it as ntfs and it mounted?? Checked what was on there and it was my windows e: drive?? For some reason the following has changed from:
hda1 = NTFS c:
hda2 = ??
hda5 = ext3 / (root)
hda6 = NTFS e:
hda7 = Swap swap
hda8 = ext3 /home
to:
hda1 = NTFS c:
hda2 = ??
hda5 = ext3 / (root)
hda6 = Not sure (Swap?? not mount yet so not 100% sure)
hda7 = ext3 /home
hda8 = NTFS e:
How has the above changed?? Possible because I installed Partition magic 8?? Although I installed it, it was only to create rescue disk to fix someone else computer as I needed to save some data for them. All I did was go into the program but never modified anything!!
Can anyone shed any light on this?
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 DEBIAN
scrounge-ntfs
scrounge-ntfs(8) BSD System Manager's Manual scrounge-ntfs(8)
NAME
scrounge-ntfs -- helps retrieve data from corrupted NTFS partitions
SYNOPSIS
scrounge-ntfs -l disk
scrounge-ntfs -s disk
scrounge-ntfs [-m mftoffset] [-c clustersize] [-o outdir] disk start end
DESCRIPTION
scrounge-ntfs is a utility that can rescue data from corrupted NTFS partitions. It writes the files retrieved to another working file system.
Certain information about the partition needs to be known in advance.
The -l mode is meant to be run in advance of the data corruption, with the output stored away in a file. This allows scrounge-ntfs to recover
data reliably. See the 'NOTES' section below for recover info when this isn't the case.
OPTIONS
The options are as follows:
-c The cluster size (in sectors). When not specified a default of 8 is used.
-l List partition information for a drive. This will only work when the partition table for the given drive is intact.
-m When recovering data this specifies the location of the MFT from the beginning of the partition (in sectors). If not specified
then no directory information can be used, that is, all rescued files will be written to the same directory.
-o Directory to put rescued files in. If not specified then files will be placed in the current directory.
-s Search disk for partition information. (Not implemented yet).
disk The raw device used to access the disk which contains the NTFS partition to rescue files from. eg: '/dev/hdc'
start The beginning of the NTFS partition (in sectors).
end The end of the NTFS partition (in sectors)
NOTES
If you plan on using this program sucessfully you should prepare in advance by storing a copy of the partition information. Use the -l option
to do this. Eventually searching for disk partition information will be implemented, which will solve this problem.
When only one partition exists on a disk or you want to rescue the first partition there are ways to guess at the sector sizes and MFT loca-
tion. See the scrounge-ntfs web page for more info:
http://memberwebs.com/swalter/software/scrounge/
AUTHOR
Stef Walter <stef@memberwebs.com>
scrounge-ntfs June 1, 2019 scrounge-ntfs