Re: All JFS partitions unreadable

Dave Parsons wrote:
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
.

Relevant Pages

  • Re: All JFS partitions unreadable
    ... partitions on 2 disks and 3 HPFS partitions to find that ... for all the JFS partitions and the FAT one. ... If I boot to the command line from the boot blob, ... I took the non-system disk out and put it into ...
    (comp.os.os2.bugs)
  • Re: Dual Boot Problem
    ... I have an IBM T20 Laptop set up as dual boot with the HD divided into several partitions. ... All was working fine until I thought to change a drive letter under Win2000 to bring the FAT partitions in line with the OS/2 ... However for some reason reinstalling "boot manager" temporarily resolves it until windows runs again. ... you can use DFSee to touch the LVM information and see if that makes it right. ...
    (comp.os.os2.misc)
  • Re: Dual Boot Problem
    ... letter under Win2000 to bring the FAT partitions in line with the OS/2 ... I can get it to work again by removing "Boot Manager" and Reinstalling ... DFSee has a fix for this. ...
    (comp.os.os2.misc)
  • Re: All JFS partitions unreadable
    ... partitions on 2 disks and 3 HPFS partitions to find that ... I spent many hours with DFSee yesterday and all that I could ... If I boot to the command line from the boot blob, ... I took the non-system disk out and put it into ...
    (comp.os.os2.bugs)
  • Re: All JFS partitions unreadable
    ... partitions on 2 disks and 3 HPFS partitions to find that ... I spent many hours with DFSee yesterday and all that I could ... If I boot to the command line from the boot blob, ... I took the non-system disk out and put it into ...
    (comp.os.os2.bugs)