UFS Fsck help

[Jwl2FL]

So here is the run down.

I have an embedded install of 9.3.0.2 on an old intel pentium 4 system, now using an amd phenom. With a total of 5 HDDs, 3 in external enclosures and 2 in the machine itself. All drives were formatted in UFS and had been working great for about 7 months.

The 'old' mobo in my NAS died due to cap swelling, well after replacing the mobo with another all HDDs but my boot drive ended up being marked dirty and put into read only.

I have tried and tried to get these drives marked clean to be able to recover the data as I have a new system in the works using an off lease xeon server that I picked up dirt cheap.

I am currently focusing on one drive after having no luck on the other three, the drive that I am focusing on is the drive that is installed in the machine and not one of the external drives. This internal drive is also the only drive that will mount in the read only condition allowing me to see that the data is still intact on the drive.

Here is the print out of an fsck attempt from the web gui, unmount box unchecked in the, Disks | mount point | FSCK area.

** /dev/ufsid/55a79c7aeb91ad7d (NO WRITE)
SETTING DIRTY FLAG IN READ_ONLY MODE

UNEXPECTED SOFT UPDATE INCONSISTENCY
** Last Mounted on /mnt/JR
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
32087 files, 207829073 used, 28692766 free (1286 frags, 3586435 blocks, 0.0% fragmentation)
Successful

Here is a print out of the same page with the unmount box checked.


** /dev/ufsid/55a79c7aeb91ad7d
** Last Mounted on /mnt/JR
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
32087 files, 207829073 used, 28692766 free (1286 frags, 3586435 blocks, 0.0% fragmentation)

***** FILE SYSTEM IS CLEAN *****

***** FILE SYSTEM WAS MODIFIED *****
Successful

With this I had thought that the problem was resolved, as this had been the output that marked a remedy in the past. but alas the drive can still not be accessed from my windows machine.

Here is a print out of the advanced web gui command that I also ran,

$ fsck_ufs -y /dev/ada1p1
** /dev/ada1p1 (NO WRITE)

USE JOURNAL? no

** Skipping journal, falling through to full fsck

SETTING DIRTY FLAG IN READ_ONLY MODE

UNEXPECTED SOFT UPDATE INCONSISTENCY
** Last Mounted on /mnt/JR
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
32087 files, 207829073 used, 28692766 free (1286 frags, 3586435 blocks, 0.0% fragmentation)

and.

$ fsck_ufs -y /dev/ada1
** /dev/ada1 (NO WRITE)
ioctl (GCINFO): Inappropriate ioctl for device

and again with the drive unmounted,

$ fsck_ufs -y /dev/ada1p1
** /dev/ada1p1

USE JOURNAL? yes

** SU+J Recovering /dev/ada1p1
Journal timestamp does not match fs mount time
** Skipping journal, falling through to full fsck

** Last Mounted on /mnt/jr
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
32087 files, 207829073 used, 28692766 free (1286 frags, 3586435 blocks, 0.0% fragmentation)

***** FILE SYSTEM IS CLEAN *****

***** FILE SYSTEM WAS MODIFIED *****

So as you can see the drive is being marked clean when unmounted but once it is mounted it is getting marked dirty again and defaulting back to read only. I would like to just get the drive to the point that I can get the data off it and onto the new to me server that is replacing the hodge podge NAS server that I have now. any help would be greatly appreciated. I am sorry for the wall of text but I am hoping that there is someone here that can help me with this issue and would like for them to have all the info that I can provide them.