WebSite Information > Article Discussions

[Arca Noae] Checked your disk lately?

(1/6) > >>

Martin Iturbide:
Reference: [Arca Noae] Checked your disk lately?

It is a great milestone for DFSee to support GPT, but I'm still thinking how useful will be that for OS2-eCS-BlueLion installation.

I'm guessing that it should be useful for someone to boot from USB/CD and with DFSee try to repartition and already partitioned HDD (by Windows or Linux) and resize partition to fit OS2-eCS-BlueLion. (and of course use all the great features of DFSee on a GPT drive) But once you boot the Installer will it recognize the installation partition on GPT or after installing the OS, will it boot?

I was told that what we are missing is to create some GPT driver like a FLT (Filter Device Driver). Will a  GPT.FLT driver will work without having UEFI support?


--- Quote ---We at Arca Noae would like to thank ...., and OS/2 VOICE for its ongoing community support.
--- End quote ---

I really do not know the formal relationship between Arca Noae and OS2VOICE, I'm getting jealous about it  :P

I personally want to thank Steve Wendt from OS/2 Warp New and Rumors, the people from Italy behind eCSoft/2 and the people that uploads their software to hobbes and netlabs for their great "ongoing community support", and super special thanks to the developers that shares their software and don't hide their source code to the public.

Regards

Michael Holzapfel:

--- Quote from: Martin Iturbide on December 06, 2015, 06:14:53 am ---I personally want to thank Steve Wendt from OS/2 Warp New and Rumors, the people from Italy behind eCSoft/2 and the people that uploads their software to hobbes and netlabs for their great "ongoing community support", and super special thanks to the developers that shares their software and don't hide their source code to the public.

--- End quote ---
Fully agree on this statement. I really get concerned about ArcaNoae's new attitude. Instead of working on their own roadmap (https://www.arcanoae.com/roadmap/), they announce a new version OS/2. My drivers and software package license expires soon, nearly nothing from roadmap was realized (except of pre-beta network drivers).
Important software repositories went away from netlabs (like USB-drivers, we no have two different repos, AHCI and ACPI). So if ArcaNoae suddenly decides to drop any OS/2 Activity, we have nothing in our hands.
This reminds me very much of Mensys, many announcements, no substantial progress, no transparency.
Bitwise is doing a much better job here, you can follow each development step easily (see Mozilla @github or vbox @ netlabs).
I really doubt if I still want to continue to invest money in the products of ArcaNoae.

Michael


Greggory Shaw:

--- Quote from: Michael Holzapfel on December 06, 2015, 01:11:37 pm ---...
I really doubt if I still want to continue to invest money in the products of ArcaNoae.

Michael

--- End quote ---

How about you actually let them have a chance first of all - and a deal with Big Blue is no small deal.

And you're right they're about the last devoplers, so again how about a little support first.

Greggory

Pete:
Hi All

Unlike Michael I am reasonably happy with my recent Arca Noae subscription - at the moment.

I have downloaded and installed updates to ACPI, AHCI, Multimac, USB, Uniaud and JFS from the driver pack and am happy with most of these updates.

However, I have bumped into a couple of JFS problems that have made me revert to an earlier JFS release.

The Problems

1] The JFS /AUTOCHECK:+* switch is no longer honoured. This means that it is impossible to *force* chkdsk on drives that are Dirty but marked as Clean. This had been reported by someone else and the result is *unsatisfactory* with the bug marked as Resolved:-

Resolution:  won't fix
Comment:  Regardless of whether you consider it a defect fix, an enhancement, or just a change in operation, this is how it works now.

I have opened a new bug about this problem and hope that Arca Noae rethink and resolve this problem. It is silly to need to boot from another device, ie CD/DVD, in order to chkdsk a Dirty but marked Clean drive.


2] Since installing this JFS release  my system often "loses" a drive volume at boot. I have JFS formatted volumes G: through L: with H: and L: being bootable. About 1 in 3 boots I notice that G: is not mentioned at all during the JFS chkdsk display.
Once booted I can get G: to display in the Drives folder by running LVM and then exiting using Save and Exit - with no changes made and - Voila! drive G: appears in the Drives folder.

This is clearly undesirable behaviour by the JFS driver and needs fixing.

How do I know this is related to JFS 1.09.06?

Simple: It does not happen with any earlier release of JFS.


I have reverted to the jfs installed by eCS2.2beta2 - JFS 1.09.05 - and suggest that anyone else having any form of hard drive problems with JFS 1.09.06 - whether local or usb attached - reverts to any earlier build to see if the problem(s) go away.


Plugging DFSee as a disk fixer when you are supplying what in my view is a dodgy filesystem driver is a bit rich   ;-)

Depending on how Arca Noae resolve these problems will affect whether I stay happy with Arca Noae.

Regards

Pete

Andreas Schnellbacher:

--- Quote from: Pete on December 06, 2015, 05:44:44 pm ---1] The JFS /AUTOCHECK:+* switch is no longer honoured. This means that it is impossible to *force* chkdsk on drives that are Dirty but marked as Clean.

--- End quote ---
My technical opinion: Note that with '+*' you can't force anymore any clean-marked volume being checked at all, regardless if it's dirty or not.

When a dirty boot volume is marked clean, it's time to boot from another volume and perform the chkdsk from there. If that would happen for other volumes, you have now also to boot to another volume for that. Is that really that important? How many times happened that for you?


--- Quote from: Pete on December 06, 2015, 05:44:44 pm ---2] Since installing this JFS release  my system often "loses" a drive volume at boot. I have JFS formatted volumes G: through L: with H: and L: being bootable. About 1 in 3 boots I notice that G: is not mentioned at all during the JFS chkdsk display.
Once booted I can get G: to display in the Drives folder by running LVM and then exiting using Save and Exit - with no changes made and - Voila! drive G: appears in the Drives folder.

--- End quote ---
I would give David at least a few weeks time to investigate this and to react to your recently posted bug.

I agree with you that this needs fixing and if it's somehow reproducible, chances are not bad to fix it.

Navigation

[0] Message Index

[#] Next page

Go to full version