This answer is so very correct, but when I first read it I didn't know what I was talking about. It took over a year to realize that a drive CANNOT "change" from 512e to 4kn just by some configuration setting; this is baked into the drive. Guys please give this answer the recognition it deserves. This is the clearest explanation I've seen yet of the 512n/512e/4kn thing. This will become popular once 4kn is common in the consumer space ;p — allquixotic12 secs ago
Your disks are either 512e (512 sectors on SAS/SATA interface) or 4k native (4k sectors on SAS/SATA interface), and unfortunately there is no way to change that via software or jumpers etc. You select the transfer mode when you buy the disks. Buy 4k native disk if you have adapter that supports 4...
I thought I remember coming across a drive once where you could switch between 512e and 4kn in firmware, although it was a niche enterprise drive and doing so would lose all your data.
I have an SSD that can be configured to report its physical sector size to an OS in two different ways:
Option 1: Logical = 512 Bytes, Physical = 512 Bytes
Option 2: Logical = 512 Bytes, Physical = 4096 Bytes (4K)
What benefit does an OS gain by being aware of the 4K physical sector size, cons...
@qasdfdsaq Unfortunately, I'm not quite up to that level of wealth, yet. I'm somewhere in the middle between the "I can't afford even a 1 TB drive" and the "I have a storage cabinet with 64GB of usable space" crowds.
Hence the 4 x 4 TB array with maxCache and a pretty beastly RAID card.
The metadata overhead must be why most games ship their assets in a few package files of some various file format (some are just disguised ZIP, others are truly custom)
@DragonLord More files, period, can create many entries. But a small file does not use up any more entry space than a large file, with the exception of a heavily fragmented file.
This is the latest stage in a long running chain of events that has seen me cross the seven circles of HDD hell only to arrive at these depths of virtual inferno.
My Hard Drive is a 750GB Seagate Barracuda. At the point it is now, Hard drive is still recognized in BIOS and is able to be recogniz...
If you wanted to pay a lot of money you could probably get someone to try a board swap with another drive from the same batch (if one can be found). But that's expensive, risky and very involved.
@Bob, it's still recognized in the bios, it recognizes it in disk management, it even can tell the firmware of it as you can see from the pics... if the problem is software or firmware caused, there's got to be a way to recover from it.
I'm at that point where I understand more about modern storage and I/O than 98% of the population, but I'm still in a completely different (lower, more ignorant) league than the remaining 2% :P
As I said -- somehow your drive is in a state where the system can detect that there's something connected, but can't get any really meaningful info from it.
@qasdfdsaq do you remember the days when significant bits of hardware sold to consumers would be breakable due to certain user inputs? like, the hardware would actually break, right then and there if you executed certain code?
I seem to remember it being possible to break certain GPUs with certain user input. And of course many types of hardware that have field-flashable firmware can be bricked (even today, with smartphones) due to a bad flash.
bricked is not quite the same as actually damaging electro/mechanical parts though
I can still break my GPU, just set the voltage and clockspeed sliders to the far end of the scale, and tell my environmental controller to cut power to the water cooling pump.
Then there were higher "levels" of breakage that have since been closed off. For instance, on XP, the graphics drivers were GIGO, so if you passed an invalid command to your GPU, guess what -- GPU reset, kernel panic/BSOD, reboot.
Now they have a command stream verifier that avoids sending garbage to the GPU, and if the GPU does crash, they pull the power on the PCIe slot for a split-second and let it reinit :P
@allquixotic Funny how we just accept that the GPU will crash, but the CPU must never, under any circumstances, do anything odd or the whole system will go down.
and now I'm in a walled garden and let me tell you, the honeysuckle is in full bloom and it smells wonderful
@Bob heh, yeah, it's like how 32-bit "dedicated servers" for games hosted on Windows have to have some kind of a crash/network timeout detection and auto restart feature, but nginx won't crash on you unless you really torture it
anyway, same cans, same locations, iPhone screen off, no stuttering - MY problem was solved by going to Apple; others who don't have the problem are either lucky or just not seeing the same problem as I saw across 4 phones and 4 headphones for whatever reason
I'm pretty sure people were reporting issues with LG, but I never tested an LG phone personally
just Sammy and Moto
or could be the 808, or QCOM fixed a bug in the BT... I have no idea
@allquixotic If you keep up to date on some of the KVM/Xen virtualization hypervisor development mailing lists you'll realise some of those issues actually still exist today
As in they keep finding security holes where a virtual machine can set a certain bit of a certain register to some value and bam, they have DMA to a PCI device which in turn has DMA to the host memory
One day I'll compare the file mode permissions to another Xenserver I'm running and patch them up, until then, yeah. I don't want to restart and patch.