Cannot change volume name by command VOL - System file exists
mr-GreyWolf opened this issue · 16 comments
Nextor kernel version 2.1.0 beta 2
NEXTOR.SYS version 2.10
COMMAND2.COM version 2.44
A:\> vol name_of_volume
*** System file exists
Discussion here.
It has to do with Windows creating System Volume Information folder I think. This then gets a short name FAT entry and that is recognized as the “system file exists” and the volume showing as B (on my setup). I circumvented it by hsving Nextor on a floppy disk and after _fdisk and reboot I copy Nextor.sys and command2.com from floppy to SD, boot again and issue vol command (before modern OS touches the SD card)
It has to do with Windows creating System Volume Information folder I think.
I do not use Windows.
I copy additional files under Debian GNU/Linux.
Hello, I'm unable to reproduce this. Could you please send me an image of the device giving you the error? If not, maybe a dump of the root directory area of the device could be useful.
Hello, I'm unable to reproduce this. Could you please send me an image of the device giving you the error? If not, maybe a dump of the root directory area of the device could be useful.
Hello!
How to create a dump of the root directory ?
How to create a dump of the root directory ?
Since you are using Linux, perhaps you could use the dd tool to dump the first few KBs of the device? (assuming that you are using the first/only partition of the device)
@Konamiman, here's the link to dump of start first partition.
Hello, thanks for the dump but it's not big enough. According to the boot sector parameters it seems that the size of the FAT is 64K, and since there are two FAT copies and the root directory size is 16K, I would need the first 145K of the partition (let's make it 150K to be safe).
Hello, @Konamiman this 256K and full partition image.
Ok, got it now. This will help me troubleshoot the issue, thank you!
I can confirm that the issue is caused by the presence of long name entries in the root directory (those entries have an attributes byte of 0Fh, which is volume label + system + hidden + read-only, so Nextor gets heavily confused with those). I'll include a fix in the next version of the Nextor kernel.
Fixed in v2.1.0
I'm using 2.1.0 and I also ran into this issue... What can I do?
@MBilderbeek are you using the latest 2.1.0 available (not an alpha or a beta)?
Yes, I downloaded the 2.1.0 release version when I set up my CF card last week. Also flashed the accompanying IDE BIOS on my Carnivore 2.
It may be a similar but slightly different situation triggering the same issue. It’s wise to give the output of ver to make sure you are fully updated and if so I guess a dump of the partition will help in the investigation.
Well, what can I tell.... I just tried it again and now it works...!? Nextor kernel version is (indeed) 2.1.0. Never mind, I guess...