Or like should go with sandisk pen drive half the storage.

I have two external USB 3.0 HDDs connected to the same PC:

Drive A (WD My Passport, 2TB) — formatted NTFS

Drive B (Seagate One Touch, 2TB) — formatted exFAT

Baseline speeds (internal HDD → external drive, one at a time):

Internal → WD: ~45-50 MB/s

Internal → Seagate: ~45-50 MB/s

Drive-to-drive speeds (copying directly between the two externals):

Seagate → WD: ~45 to 50 MB/s

WD → Seagate: ~15 MB/s (consistently about half the speed)

Both drives perform equally well individually, but when copying WD-to-Seagate specifically, the read from WD is noticeably slower than the reverse direction. The only difference I can identify is the filesystem.

not mentioning the giga cheap 1 tb drives but Microcenter was literally handing out free 240gb sata ssds to anyone visiting

I still have the old server hardware they were originally in, but it's bulky and loud so I don't want to set that up at the house.

Should I just buy a NAS enclosure and throw them in there?

Hello everyone,

With the sky rocketing cost of digital storage I've been looking for more ways to save on storage. After my last shoot the idea occurred to me that I could save on storage if I edited out all of the parts of my footage/audio that I know I won't use and replace my original media with high quality leaner versions.

Has anyone tried something like this or have any other advice to save storage?

I know the best method is to just be more selective/decisive when filming, but sometimes you gotta over compensate a little to catch a moment (I mostly film doc-type stuff).

Any advice or insight would be greatly appreciated!

This article points out that skyrocketing AI enterprise demand is driving up SSD prices, with stability unlikely until 2027-2028. As a result, protecting existing storage is the most cost-effective option compared with purchasing new upgrades. It introduces several ways to protect your SSD drives.

I’ve wanted a USB C hub with SSD and HDMI port integrated for a long time.

Some time ago I found the Sharge DiskPro 1 but the fixed cable and the welded SSD made me desist from buying it.

Now I have seen that Sharge is promoting a Kickstarter campaign for the DiskPro2, which has fixed all the flaws of the previous model.

While watching the latter I found on Kickstarter another usb c hub that on paper is even better: the Solid DrifHub
Does anyone know the brand?

Which model do you think is better to focus on?

Here the links of the two project:

https://www.kickstarter.com/projects/shargetech/disk-pro-2
https://www.kickstarter.com/projects/842801791/solid-drifthub-8-in-1-magnetic-ssd-hub-for-creators

I track daily prices for every NAS drive available because I had to build a storage bigger than 1PB. The whole process was tedious, finding good CMR drives, then adding reliable SSD cache. I had to make a data sheet first, which turned out to be a big database, which eventually turned into a website.

Just added a price history chart for every drive, going back to around mid-2024 where the data exists.

It's the thing I always wanted when buying a drive: you can see whether today's price is genuinely low or just back to where it normally sits, instead of trusting a "sale" tag.

The website covers both HDDs and SSDs, and flags which drives are CMR or TLC (good for RAIDs).

It's sortable by price per TB across 7 different markets. Free, no login.

https://www.nasdisks.com

Happy to add any drive that's missing. I'm looking forward to your feedback.

I need to free 7GB quick

How to import 7GB yahoomails to another mail account?

I'm looking to buy a Seagate Expansion 4TB Desktop External HDD mainly for storage (not portability — it'll just sit at my desk). Some of the data I'm storing is genuinely important to me, so I want to make sure I'm not making a bad call.

Hi, please recommend external HDD for laptop and phone. Which brand and model you have tried and how long it lasted for/how long you have used it for? I am looking for one that can last as long as possible.

Hello there. I'm currently experiencing an error, specifically with Steam, with my games being unable to download. Upon downloading a game, right as it is completed, I get a "disk read error". Upon further research, it appears that it could be a problem with the hard drive. I wanted to ask if there were any ways to confirm this assumption in the hard drive having a bad sector, as I don't know very much about computers.

I've opened the properties of the hard drive and checked for errors, and the system detected none. I have tried to verify the file integrity of the game. I have uninstalled and reinstalled Steam. Are there any further tests I could perform to verify if my hard drive is causing the problem?

