You are not logged in.
So I have this one hard drive with two NTFS partitions both around 2.5TBs after I close my Arch Linux session and boot Windows on the same device one of them didn't properly boot on Windows. I thought maybe Linux didn't disconnect the drive properly and rebooted Arch and well... The name shows up but when I try to open the drive I'm getting the following error: `An error occurred while accessing 'Elements', the system responded: An unspecified error has occurred: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.` Sooo... I like to assume there is a certain tool to fix that. Can you help me out?
Journal, before you ask: https://privatebin.net/?0cdddbfd7b1c283 … v8gwMVobod
Last edited by xanrer (2023-07-05 19:35:53)
Offline
Can you paste a bog standard line based journal next time, produced by
sudo journalctl -b?
Your problem is
ntfs3: sdb1: volume is dirty and \"force\" flag is not set!
ntfs3: sdb2: volume is dirty and \"force\" flag is not set!you "could" set said force flag and deal with any potential fallouts. What you should actually be doing is booting Windows again which should run a chkdsk on this particular disk again (or boot the "working" Windows and chkdsk both partitions from there).
Of general note here, the ntfs3 driver included in the kernel has somewhat of a history of corrupting NTFS file systems relatively easily (though it has bettered quite a bit), if you want a more stable ntfs implementation consider ntfs-3g (which will have a perf hit though)
Last edited by V1del (2023-06-20 08:30:20)
Offline
Roger that I'll run chkdsk on Windows, also I thought I had NTFS-3g, guess I didn't activate it correctly. Thank you.
Offline
Ran the command as you said, got an:
1150174 files processed.
File data verification completed.
Phase duration (User file recovery): 1.47 days.
An unspecified error occurred (766f6c756d652e63 470).
Please tell me there are better programs than built-in Windows ones. I'll pay, doesn't matter how expensive the program is.
Offline
https://wiki.archlinux.org/title/SMART and check the dmesg output when trying to *read* from the disk on linux.
You'll probably pay for a new drive.
As a general not, see the 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.
Offline
Did `sudo smartctl -a /dev/sdb` then ran `sudo dmesg` here is the output:
https://privatebin.net/?eb407931d7c30f4 … chYohaW7R4
Offline
The output of smartctl -a would be interesting, it doesn't lead to any action as a command. But that dmesg tail doesn't really look confidence inspiring as to the disk health.
Offline
Offline
9 Power_On_Hours 0x0032 096 096 000 Old_age Always - 3557
197 Current_Pending_Sector 0x0032 198 198 000 Old_age Always - 2438
# 2 Extended offline Completed: read failure 90% 2710 1021332032[ 24.858145] sd 1:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=2s
[ 24.858151] sd 1:0:0:0: [sdb] tag#0 Sense Key : Medium Error [current]
[ 24.858153] sd 1:0:0:0: [sdb] tag#0 Add. Sense: Unrecovered read error
[ 24.858156] sd 1:0:0:0: [sdb] tag#0 CDB: Read(16) 88 00 00 00 00 02 0b 56 06 88 00 00 02 00 00 00
[ 24.858157] critical medium error, dev sdb, sector 8780121736 op 0x0:(READ) flags 0x80700 phys_seg 5 prio class 2
[ 27.935977] sd 1:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=2s
[ 27.935986] sd 1:0:0:0: [sdb] tag#0 Sense Key : Medium Error [current]
[ 27.935989] sd 1:0:0:0: [sdb] tag#0 Add. Sense: Unrecovered read error
[ 27.935993] sd 1:0:0:0: [sdb] tag#0 CDB: Read(16) 88 00 00 00 00 02 0b 56 06 98 00 00 00 08 00 00
[ 27.935995] critical medium error, dev sdb, sector 8780121752 op 0x0:(READ) flags 0x0 phys_seg 8 prio class 2
[ 27.936004] Buffer I/O error on dev sdb2, logical block 3887426656, async page read
[ 27.936009] Buffer I/O error on dev sdb2, logical block 3887426657, async page read
[ 27.936012] Buffer I/O error on dev sdb2, logical block 3887426658, async page read
[ 27.936015] Buffer I/O error on dev sdb2, logical block 3887426659, async page read
[ 27.936018] Buffer I/O error on dev sdb2, logical block 3887426660, async page read
[ 27.936020] Buffer I/O error on dev sdb2, logical block 3887426661, async page read
[ 27.936022] Buffer I/O error on dev sdb2, logical block 3887426662, async page read
[ 27.936025] Buffer I/O error on dev sdb2, logical block 3887426663, async page read
[ 30.958228] sd 1:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=2s
[ 30.958237] sd 1:0:0:0: [sdb] tag#0 Sense Key : Medium Error [current]
[ 30.958240] sd 1:0:0:0: [sdb] tag#0 Add. Sense: Unrecovered read error
[ 30.958243] sd 1:0:0:0: [sdb] tag#0 CDB: Read(16) 88 00 00 00 00 02 0b 56 06 98 00 00 00 08 00 00
[ 30.958245] critical medium error, dev sdb, sector 8780121752 op 0x0:(READ) flags 0x0 phys_seg 8 prio class 2
[ 30.958254] Buffer I/O error on dev sdb2, logical block 3887426656, async page read
[ 30.958259] Buffer I/O error on dev sdb2, logical block 3887426657, async page read
[ 33.902732] sd 1:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=2s
[ 33.902742] sd 1:0:0:0: [sdb] tag#0 Sense Key : Medium Error [current]
[ 33.902746] sd 1:0:0:0: [sdb] tag#0 Add. Sense: Unrecovered read error
[ 33.902751] sd 1:0:0:0: [sdb] tag#0 CDB: Read(16) 88 00 00 00 00 02 0b 56 06 98 00 00 00 08 00 00
[ 33.902753] critical medium error, dev sdb, sector 8780121752 op 0x0:(READ) flags 0x0 phys_seg 8 prio class 2
[ 33.902764] buffer_io_error: 6 callbacks suppressed
[ 33.902765] Buffer I/O error on dev sdb2, logical block 3887426656, async page read
[ 33.902772] Buffer I/O error on dev sdb2, logical block 3887426657, async page read
[ 33.902776] Buffer I/O error on dev sdb2, logical block 3887426658, async page read
[ 33.902780] Buffer I/O error on dev sdb2, logical block 3887426659, async page read
[ 33.902783] Buffer I/O error on dev sdb2, logical block 3887426660, async page read
[ 33.902786] Buffer I/O error on dev sdb2, logical block 3887426661, async page read
[ 33.902790] Buffer I/O error on dev sdb2, logical block 3887426662, async page read
[ 33.902793] Buffer I/O error on dev sdb2, logical block 3887426663, async page readMake sure to have backups of everything on that drive, you can eg. use https://wiki.archlinux.org/title/Disk_c … g_ddrescue
Then you can try https://wiki.archlinux.org/title/Badblocks (the non-destructive mode is gonna take ages) to see how bad things really are.
But the drive had it's first issues at least 800 power-on hours ago, it is for now NOT reliable.
(In the best of all events only one sector died, but I'd rather not hope for that)
Offline
Got it, I'm going to buy a new hard drive in a week. After that, I'll do what you recommended. I'll try to keep you updated on the issue when the time comes. Thank you two for everything!
While we are on it, how can I prevent this from ever happening again? My Windows 10 doesn't even have hibernation and I never used it on my Arch either. I have NTFS-3g installed. But I would like to know if it's possible to know these sector errors beforehand.
Offline
This is a physical error and for external devices the cause is usually that they get thrown around too much - esp. while they're on power.
=> Treat the thing more carefully.
Other causes are heat and dirt, but after less than half a year on power, unless you're operting it in the desert that's not as likely.
Your windows 10, like every windows 10, supports hibernates and defaults to hibernation when you shut it down ("fast start" - essentially a cheap trick to make windows look less fat)
This does however lead to filesystem inconsistencies, not "Sense Key : Medium Error [current]", that's a physically damaged drive.
But I would like to know if it's possible to know these sector errors beforehand.
Before they occur? You gotta ask Doc Brown, the old weirdo claims he once built a time machine that looked like a DeLorean.
Otherwise https://wiki.archlinux.org/title/S.M.A.R.T.#smartd can notify you on apparent drive issues.
Offline
Otherwise https://wiki.archlinux.org/title/S.M.A.R.T.#smartd can notify you on apparent drive issues.
Is there also a tool to improve my disks health if s.m.a.r.t says something is wrong?
Offline
that's a physically damaged drive
You're not gonna fix that with a software pill.
Once SMART starts logging errors and they creep up, the drive is in the process of dying.
Offline
Inevitable eh... Guess that's how life goes. Funnily enough, this hard drive is almost brand new. I just cloned the partition form the old one... Which was also a clone of another old one... And that was also another clone... Guess I'd be better off with copy and paste instead of partition cloning but I couldn't find any software that does that job perfectly.
Offline
The cloning is not the problem. This kind of damage does not happen from any software access.
Offline
Then I could assume that my current drive is going to the trash, no?
Offline
Then you can try https://wiki.archlinux.org/title/Badblocks (the non-destructive mode is gonna take ages) to see how bad things really are.
If you're super-lucky and the damage is contained the blocks will be re-located by the drive and you can _use_ it, but not _trust_ it.
(So eg. put a copy of your porn collection on it and attach it to your Tv, stuff where it can still be useful but it doesn't matter if it fails)
Offline
Aw maaan, I didn't even mentioned that my 2.5TBs of data being porn, how did you understand that?
That aside... I wish I never had to use windows so I didn't had to keep up with this bs. But since I have a cursed CPU my games on Linux (yes every distro not just arch) only works with less than half of the FPS on Windows. In case you are wondering its a Lenovo E595. never again I'll buy AMD. So that I can cut Windows outa my life.
Another thing, Half of my 5TB hard drive is actually kicking well. I halved it into two partitions beforehand. Hallelujah for that.
edit: I know this is getting out of scope but, can you suggest me a good copying software for Linux? After I get my data back I'd like to try the copy paste approach instead of cloning one.
Last edited by xanrer (2023-06-23 19:55:13)
Offline
how did you understand that?
"Projection" ![]()
Don't use the "good" partition to backup the "bad" one.
Wait for the replacement, ddrescue the old onto the new one, then check the old one w/ badblocks.
Avoid using it until you've cloned it as much as possible since we don't know the nature of the damage.
Especially do *not* run badblocks now, backup the data first!
Offline
Roger that! I'll keep you updated. And thank you.
Offline
Sooo... I was about to buy the new HDD and realized umm... My partition works again??? I literally did nothing. Is there an explanation for that? Haven't tried it on Windows yet but yeah... Works on Linux so I'll bite.
https://privatebin.net/?be0d6b86c6ce4cf … KPCgncQPyM
https://privatebin.net/?91ced8ce1bd7bd8 … YS3WRfDVfW
Now that I think about it... I slightly adjusted the physical location of my HDD like by 3 centimeters earlier in the day... Could that be???
Also should I even put a [Solved] to this topic? I don't know whats going on.
Offline
Was the power cable under tension?
Still run a complete long smartctl test.
Last edited by seth (2023-06-25 18:39:54)
Offline
I don't think it was under tension however the HDD was somewhat close to my PC. Which very well could be the reason.
For sure, I'm assuming the test runs in the background because it pushed me back to my prompt. So I'll run `smartctl -H /dev/sdb` when the time hits, which it says 470 minutes.
Offline
You moved the encased drive around on the outside?
Is the PC case not properly EM shielded?
Otherwise I suspect there's something loose on the inside and that wiggled a bit into place - or the case itself is broken.
You mentioned that you've been replacing this a lot, do you purchase a complete device inside a case or just a disk and re-use the same case all the time?
Offline
They are different hard drives, current one is this: https://www.westerndigital.com/products … 50BBK-WESN Before this one I had two separate hard drives also from WD and they have never been out of their shells.
Offline