17

I am currently configuring a Thinkpad E540, having inserted a 256 GB M.2 SSD into the corresponding slot, in order to run Windows 8 from the SSD instead of using the preconfigured 16 GB SSD as a cache for the hard drive.

All was well at first, but now any attempt to install software will result in the error message

Windows API error 302: This volume is too fragmented to complete this operation.

Needless to say, on an SSD fragmentation shouldn't be an issue. I tried running the drive optimization tool of Windows 8 (which defragments HDDs, and sends TRIM commands to SSDs) but it helped only briefly (so briefly actually, that it might have been mere coincidence that there was any effect at all).

Any idea what might be causing this?

*edit* Some new insights that I have gained since:

  • Rebooting temporarily removed the issue. Running the optimizer tool is not required.
  • It reappears after some time.
  • Note that the drive has 140 GB of which only 60 GB have been used. Trim shouldn't be an issue yet!
  • On the other drive E:, also on the SSD, I have not seen the issue yet.
  • Moving data to the C: drive works fine under Linux.
  • Even echo test > test may fail on C: (in the home directory)
  • Even reading the event log may fail at that point.
kdb
  • 2,080
  • 1
  • 26
  • 43
  • 6
    Regarding "fragmentation shouldn't be an issue": it still *happens* on SSDs; it's just that fragmented files can be accessed as quickly as non-fragmented ones, so you don't get the performance degradation that you'd get from fragmentation on a hard drive. – Wyzard Dec 14 '14 at 23:07
  • 2
    Is it coming up for all software? – Canadian Luke Dec 14 '14 at 23:14
  • Actually file fragmentation is simply irrelevant consider the device will itself fragment a file. Which devoce are you trying to install too? – Ramhound Dec 15 '14 at 00:32
  • I am trying to install to the C: Drive which corresponds to the first 140GB of the SSD. Curiously right now the error doesn't occur, but previously it reappeared after trimming the device and rebooting. – kdb Dec 15 '14 at 12:54
  • The error just appeared again... So it really is kind of unpredictable right now. Also note that only 60 of 140 GB on this drive are currently used actually! – kdb Dec 15 '14 at 13:07
  • Also, now that the issue has reappeared, it applies even if I try to run `echo test > test` in an administrator commandline window (i.e. the drive is effectively read-only). It does not appear on the other drive E: on the same SSD. – kdb Dec 15 '14 at 13:16
  • Fragmentation isn’t irrelevant because filesystems only care about block addresses. If it says “too fragmented”, it is. @kdb Did you install Windows yourself, formatting the partition while doing it? Or is it perhaps the OEM installation? – Daniel B Dec 15 '14 at 13:42
  • It is an installation using Lenovo's Windows 8 recovery disk, albeit to the M.2 slot, which normally is used only for a cache SSD on this configuration. I have read reports of successfully installing Windows to this slot though. Also by now when I boot into Windows, the desktop appears but no interaction with any elements is possible (only hard-reset remains possible). – kdb Dec 15 '14 at 13:43
  • 2
    Restoring Windows 8 from an image created with `ntfsclone` has solved the issue, so I think it may have been a failed update. – kdb Dec 16 '14 at 11:12
  • 1
    I read that defragmenting SSD's is very bad for it. Therefore I advise against it. – RedDragonWebDesign Dec 16 '14 at 14:48
  • 1
    There is a [Hanselman blog post](http://www.hanselman.com/blog/therealandcompletestorydoeswindowsdefragmentyourssd.aspx) about fragmented SSDs, the conclusion is that defrag is also needed for SSD's – Cerveser Dec 17 '14 at 14:46
  • Fragmentation is ALWAYS an issue irregardless of disk type because if certain blocks are allocated in such a way that the the number of serial free blocks is less than what we want, we won't be able to allocate so many serial free blocks (since they simply don't exist). Granted, it's easily worked around by not requiring a serial number of free blocks and I'm having a hard time believing this issue would show up if there's 80/140 GB left. I'm not sure if Windows provides a way to request serial disk blocks. Usually the OS manages that kind of low level disk interaction and programs use files. – Kat Dec 18 '14 at 19:02
  • @Cerveser Good link, but it sounds like defrag is really needed for the Windows OS/FS more than for the physical drive itself. – Joe M Dec 19 '14 at 00:07
  • The issue was solved in a manner that doesn't really constitute a question; Should I just vote to close the question? – kdb Dec 29 '14 at 19:11
  • 1
    @kdb, Because answer found, You can (may be even must) make answer on own question and accept it. Then it closed automaticaly. – Mikhail Moskalev Dec 29 '14 at 19:27

1 Answers1

2

I restored Windows 8 from an image. Afterwards the issue didn't show up again. My best guess would be a botched update, or permission issues after copying AppData files from the old disk, with the fragmentation warning being a possibly misleading symptom of the underlying issue.

By suggestion I post this as an answer, though I'd still be interested to know if there are other ways to resolve such issues, or what could have caused it.

kdb
  • 2,080
  • 1
  • 26
  • 43
  • That seems possible. I was trying to install the Insider Preview update on Windows 10 when this happened. Not sure if this also has something to do with dualbooting with Linux though. – xji Jan 27 '18 at 13:42