Multi Commander > Support and Feedback
Unknown error: 27
Mathias (Author):
--- Quote from: pivikov on August 28, 2019, 14:43:04 ---
--- Quote from: Mathias (Author) on August 28, 2019, 08:11:55 ---Strange. never seen anything like that. Like somethings is interrupting the writes.
Have you tried to turn off "Automatically detect read/write stratergy" (Core settings > FileSystem tab > under "Copy and Move" section
(but not sure that will make a difference if somethings is interrupting the write operations)
Edit
------
Hmm Wait internal error 27.. Internal error is error code from Windows and error code 27 is ERROR_SECTOR_NOT_FOUND "The drive cannot find the sector requested."
--- End quote ---
I turn off "Automatically detect read/write stratergy"
Since the problem is only with this disk, we can assume that it is still faulty. Just why MC reacts to this and the rest of the software is not.
I do not understand what is happening either.
--- End quote ---
I don't know. All I can say is that this error is sent from inside Windows to MC when it tries to write data.
It can also be from drives that does not support optimized way to write data. But if you still get the error when that option if OFF.. then I do not think so..
You check the Windows event log (Event viewer). There might be more information in the Windows Log system about it
pivikov:
--- Quote from: Mathias (Author) on August 28, 2019, 21:06:43 ---
--- Quote from: pivikov on August 28, 2019, 14:43:04 ---
--- Quote from: Mathias (Author) on August 28, 2019, 08:11:55 ---Strange. never seen anything like that. Like somethings is interrupting the writes.
Have you tried to turn off "Automatically detect read/write stratergy" (Core settings > FileSystem tab > under "Copy and Move" section
(but not sure that will make a difference if somethings is interrupting the write operations)
Edit
------
Hmm Wait internal error 27.. Internal error is error code from Windows and error code 27 is ERROR_SECTOR_NOT_FOUND "The drive cannot find the sector requested."
--- End quote ---
I turn off "Automatically detect read/write stratergy"
Since the problem is only with this disk, we can assume that it is still faulty. Just why MC reacts to this and the rest of the software is not.
I do not understand what is happening either.
--- End quote ---
I don't know. All I can say is that this error is sent from inside Windows to MC when it tries to write data.
It can also be from drives that does not support optimized way to write data. But if you still get the error when that option if OFF.. then I do not think so..
You check the Windows event log (Event viewer). There might be more information in the Windows Log system about it
--- End quote ---
Yes, there are two entries in the system log each time the zm-ve350 device is connected. "An error was detected on the device \Device\Harddisk2\DR27 during a paging operation.". But only when connected, similar recordings also occur when connecting flash drives, so I usually do not pay attention to them, since the drives have been working for more than one year with similar messages in the system log.
AlanJB:
Assuming your event log error was Event ID 51, there are several possibilities:
* Your device driver is outdated or corrupt
* The drive is failing
* The drive was unplugged without being "safely" removed
* The drive is very low on free spaceSome things to look into...
Edii: Also run chkdsk
Mathias (Author):
--- Quote from: pivikov on August 29, 2019, 11:24:29 ---
--- Quote from: Mathias (Author) on August 28, 2019, 21:06:43 ---
--- Quote from: pivikov on August 28, 2019, 14:43:04 ---
--- Quote from: Mathias (Author) on August 28, 2019, 08:11:55 ---Strange. never seen anything like that. Like somethings is interrupting the writes.
Have you tried to turn off "Automatically detect read/write stratergy" (Core settings > FileSystem tab > under "Copy and Move" section
(but not sure that will make a difference if somethings is interrupting the write operations)
Edit
------
Hmm Wait internal error 27.. Internal error is error code from Windows and error code 27 is ERROR_SECTOR_NOT_FOUND "The drive cannot find the sector requested."
--- End quote ---
I turn off "Automatically detect read/write stratergy"
Since the problem is only with this disk, we can assume that it is still faulty. Just why MC reacts to this and the rest of the software is not.
I do not understand what is happening either.
--- End quote ---
I don't know. All I can say is that this error is sent from inside Windows to MC when it tries to write data.
It can also be from drives that does not support optimized way to write data. But if you still get the error when that option if OFF.. then I do not think so..
You check the Windows event log (Event viewer). There might be more information in the Windows Log system about it
--- End quote ---
Yes, there are two entries in the system log each time the zm-ve350 device is connected. "An error was detected on the device \Device\Harddisk2\DR27 during a paging operation.". But only when connected, similar recordings also occur when connecting flash drives, so I usually do not pay attention to them, since the drives have been working for more than one year with similar messages in the system log.
--- End quote ---
I don't know. very strange error you get.
paging operation often have to do with the memory manger in Windows like swap things on/out of the page-file..
I have no idea on why that is happening to you setup. If it is hw related it can be so many things. Does not need to be the drives.. it can be anything in the chain from the drive to sata controller, to usb controller and drivers. I never seen an error like that.
pivikov:
--- Quote from: Mathias (Author) on August 29, 2019, 14:05:16 ---I never seen an error like that.
--- End quote ---
Have you encountered such a mistake? This is a different operating system and other drives.
At work, I often need to transfer a lot of files, while MC fails in the most seemingly standard operations.
I saved the output to a file (copy to file ctrl+l), but typing this message I found that the file Unknown.txt is empty :) But there were no mistakes.
ADD
Before the error appeared, I actively worked with several disks, added folders to the queue for moving, counted the space occupied by folders (you can see in the screenshot). There were many errors related to the lack of access rights (these are individual NTFS rights settings) These errors MC were processed correctly.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version