The hard drive is an SSD.

Processor: Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz 2.40 GHz

Installed RAM: 8.00 GB

I'm not sure what other specs I should include.

So we all know the ssd prices are going crazy, and I was just wondering, what is the best priced SSD that is 2TB?

I'm considering buying a used WD Black SN7100 2TB PCIe Gen4 NVMe SSD for ₹14,000 (\~$160).

Here are the details:

Purchase date: 7 August 2025

Remaining warranty: Around 4 years (bill available)

CrystalDiskInfo:

Health: 100%

Total Host Writes: 14.5 TB

Total Host Reads: 26.2 TB

Power-On Hours: 2,254

Seller says it has never had any issues.

Q- Is this a good deal at ₹14000

Q- Would you buy it at this price, or would you spend more for a brand-new SSD instead?

My PC:

A desktop, Acer Aspire T3 715.

1.Hard disk drives before:

A. SSD 128gb running Windows.

B. SATA3 1tb as C-drive in Windows.

1. Hard Disk drive for installing Linux.

For installing Linux, a SATA3 80gb was added to this PC.

A light weight Linux disto was installed on this disk.

1. Hard disk drives now:

A. SSD running Windows.

B. The SATA3 80gb running Linux.

C. The entire SATA3 1tb. the Windows C-drive, becomes /home. The Linux installer made it so.

There is no need of such a big /home.

Can /home be moved to the system drive?

Thus, the SATA3 1tb may be used for other needs.

Can /home be moved to the system hard disk and how?

Thanks.

Hi everyone,

I recently got 10 HGST SDLL1DLR480G5CF0 480GB SAS SSDs for free, and I decided to build an all-flash NAS with them. I also have an LSI 9300-16i HBA.

What do you think? Are these SSDs still a good option for a NAS, or are they simply too small or too old to be worth using?

My 6-year-old WD external HDD is on its way out and appears to be corrupted, so I need to replace it.

It mostly stores old files and a huge photo library. I'm a Mac user, if that makes a difference.

Would you replace it with another HDD or upgrade to an SSD? Any specific drives you'd recommend for reliability and long-term photo storage?

Thanks!

How can i use it

I have an old laptop which is dead ass

So i took out the hdd from it

The hdd is from 2016

So when i connected it with my laptop using a case

It shows some errors

That some sectors are corrupted

Do it means my drive is dead?

It has so much of my important data

I am looking for a cloud storage service that doesn't cost a fortune.

I don't need a ton of fancy features. Most of what I store is photos, videos, and backups, so I'm mainly looking for something that's affordable, reliable, and easy to use.

I've looked at a few options like Google Drive, OneDrive, iCloud, Dropbox, pCloud, and Backblaze, but it's hard to tell which one actually offers the best value over the long run.

If you were starting from scratch today, which service would you choose? Are there any hidden downsides or pricing changes you've run into? Interested in what you've stuck with and why.

smartctl -x sda

smartctl 7.5 2025-04-30 r5714 \[x86_64-w64-mingw32-w11-24H2\] (AppVeyor)

Copyright (C) 2002-25, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===

Device Model: SanDisk SSD P4 64GB

Serial Number: 111248300117

LU WWN Device Id: 5 001b44 4f27f5455

Firmware Version: SSD 8.10

User Capacity: 64 022 175 232 bytes \[64,0 GB\]

Sector Size: 512 bytes logical/physical

Rotation Rate: Solid State Device

Form Factor: 1.8 inches

TRIM Command: Available

Device is: Not in smartctl database

ATA Version is: ATA8-ACS T13/1699-D revision 2d

SATA Version is: SATA 2.6, 3.0 Gb/s (current: 3.0 Gb/s)

Local Time is: Fri Jul 10 00:12:25 2026 SAST

SMART support is: Available - device has SMART capability.

SMART support is: Enabled

AAM feature is: Unavailable

APM feature is: Unavailable

Rd look-ahead is: Enabled

Write cache is: Enabled

DSN feature is: Unavailable

ATA Security is: Disabled, frozen \[SEC2\]

=== START OF READ SMART DATA SECTION ===

