Re: No space left on device ...
> Has this ever worked in the past? It is my understanding that the Linux NTFS driver is read-only.
> Mounting how exactly? And what is the contents of /proc/mounts? Maybe
> you mounted the partition read only?
Well, actually, yes. This is how I have been mounting the Windows
NTFS of my laptop and my employer's as well without any problems
whatsoever. I just open the file browser/viewer and click the drive to
mount it in order to unmount, eject it you right click on it. It
works.
>> $ cp "No space left on device" > No_space_left_on_device.txt
>> bash: No_space_left_on_device.txt: No space left on device
>That *shouldn't* work. I get:
my mistake I meant: echo "No space left on device" >
No_space_left_on_device.txt
> Does anybody read signatures any more?
Apparently, some of us do. ;-) My obfuscation of the path didn't
relate to the error.
> First thing to try is to boot back into Windows and see if there is a
message about the drive. If so, let Windows 'fix' it. I've had cases
where the drive was not cleanly unmounted and Linux has mounted it
read-only. Windows was able to repair it, whatever the problem was.
THis is the second thing I did. I booted into the BIOS and run an
exhaustive test/diagnostic on every physical part of it twice. It all
tested fine, including the hard drive.
Then something spooky happened. I couldn't care less about Windows,
but then "'the BIOS' 'told me'" it would fix my laptop and it effing
did without messing with any of my data!!! Then I could boot into
windows again ... once I checked everything was fine I went back to my
Debian live ways.
Every electronic thing I use has a mind of its own, that makes your
life so much more enjoyable! ;-)
> Did you disable the Fast Boot feature in Windows?
Yes, I did. I had to reset the BIOS to "factory settings" which also
changed the clock time which then I couldn't change with hwclock ...
but when I booted the laptop with a network access at the library. It
did reset the clock apparently using WIndows time servers.
That fix took me like four hours (dealing with the nonsense of the
installation ...), but at the end of th eday I was able to go back to
my do, do, do, ... mode.
Thank you,
lbrtchx
Reply to: