I need help immediately!
After moving hard drive from one SCO box to another and manualy
making entries in /dev I lost access to filesystems on that drive.
Fdisk sees correct partition table and divvy can show division table,
but all divisions are 'NON FS' with correct per-block layout.
fsck can't recognize fs type. If I use '-F HTFS' I got
error about bad MAGIC NUMBER.
Unfortunately I have no backup and data very important.
At least to files from one filesystem ( compressed cpio archives
of two filesystems at this drive ).
Does anybody have clue? Is it possible using fsdb correct this magic
number?
At which offset?
I make raw copy ( dd ) of divisions so I can experiment with drive.
Any suggestions are welcome.
Thanks at all!
--
Sincerely yours,
Artyom V. Viklenko.
-----------------------------------------------------------------------
Artyom V. Viklenko : MIPK-KSPU 21, Frunze Str. Kharkov Ukraine 61002
System Administrator : Phone: +38 0572 400026 Fax: +38 0572 474062
ar...@mipk-kspu.kharkov.ua http://www.freenet.kharkov.ua/~artem
I would guess that the SCSI adapter on the new system is applying a different
drive translation (number of heads/cylinders/sectors) to the hard disk than
the old SCSI adapter. This would allow Unix to see the fdisk table
correctly, and possibly the divvy table too, but the actual data in the
divisions would be in the wrong order to make any sense as a valid
filesystem.
Are you going from a non-Adaptec adapter to an Adaptec on the new system?
> Thanks at all!
>
> --
> Sincerely yours,
> Artyom V. Viklenko.
>
> -----------------------------------------------------------------------
> Artyom V. Viklenko : MIPK-KSPU 21, Frunze Str. Kharkov Ukraine 61002
> System Administrator : Phone: +38 0572 400026 Fax: +38 0572 474062
> ar...@mipk-kspu.kharkov.ua http://www.freenet.kharkov.ua/~artem
--
Bob Bailin
72027...@compuserve.com
"Artyom V. Viklenko" wrote:
>
> Hi, Guys!
>
> I need help immediately!
>
> After moving hard drive from one SCO box to another and manualy
> making entries in /dev I lost access to filesystems on that drive.
>
> Fdisk sees correct partition table and divvy can show division table,
> but all divisions are 'NON FS' with correct per-block layout.
In divvy, you can mark a partition as a particular file system type
but NOT have the file system created. Looking at the divvy man page,
you'll want to do a 't' and a 'p'.
> fsck can't recognize fs type. If I use '-F HTFS' I got
> error about bad MAGIC NUMBER.
>
> Unfortunately I have no backup and data very important.
> At least to files from one filesystem ( compressed cpio archives
> of two filesystems at this drive ).
Apparently the data isn't important if you've move the harddrive around
without a backup! There are hundreds of things that can effect a
harddrive when moving it, from getting the divisions wrong to
accidentally dropping it (and I've done both). Not making a
backup of critical data tells me that the data isn't critical.
Next time, take the time and do the backup first. Make two,
it's worth the effort
--
Jim Sullivan
Manager, Applied Technology Group
SCO www.sco.com
831 427 7108 - j...@sco.com
All much simpler. Both systems has EIDE drives. Also I cant use old
drive
on original system. Drive use NORMAL translation ( non-LBA ) and it is
recognized correctly in both systems. I think some trouble occurs during
first use of divvy.
I now. But in this case nothing happens with divisions itself. I have
done that.
But no result.
>
> > fsck can't recognize fs type. If I use '-F HTFS' I got
> > error about bad MAGIC NUMBER.
> >
> > Unfortunately I have no backup and data very important.
> > At least to files from one filesystem ( compressed cpio archives
> > of two filesystems at this drive ).
>
> Apparently the data isn't important if you've move the harddrive around
> without a backup! There are hundreds of things that can effect a
> harddrive when moving it, from getting the divisions wrong to
> accidentally dropping it (and I've done both). Not making a
> backup of critical data tells me that the data isn't critical.
> Next time, take the time and do the backup first. Make two,
> it's worth the effort
Agree. But sometimes it happen. Backups are not performed ...
I have no tape on old system. So after cpio and compress I move
archive to another system via ftp. But at this case ftp was not
performed.
But data still important!
>
> --
> Jim Sullivan
> Manager, Applied Technology Group
> SCO www.sco.com
> 831 427 7108 - j...@sco.com
--
Perhaps the old disk is not configured properly under the new
system; a different CHS geometry could give the problems
you're experiencing. If you did take note of 'em, please
try by using the 'dparam' command to 'stamp' the old
disk parameters on the old drive, so that the new system
is able to correctly recognize it. As an example :
dparam /dev/rhd10 <cyl> <hds> x x x x x <sects>
where 'x' is the value previously reported by dparam
concerning precomp, landing zone and so on (use
'dparam /dev/rhd10' to check 'em before writing 'em).
Hope this helps !
Best,
Roberto
--
---------------------------------------------------------------------
Roberto Zini email : fr...@strhold.it
Technical Support Manager -- Strhold Sistemi EDP Reggio Emilia(ITALY)
---------------------------------------------------------------------
"Has anybody around here seen an aircraft carrier?"
(Pete "Maverick" Mitchell - Top Gun)