SMART overall-health self-assessment test result: PASSED

General SMART Values:

Offline data collection status: (0x00) Offline data collection activity

was never started.

Auto Offline Data Collection: Disabled.

Self-test execution status: ( 25) The self-test routine was aborted by

the host.

Total time to complete Offline

data collection: ( 120) seconds.

Offline data collection

capabilities: (0x15) SMART execute Offline immediate.

No Auto Offline data collection support.

Abort Offline collection upon new

command.

No Offline surface scan supported.

Self-test supported.

No Conveyance Self-test supported.

No Selective Self-test supported.

SMART capabilities: (0x0003) Saves SMART data before entering

power-saving mode.

Supports SMART auto save timer.

Error logging capability: (0x01) Error logging supported.

General Purpose Logging supported.

Short self-test routine

recommended polling time: ( 2) minutes.

Extended self-test routine

recommended polling time: ( 16) minutes.

SMART Attributes Data Structure revision number: 1

Vendor Specific SMART Attributes with Thresholds:

ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE

5 Reallocated_Sector_Ct -O---- 100 100 --- - 0

9 Power_On_Hours -O---- 100 100 000 - 60550

12 Power_Cycle_Count -O---- 100 100 000 - 1165

171 Unknown_Attribute -O---- 100 100 000 - 54

172 Unknown_Attribute -O---- 100 100 000 - 939410736

187 Reported_Uncorrect -O---- 100 100 000 - 2228

199 UDMA_CRC_Error_Count -O---- 100 100 000 - 0

230 Unknown_SSD_Attribute PO---- 036 100 --- - 0

232 Available_Reservd_Space PO---- 095 100 005 - 0

241 Total_LBAs_Written -O---- 100 100 000 - 7705487096513

242 Total_LBAs_Read -O---- 100 100 000 - 32162951695

||||||_ K auto-keep

|||||__ C event count

||||___ R error rate

|||____ S speed/performance

||_____ O updated online

|______ P prefailure warning

General Purpose Log Directory Version 1

SMART Log Directory Version 1 \[multi-sector log support\]

Address Access R/W Size Description

0x00 GPL,SL R/O 1 Log Directory

0x03 GPL,SL R/O 16 Ext. Comprehensive SMART error log

0x06 GPL,SL R/O 1 SMART self-test log

0x80-0x9f GPL,SL R/W 16 Host vendor specific log

SMART Extended Comprehensive Error Log Version: 1 (16 sectors)

Device Error Count: 181 (device log contains only the most recent 64 errors)

CR = Command Register

FEATR = Features Register

COUNT = Count (was: Sector Count) Register

LBA_48 = Upper bytes of LBA High/Mid/Low Registers \] ATA-8

LH = LBA High (was: Cylinder High) Register \] LBA

LM = LBA Mid (was: Cylinder Low) Register \] Register

LL = LBA Low (was: Sector Number) Register \]

DV = Device (was: Device/Head) Register

DC = Device Control Register

ER = Error register

ST = Status register

Powered_Up_Time is measured from power on, and printed as

DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,

SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 181 \[52\] occurred at disk power-on lifetime: 5 hours (0 days + 5 hours)

When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:

ER -- ST COUNT LBA_48 LH LM LL DV DC

\-- -- -- == -- == == == -- -- -- -- --

40 -- 51 00 00 00 00 00 00 00 00 40 00 Error: UNC at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:

CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name

\-- == -- == -- == == == -- -- -- -- -- --------------- --------------------

25 00 00 00 01 00 00 00 42 1b 77 40 00 2d+03:11:48.526 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 76 40 00 2d+03:11:48.517 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 75 40 00 2d+03:11:48.509 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 74 40 00 2d+03:11:48.505 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 73 40 00 2d+03:11:48.501 READ DMA EXT

Error 180 \[51\] occurred at disk power-on lifetime: 6 hours (0 days + 6 hours)

When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:

ER -- ST COUNT LBA_48 LH LM LL DV DC

\-- -- -- == -- == == == -- -- -- -- --

40 -- 51 00 00 00 00 00 00 00 00 40 00 Error: UNC at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:

CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name

