I've got a 2TB Toshiba drive (formatted as NTFS) that has become very slow and I was wondering if anyone here as any ideas what the problem could be and how I could fix it. All the data I'd need off the drive is backed up, but I would at least like a drive to put it back on to!

In short, it became slow after I had to force power-off the system it was connected to (Pop OS installed on another external drive which I unplugged by mistake) and I haven't bothered to try to fix it in the six months since.

I've tested it on Pop and it takes about 10-20 minutes to mount, and 2 minutes to unmount and safely remove. The data itself seems fine but performance is slow, accessing a 20MB image takes several seconds and selecting the drive in GNOME Disks caused it to freeze.

The drive sounded louder than normal, especially after plugging in.

On Windows, the drive was recognised and browsable immediately, but browsing through folders was very slow - opening some folders causes Windows Explorer to freeze for a while. Some of my double-clicks were mis-recognised as click-to-rename, which took several seconds to activate and during which time Task Manager reported the average response time between 5000 and 11000 ms.

Attempting to load an audio file resulted in lots of buffering. Task Manager reports an active time of 100% (even when not loading files or folders) and the activity never exceeded 100 KB/s (and doesn't sustain it for more than a second). Ejecting the drive takes forever - after ejecting it using the tray icon, the tray icon is not removed (even though there are no other drives connected or listed) and the active time is still 100% with the indicator LED blinking non-stop. The system did not enter sleep right away after me asking it to either.

All of that to say, does anyone know what the issue could be, or how I could find and fix it? Thanks!

Edit: fixed and normal functionality restored (at least so I can check the drive a bit easier) using Scan & Repair in Windows (see my comment).

Hi Tildes. Hopefully this thread will be both a good discussion and helpful to some of you, and hopefully me.

As I'm guessing most of you know, data backups are quite important and it is best to have at least one copy locally and another copy somewhere else. At the moment, I store photos on an external hard drive and Google Drive, photos from my phone on Google Photos with copies of important original quality files saved locally, and everything else on drives in my PC and a network drive on my Raspberry Pi. It's far from ideal, I've only got one copy of some files and three or four of some others so I've been looking for something better to keep everything organised, safe and in one place.

I've tried the free trial of Backblaze, which seemed the obvious choice, but it had a few problems. I couldn't backup my Pi's network share, and in general it's a bit clunky and difficult to use. It is marketed as an easy solution to backing up data, but in doing this it just makes everything more difficult, at least for me - I know what I want backed up, and I would prefer to select it manually, but by opting in everything for backup by default you have to spend ages excluding the folders you don't want saved, one-by-one, in a UI that is difficult to use and often unclear. Sometimes the exclusions list just doesn't work - the Program Files folders are meant to be excluded by default and they were listed under exclusions but were backing up anyway. For me it found over 200,000 files, and because they were all so small it barely managed to backup 100MB in three hours. (Not that I know where the files come from because they aren't listed in the Windows app in any vaguely comprehensible way.)

So I need to find something else, and I was hoping someone here would have some recommendations. Personally I need it to:

• Be affordable and easy to setup and use
• Backup external and network drives to the cloud (physically keeping another drive somewhere else isn't an option for me)
• Be trustworthy and have strong commitments to security and privacy
• Work well for my use case: preferably automatic from Windows

Looking forward to any comments or recommendations. Thanks!

I have a large VirtualBox VM on an external HDD. The HDD fails the S.M.A.R.T. test. The VM still works fine, but any regular attempt to copy the VM files over to a healthy drive fails ... there is clearly already something corrupt in the VM's virtual HDD, although it is not (apparently? yet?) affecting the functionality of the actual VM.

Any suggestions on how to save the VM? Linux Mint Guest OS, Pop_OS (Ubuntu) Host. The VM is nearly 800 GB. Both regular copy and rsync fail.

Thanks,
Eric

PS: (and perhaps I should have led with this, but...) is it okay to ask these kinds of specific, technical, "help me with my tech-stuff" questions here on Tildes?

Update to the update ... moved update info into a comment ... will keep my progress updated in that primary comment.

Danke, y gracias to all

Introduction

I want to give an introduction on several physics topics at a level understandable to laypeople (high school level physics background). Making physics accessible to laypeople is a much discussed topic at universities. It can be very hard to translate the professional terms into a language understandable by people outside the field. So I will take this opportunity to challenge myself to (hopefully) create an understandable introduction to interesting topics in modern physics. To this end, I will take liberties in explaining things, and not always go for full scientific accuracy, while hopefully still getting the core concepts across. If a more in-depth explanation is wanted, please ask in the comments and I will do my best to answer.

Previous topics

Bookmarkable meta post with links to all previous topics

Today's topic

Today's topic is spintronics storage devices for computers. I will try to explain how we can use an electron's spin to read and write data and why this is more efficient than current technologies.

What do we need to have a storage device?

In order to be able to save a bit (a 0 or a 1 in computer science speak), we need to be able to represent both the 0 and the 1 in some physical way. We could for example flip a light switch and say light on is 1, light off is 0. We will also need to be able to read the information we stored, in this case we can simply look at the lamp to see if we're storing a 0 or a 1. We would also like for this information to be stored even when power is cut, so that next time we power the hardware back on, we will still be able to read the data. Lastly, we want to be able to change between 0 and 1 freely; no one wants to go back to the CD days for storage.

Now for some basic concepts.

What is spin?

Spin arises from quantum mechanics. However, for the purpose of explaining spin storage devices we can think of an electron's spin as a bar magnet. Each electron can be thought of as a freely rotating bar magnet that will align itself with the fields from nearby magnets. Think of it as a compass (the electron) aligning itself to a fridge magnet when it's held near the compass.

Why are some metals magnetic?

Why can we make permanent magnets out of iron, but not copper? In all metals, we have spins that are free to rotate. This means that we can turn a metal into a magnet by holding it near another magnet, it will "copy" the other magnet's magnetisation - its spins will rotate in the direction of the field. But as soon as we remove the magnet, our metal will stop being magnetic. This is because the spins are freely rotating, the spins will align to the magnet's magnetisation when they feel it, but nothing is holding them in place as soon as it's removed. We call this property paramagnetism.

However, iron (and some other metals) will retain a nearby magnet's magnetisation even when the magnet is removed. This is because in these materials, called ferromagnets, it costs energy for the spins to rotate away from the material's magnetisation. They are pinned into place.

What happens if we expose half of our ferromagnet to a magnetisation pointing in one way (let's call it up), and the other half to a magnet whose magnetisation is pointing the other way (which we call down)? The ferromagnet would copy both magnetisation directions and create a boundary region - a so-called domain wall - in the centre. The spins in this domain wall will slowly rotate over the thickness of the wall so that at one end they're pointing up and at the other end they're pointing down.

How can we use spin to store data?

What if, instead of a light bulb, we used a bar magnet as our storage medium. We could magnetise our bar magnet in one direction to store a 1 and magnetise it in the other direction to store a 0. To read what we have stored, we simply check the bar magnet's magnetisation.

Let's work out this idea. We want to be able to efficiently change the magnetisation of a bar magnet and we want to be able to read the bar magnet's magnetisation. We will use a ferromagnet because it will retain our data indefinitely (its magnetisation will not change unless we force it to). We know it costs energy to flip the spins inside a ferromagnet, so we will want to use a very tiny ferromagnet - it will have less spins which means it will cost us less energy to change the magnetisation (i.e. flip the spins).

Magnetoresistance

A-ha, now we're getting into the fancy-titled paragraphs. What do you, dear reader, think would happen when we send a current (e.g. a bunch of electrons) through a magnet? What would happen to the current's electrons (also called itinerant electrons, to distinguish them from the non-moving electrons of the metal)? At the boundary of the magnet, where the current enters, only the electrons who (through random chance) have a spin that's aligned to the magnet's magnetisation will pass through. We call this effect magnetoresistance, as in effect part of our current will feel a resistance - they cannot pass through to the magnet. So to rephrase, the current inside the magnet will be "magnetised" - all of the spins of the itinerant electrons are pointing the same way.

Current induced domain wall motion

So now we know what happens to a current that's inside a magnet. What happens when this current meets a domain wall - the region where the magnetisation changes direction? The itinerant electrons' spins will start rotating along with the magnetisation, but the static electrons of the ferromagnet will also start rotating in the opposite way due to the magnetisation they feel from the current (more experienced readers will recognise this as conservation of angular momentum). So the spins inside the current will slowly rotate until they are pointing the opposite direction and can continue passage from the up-magnetised part of the ferromagnet into the down-magnetised part. But the spins that belong to the ferromagnet itself will be rotating in the opposite manner, slowly rotating from down to up as the current passes through. This means the boundary region between up and down magnetisation, the domain wall, will move along with the current.

So in short, by sending a current through a magnet that's magnetised in opposite directions at each end, we can force our preferred magnetisation to expand in the current's direction. By reversing the direction of the current we can then magnetise the other way again.

So we can say magnetising up (pushing current through (let's say) from left to right) can be our 1 and magnetising down (pushing current through from right to left) can be our 0. This would allow us to store data permanently as even when we remove the current our magnet will remember its magnetisation. If we make a really tiny ferromagnet we will only need a really tiny current to flip it's magnetisation too. So we can scale this process down to get to really good efficiencies. In the lab these types of devices are down to nanometre scale and require extremely little current to be operated.

Reading the data

OK, so now we know how to write data. But how do we read it? The key effect here will be magnetoresistance, as explained earlier in the post.

Let's look at this picture. The red dotted line shows our write currents, the big bar is our ferromagnet. The arrows pointing up and down at the sides are our magnetisation direction, the double-pointed arrow in the centre shows the region where we flip the magnetisation by sending through a current.

Now we jam a third, permanently magnetised, bit of metal (let's call it the read terminal) on top of the centre of our bar. We send a current from this read connector to one of the ends of the ferromagnet. If the ferromagnet's magnetisation is aligned to that of the read terminal we will experience a low (magneto)resistance, but if the ferromagnet is magnetised in the opposite direction we will experience a high resistance. By measuring the difference in resistance we can determine if we have a 0 or a 1 stored. We just need to be careful not to send too big of a current, else that would influence our ferromagnet's magnetisation. But small currents means better efficiency, so this is not a problem at all.

Conclusion

This concludes the post, we have seen how to use spins and magnets to both write and read data and we understand why this is efficient.

Feedback

As usual, please let me know where I missed the mark. Also let me know if things are not clear to you, I will try to explain further in the comments!

I'm currently researching the cheapest off site backup system and it looks like leaving a hdd at a friends house is the best option. The only thing I am stuck on is how to access it remotely. I need a system on a chip that I can plug in to the hdd and Ethernet and that provides ssh access. My first thought was a raspberry pi with a sata to usb cable but since I will only be doing weekly backups it makes no sense to keep the drive spinning 24/7. I need some way to turn off the drive and then back on over the internet. From what I understand there are linux programs that can do it but only directly over sata because the command doesn't work on usb sata controllers.

What I need is a cheap linux SoC that has sata and ethernet. Does anyone have any ideas?

I've been trying to find a small capacity (64GB or less) flash drive with decent read and write speeds, but haven't been able to find anything. I'm looking for something in the 200-300 MB/s read/write range, but I can't seem to find anything that reliably breaks the 100 MB/s mark even in larger capacities. The SanDisk Extreme Pro 128GB seems to have adequate performance, but at $65 is a bit out of my price range since I'd like to purchase a handful of drives.

Does anyone know of any other smaller flash drives with SSD-level performance?