OS/2, eCS & ArcaOS - Technical > Applications
duplicate block references have been detected in meta data
andreas:
cannot start any drive anymore.
It seems I have a corrupt partition table.
At least the Installation Volume Manager tells me so.
under chkdsk i get the message. "duplicate block references have been detected in meta data"
what can i do?
Dave Yeo:
Have you tried chkdsk /D x:
Try DFSee.
I've had success and failures trying fsck-jfs under Linux (Mint) and in one case mounted a bad partition read-only under Linux and copied everything (except one directory) to alternate media. Unluckily often the default mount of OS/2 JFS doesn't enable xttrs (Extended Attributes).
andreas:
i tried chkdsk C:/ F:1 what does /D x: do?
i'm just trying to create a linux live-stick, KI gave me advice to use gparted. stick is beeing built right now.
I have no experiance with linux at all. But i will try. I really need access to my system as quick as possible
edit:
before chkdsk worked, but now i get the message "SYS0015: The System cannot find the specified drive."
Dave Yeo:
/D for debug, sometimes it helps or at least a better error report.
If you have no experience with Linux, I don't know if you should go that route. You need to figure out what device(s) you have and use a terminal to do something like sudo fsck /dev/sda1 or use fsck.jfs if I remember correctly.
With Gparted, it might give you an idea of the problem but you can break your partitioning as far as OS/2 is concerned, really easy. Not all distributions have JFS support either
Have you looked at DFSee? There's an option to install to a minimal Linux USB stick or if you get your USB Linux stick booting, running DFsee from it.
Good luck and after consider back up plans. I have a USB hard drive, use rsync to back up my data and use zip to zip up my boot partition.
BTW, is it a hard drive or SSD that is giving you problems?
Dariusz Piatkowski:
andreas,
--- Quote from: andreas on January 28, 2025, 04:24:24 am ---i tried chkdsk C:/ F:1 what does /D x: do?
--- End quote ---
Courtesy of Lewis (AOS) and sTeven Levine (whom he credits for sharing his notes on this topic):
--- Code: ---Check FS content
Usage: chkdsk drive: [/A] [/B] [/C] [/D] [/F[:n]] [/O] [/P] [/V]
/A - Enable autocheck mode (undocumented)
/B - Perform LVM Bad Block List utility processing only
/C - Process ifdirty after logredo
/D - Enable debug mode (undocumented) all log messages written to stdout in english
/F[:n] Full check
0 => read only (default)
1 => prompt for permission for each repair
2 => preen (default if n omitted)
3 => Assume permission given for all repairs.
If exiting with clean file system, invoke LVM Bad Block List utility processing on the way out.
Note: :1 and :2 are converted to :3
/O - Omit logredo (undocumented)
/P - Enable pmchkdsk mode (undocumented)
/V - Verbose messaging (ignored)
Both / and - prefix supported
Options are case-insenitive Called as chkdsk drive: /F /A [/C] for autocheck
--- End code ---
Navigation
[0] Message Index
[#] Next page
Go to full version