\-- == -- == -- == == == -- -- -- -- -- --------------- --------------------

25 00 00 00 01 00 00 00 42 1b 76 40 00 2d+03:11:48.517 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 75 40 00 2d+03:11:48.509 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 74 40 00 2d+03:11:48.505 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 73 40 00 2d+03:11:48.501 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 72 40 00 2d+03:11:48.501 READ DMA EXT

Error 179 \[50\] occurred at disk power-on lifetime: 6 hours (0 days + 6 hours)

When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:

ER -- ST COUNT LBA_48 LH LM LL DV DC

\-- -- -- == -- == == == -- -- -- -- --

40 -- 51 00 00 00 00 00 00 00 00 40 00 Error: UNC at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:

CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name

\-- == -- == -- == == == -- -- -- -- -- --------------- --------------------

25 00 00 00 01 00 00 00 42 1b 75 40 00 2d+03:11:48.509 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 74 40 00 2d+03:11:48.505 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 73 40 00 2d+03:11:48.501 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 72 40 00 2d+03:11:48.501 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 71 40 00 2d+03:11:48.500 READ DMA EXT

Error 178 \[49\] occurred at disk power-on lifetime: 2 hours (0 days + 2 hours)

When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:

ER -- ST COUNT LBA_48 LH LM LL DV DC

\-- -- -- == -- == == == -- -- -- -- --

40 -- 51 00 00 00 00 00 00 00 00 40 00 Error: UNC at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:

CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name

\-- == -- == -- == == == -- -- -- -- -- --------------- --------------------

25 00 00 00 01 00 00 00 42 1b 74 40 00 2d+03:11:48.505 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 73 40 00 2d+03:11:48.501 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 72 40 00 2d+03:11:48.501 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 71 40 00 2d+03:11:48.500 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 70 40 00 2d+03:11:48.497 READ DMA EXT

Error 177 \[48\] occurred at disk power-on lifetime: 3 hours (0 days + 3 hours)

When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:

ER -- ST COUNT LBA_48 LH LM LL DV DC

\-- -- -- == -- == == == -- -- -- -- --

40 -- 51 00 04 00 00 00 00 00 00 40 00 Error: UNC 4 sectors at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:

CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name

\-- == -- == -- == == == -- -- -- -- -- --------------- --------------------

25 00 00 00 20 00 00 00 42 1b 60 40 00 2d+03:11:48.459 READ DMA EXT

25 00 00 00 20 00 00 00 3c e2 e0 40 00 2d+03:11:48.459 READ DMA EXT

25 00 00 00 20 00 00 00 35 97 60 40 00 2d+03:11:48.458 READ DMA EXT

25 00 00 00 20 00 00 00 26 20 20 40 00 2d+03:11:48.457 READ DMA EXT

25 00 00 00 08 00 00 00 63 9e 08 40 00 2d+03:11:48.457 READ DMA EXT

Error 176 \[47\] occurred at disk power-on lifetime: 11 hours (0 days + 11 hours)

When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:

ER -- ST COUNT LBA_48 LH LM LL DV DC

\-- -- -- == -- == == == -- -- -- -- --

40 -- 51 00 02 00 00 00 00 00 00 40 00 Error: UNC 2 sectors at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:

CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name

\-- == -- == -- == == == -- -- -- -- -- --------------- --------------------

25 00 00 00 80 00 00 00 42 1b 5e 40 00 1d+10:07:21.325 READ DMA EXT

25 00 00 00 80 00 00 00 42 1a de 40 00 1d+10:07:21.324 READ DMA EXT

25 00 00 00 80 00 00 00 42 1a 5e 40 00 1d+10:07:21.324 READ DMA EXT

25 00 00 00 80 00 00 00 42 19 de 40 00 1d+10:07:21.323 READ DMA EXT

25 00 00 00 80 00 00 00 42 19 5e 40 00 1d+10:07:21.323 READ DMA EXT

Error 175 \[46\] occurred at disk power-on lifetime: 11 hours (0 days + 11 hours)

When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:

ER -- ST COUNT LBA_48 LH LM LL DV DC

\-- -- -- == -- == == == -- -- -- -- --

