On 2020-11-24 at 22:34, Kanito 73 wrote: > Hello > > Al the previous issues I published are now solved. Relative to the > RTL8821CE, I searched for a module rtl8821ce.ko but the generated > module was just 8821ce.ko so when I loaded the only RTL* > (rtl8821ae.ko) the right 8821ce.ko was already loaded and I thought > it was the rtl8821ae activating my wifi. [SOLVED] > > Now I have another BIG problem. I installed both Windows10 (version > OCTOBER 2020) and Debian 10.0.6 in dual boot and left a large NTFS > partition for data on the primary disk (HDD) and the whole secondary > disk (SDD) also as a unique NTFS partition. > > Well, I installed Windows, then Installed Linux and tested the NTFS > partitions from Linux (Debian) mounting and copying some files > successfully. After rebooting with Windows those partitions were not > accessible from Linux anymore. If they are mounted at boot time via > /etc/fstab it silently mounts them as "ro" (read only) although from > time to time they are mounted ocasionally as "rw" but as soon as I > try to write or copy there they are turned to "ro". If I mount > manually with the mount command, they are also mounted as "ro" > showing a message indicating that the NTFS partition was unmounted > uncleanly (and to fix with Windows) or that it is locked by windows > to perform a check or installation of something or an update BUT THEY > ARE CLEAN EMPTY PARTITIONS. > > What can I do? At this moment I am formating the 700Gb HDD partition > and just formated the 128Gb SDD from Windows with the full format > (not quick format) to see if there is a physical error on the disks. > The SDD was fully formated with no errors. The HDD partition > currently at 80% has not showed errors... So I think that Windows 10 > locks the partitions or something weird is going on. Modern Windows versions have a quirk that, in a default configuration, "Shut Down" doesn't actually shut all the way down; it effectively performs a type of "suspend". The reasons are a little complicated to describe, but boil down to making it possible for the next boot-up to happen faster. One effect of the way this is implemented is that at least the primary Windows drive (usually C:) doesn't get cleanly unmounted before the shutdown. In order to avoid risk of corrupting it, the Linux NTFS tools will refuse to mount such a partition read-write. It's possible (I don't think I've ever tested) that this will happen for other partitions, as well. One way to test whether this is what is happening would be to use "Reboot", rather than "Shut Down", to get out of Windows. A "Reboot" doesn't do that suspend-analog, it actually does shut things all the way down before rebooting. If you then boot to another OS (or even power off via the power button, once you've reached the POST screen) before going back into Windows, then if this is what is happening, you'll find that the partition in question was cleanly unmounted and the Linux tools can mount it read-write. There's also a way to disable this behavior, but I don't remember what it was; also, while I think I tried to implement it on computers at my workplace at one point, I don't remember having ever actually gotten it to work as advertised. If you want to try going that way, good luck. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw
Attachment:
signature.asc
Description: OpenPGP digital signature