Re: All JFS partitions unreadable
- From: "Dave Parsons" <dwparsons@xxxxxxxxx>
- Date: Tue, 20 Mar 2007 07:19:31 +0100
On Mon, 19 Mar 2007 22:09:40 UTC, "James J. Weinkam" <jjw@xxxxxxxxx> wrote:
Dave Parsons wrote:Yes I'm afraid it does.
On Mon, 19 Mar 2007 01:46:30 UTC, "William L. Hartzell" <wlhartzell@xxxxxxxxx> wrote:
Sir:
Jim Moe wrote:
Dave Parsons wrote:
A few days ago I booted a box with a mixture of 3 JFS
partitions on 2 disks and 3 HPFS partitions to find that
none of the JFS partitions were readable. I don't remember
doing anything unusual when I shut it down the day before.
Just as a sanity check...
Is the ifs=jfs.ifs line the *first* IFS in config.sys? It must be loaded
before any other filesystem, especially hpfs and fat32.
It is beginning to sound like the partitions have been marked hidden or
something added to each partition that makes the superblocks (FAT) not
readable. He needs to take the data files that the Dfsee author
requires to figure this out.
Yes, I spent many hours with DFSee yesterday and all that I could
see was that after a complete boot to the GUI then in DFSee
Display -> Volume overview
DFsee says
OS Vulume info : D: Not ready, no size info, fs: UNKNOWN
for all the JFS partitions and the FAT one.
If I boot to the command line from the boot blob, then they all
show correctly and are accessible.
It seems that something late in the boot process marks them
not ready, but what & why, I have no idea at the moment.
I presume that most of the dfsee tests display data from the
disk itself, but this volume overview test uses, possibly different,
OS API calls.
Another thing, I took the non-system disk out and put it into
another PC, no problems at all!
Are you doing a warm or cold boot? My kids' desktop (Asus M2NBP-VM CSM with one
Samsung SP2504C 250GB SATA drive) only detects and operates the JFS volumes on a
cold boot. After a warm boot, it not only does not see the JFS volumes, but
DFSee shows an incorrect size for the extended partition. We have not been able
to figure out what causes this or how to fix it. We suspect that either the
drive or the onboard controller (SATA) does not reset properly on a warm start.
Once the system boots correctly, the drives and their contents are intact.
There has never been any instance of data corruption.
My own desktop (Asus A8N5X with two Seagate Barracuda ST3250824XS 250GB SATA
drives) usually sees the JFS drives on a warm boot but occasionally fails to do
so. A cold boot always cures the problem.
YMMV
Over the weekend I performed very many reboots, some warm & some cold,
but the results were consistently bad, the 3 JFS & 1 FAT always failed.
The PC in question is quite old now, about 1999, IIRC, the system
disk is an 8GB from that era and the data disk is a 60GB Seagate from
about a year ago.
Dave
.
- References:
- All JFS partitions unreadable
- From: Dave Parsons
- Re: All JFS partitions unreadable
- From: Jim Moe
- Re: All JFS partitions unreadable
- From: William L. Hartzell
- Re: All JFS partitions unreadable
- From: Dave Parsons
- Re: All JFS partitions unreadable
- From: James J. Weinkam
- All JFS partitions unreadable
- Prev by Date: Re: All JFS partitions unreadable
- Next by Date: Re: Some partitions unreadable when boot complete. was: All JFS partitions unreadable
- Previous by thread: Re: All JFS partitions unreadable
- Next by thread: Re: All JFS partitions unreadable
- Index(es):
Relevant Pages
|