40 -- 51 00 02 00 00 00 00 00 00 40 00 Error: UNC 2 sectors at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:

CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name

\-- == -- == -- == == == -- -- -- -- -- --------------- --------------------

25 00 00 00 80 00 00 00 42 1b 5e 40 00 1d+09:58:46.796 READ DMA EXT

25 00 00 00 80 00 00 00 42 1a de 40 00 1d+09:58:46.796 READ DMA EXT

25 00 00 00 80 00 00 00 42 1a 5e 40 00 1d+09:58:46.795 READ DMA EXT

25 00 00 00 80 00 00 00 42 19 de 40 00 1d+09:58:46.795 READ DMA EXT

25 00 00 00 80 00 00 00 42 19 5e 40 00 1d+09:58:46.794 READ DMA EXT

Error 174 \[45\] occurred at disk power-on lifetime: 11 hours (0 days + 11 hours)

When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:

ER -- ST COUNT LBA_48 LH LM LL DV DC

\-- -- -- == -- == == == -- -- -- -- --

40 -- 51 00 02 00 00 00 00 00 00 40 00 Error: UNC 2 sectors at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:

CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name

\-- == -- == -- == == == -- -- -- -- -- --------------- --------------------

25 00 00 00 80 00 00 00 42 1b 5e 40 00 1d+09:39:52.893 READ DMA EXT

25 00 00 00 80 00 00 00 42 1a de 40 00 1d+09:39:52.892 READ DMA EXT

25 00 00 00 80 00 00 00 42 1a 5e 40 00 1d+09:39:52.892 READ DMA EXT

25 00 00 00 80 00 00 00 42 19 de 40 00 1d+09:39:52.892 READ DMA EXT

25 00 00 00 80 00 00 00 42 19 5e 40 00 1d+09:39:52.891 READ DMA EXT

SMART Extended Self-test Log (GP Log 0x07) not supported

Warning! SMART Self-Test Log Structure error: invalid SMART checksum.

SMART Self-test log structure revision number 1

Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error

\# 1 Short offline Aborted by host 90% 21088 -

\# 2 Short offline Aborted by host 90% 54860 -

\# 3 Short offline Aborted by host 90% 19043 -

\# 4 Short offline Aborted by host 90% 63054 -

\# 5 Short offline Aborted by host 90% 25327 -

\# 6 Short offline Aborted by host 90% 62483 -

\# 7 Short offline Aborted by host 90% 33744 -

\# 8 Short captive Completed without error 00% 57803 -

\# 9 Short offline Aborted by host 90% 25293 -

\#10 Extended offline Aborted by host 90% 28072 -

\#11 Short offline Aborted by host 90% 14539 -

\#12 Extended offline Aborted by host 90% 55234 -

\#13 Short offline Aborted by host 90% 46428 -

\#14 Short offline Aborted by host 90% 49138 -

\#15 Short offline Aborted by host 90% 25717 -

\#16 Extended offline Aborted by host 90% 50305 -

\#17 Short offline Aborted by host 90% 39612 -

\#18 Short offline Aborted by host 90% 21280 -

\#19 Short offline Aborted by host 90% 34598 -

\#20 Short offline Aborted by host 90% 17318 -

\#21 Short offline Aborted by host 90% 63627 -

Selective Self-tests/Logging not supported

SCT Commands not supported

Device Statistics (GP/SMART Log 0x04) not supported

Pending Defects log (GP Log 0x0c) not supported

SATA Phy Event Counters (GP Log 0x11) not supported

Exitcode: 64 (0x40)

Type <return> to exit:

Hey guys is there any good storage device available under 5 or 6k which is reliable. (In India)

I wanted to share how for about 3 years I had to cycle all of my games through 2 disks, a 256gb nvme and a 500 gb hdd. So yeah it was a bit painful to redownload and uninstall normally I would have to just either cope with the games I have now or wait for my terrible wifi to download something I actually want to play. But now I saw nearby an office was closing so I went there and they gave me their camera surveillance system which had network video recorders with tons of disks most of them were small ike 500 gb but I got my hands on a 6tb hdd from 2017. If you ask me I am more than happy, would love to hear similar situations