Linux OS mounts a partition as read-only if it detects a fault or an error. Sometimes it does that rather than refusing to mount all together. So, you have to check the health of the usb memory stick and the health of the file system with chkdsk/fsck etc.
I had in idea in mind for cards crashing at VRel (signs of a dying core), a reverse-shunt mod (lower the resistance of the current sensing shunt), reducing the power draw of the card and stopping the crashing, but I doubt that will work on the artifacting one.
I am not sure if you are just joking about linux being bad, but of course you are going to have a difficult time working with it if you dont know the tool... A lot of this is like someone holding a soldering iron with only 2 fingers and then complaining that soldering is hard...of course its hard if you are holding the tool wrong.
Its caused by linux. I booted into another tinylinux SSD and every USB drive with tinylinux on it was locked up with SYSTEM READ ONLY so i had to run that program for all my USB thumb drives that were connected while i was booting from that tinylinux SSD. Linux did it am sure.
@@northwestrepair Not sure what happened in your case, but drives going read-only by themselves is something Linux does when it thinks the drive is dying and it doesn't want to make things worse.
@@northwestrepair Yeah, but _why_ did it do it. I've only been using it seriously for a few years now, but I now use Linux for everything. I have a gaming PC, a router and multiple servers on Linux. ProxMox for the servers and router, even. I've also been putting user friendly distros on the computers of people who are trying to escape MS. Despite all that, I have _never_ seen this. I've seen all sorts of silly things, like starting x with sudo breaking x's permissions, crappy NTFS support causing NTFS partitions to not mount without clearing the dirty bit, I've seen several types of permissions weirdness with networked shares... But this is not something that looks like a typical Linux breakage/kludge. There's more going on here than "it's just linux." You might want to look into what caused it to start locking file systems.
"Case sensitivity a faulty logic in the operating system design". That's not the operating system fault, it's a choice by the shell script developer... Add a [to]lower() somewhere.
Not only, extracting the pen or forcing the shutdown while a write on the filesystem is ongoing. It's how ext filesystem works and is a protection against data losses.
I remember my live linux on usb always somewhat destroy filesystem after just slightly use. When i plugged stick into windows, it reads absurdly high capacity (for example srick was 8GB but system reads terabytes)
haha , if i was the owner of the card, i would prefer to use the vga as it is now and forget about its problems because there is no way to fix it but the card works anyway.
Break out the fuming nictric acid, get down to the core and fix it or bypass that core. Now you're talking! 😝 I've always wanted one of those nanometer stages and tool holders.
I recently started using a FS that is not case sensitive and it’s so bad. How can you say being case sensitive is faulty logic? Also get familiar with ‘mount, ‘touch’, ‘cat’’ and ‘dmesg’
This reminds me some Old factory OC-ed cards where the GPU is going to fall in same way right after some new driver is relesed. Flashing back some non-OC bios may slove this kind of behave.
Dumb question but why would it be certain that it's a dead core vs an ripped or oxidised pad or something underneath it? Would it just not work at all if that were the case?
If it was a ripped, oxidised or crached solderjoint you would either not get the card to properly boot (missing phase), booting in x8, or it would artifact in the same place the whole time (line artifacts). And he tested to confirm, that this was not the case here by runing Haven, and measuring phases . In adition the test tells him its pixel miscompare. Atleast that is my experience, but im no NWR so dont take it as gospel :P
Looks like you need file system check - fsck. In some cases when the system turned off without proper shutdown procedure, file system may be in read only state until fsck confirm its ok.
I wish you were closer I have a 1660 super that was dead on reliable, never OCd and did exactly what I wanted it to do.... till it didn't. Same senerio. I think it has a dead Vram chip and not one will touch it in Thailand.
If you use a FAT filesystem and don't shut it down cleanly, it will have problems. Doesn't matter if it's Windows, Linux, or OS X. Linux will mount unclean filesystems as read-only by default. Nobody who actually runs Linux runs it on a crusty old FAT filesystem; it'd be ext4 or something. But if you use a more advanced filesystem, Windows won't be able to read it.
Ooohhhh... So this is the same problem that the Linux NTFS driver has. Except that wont even let you mount the drive if the dirty bit is set. I tried using an NTFS partition for my games drive on this gaming PC, for obvious reasons. It didn't go well. BTRFS hasn't had a single problem, though. I took this as a sign to finally dump Windows completely.
Sometimes if a ntfs filesystem is dirty it will boot read only. You can chkdsk /X [drive[ in windows to fix it. Also if you are not root you can su root. If you are booting with that disk it is probably not ntfs though I assume it is more like ext4 or btrfs.
Why no fix?? But i saw many old gpus with artifacts that People fix with lowering voltage or better lower clock mhz easy fix for artifacts because value are too much on some gpus..
my 1650 does the same but i recovered it with a big undervolt. obviously i lost speed but it doesn't produce any artifacts. do some more tests before giving up.
@@AbzRaider I said I can fix it, get it back to 100% functionality with a little bit lower performance. Only then it can't be returned to the owner, so it can be solved. I'm sure Tony can fix it another way though.
It's not just a Linux thing, if Windows also detects a problem with a drive it will forcefully make the partition read-only to avoid further damage to it. At least on Linux you were able to figure out the problem relatively headache free. This is why Windows will never replace Linux for server owners ;)
When you boot that Linux environment the # symbol means that every command is being ran with root permissions which has r/w access to all files irregardless of file permissions or attributes. When it shows that files are available read only it means that the partition with your Linux environment gets corrupted and automatically mounted as read only.
I think a 3070 getting over 2Ghz on core consistently on Furmark is not normal at all. Even on Timespy, it should be around 1935Mhz, not 2Ghz+ . I suspect something wrong about the vBIOS. Maybe try to reflash it.
I did wonder if Tony should have underclocked the card to around 1905mhz to see if it still glitches - but the low board power draw tells the story of there being something wrong with some of the CUDA coresa
Well I would say it is not a dead core, maybe some kind of internal fault, I would reconsider reballing, a dead core will not even run a test. semi dead maybe, still working better than a 1050 ti xD
Kinda funny I was gonna ask you if you'd ever recommend getting an oscilloscope for diagnosing and you just used one in this particular video haha 😆 Thanks as always for sharing your curiosity trips:)
umm if you put it on ebay... you dont say it is artifacting.. you say it is untested and you know nothing about it ... :D also -- if Linux gives me too much problem, i use rm -r * :) (DONT DO THIS!!!... I AM KIDDING! lol
I asked for every video you make. Just keep making them. They're always awesome.
I like to pretend I know wtf is going on and what you are doing when I watch your videos.
Same
😂😂😂
😂
Linux OS mounts a partition as read-only if it detects a fault or an error. Sometimes it does that rather than refusing to mount all together. So, you have to check the health of the usb memory stick and the health of the file system with chkdsk/fsck etc.
yes !
😮
everytime I see pixel miscompare in my logs I die on the inside a little bit
Tá explicado pq vc é tão foda nos reparos, vc assiste esse cara
this 3070 looked clean and well cared for. that's a bummer
I had in idea in mind for cards crashing at VRel (signs of a dying core), a reverse-shunt mod (lower the resistance of the current sensing shunt), reducing the power draw of the card and stopping the crashing, but I doubt that will work on the artifacting one.
The command to change permissions on files in *nix is 'chmod'
It's a bit more complicated when the entire filesystem gets locked down unexpectedly, usually it's for the device's own protection.
@@kayblis Just add -R to recursively change all data in a folder ;)
GiGaSzS in this case, the whole filesystem was mounted "ro" for whatever reason. This is not a "chmod" situation.
How can I get the Nvidia diagnosis utilities by RoboCop 1.2 , isn't in the GPU shared driver 😢
I am not sure if you are just joking about linux being bad, but of course you are going to have a difficult time working with it if you dont know the tool...
A lot of this is like someone holding a soldering iron with only 2 fingers and then complaining that soldering is hard...of course its hard if you are holding the tool wrong.
It locking down the file system is usually a sign of a more sinister problem. Would run a fsck and/or check logs to figure out why it locked it down.
Its caused by linux.
I booted into another tinylinux SSD and every USB drive with tinylinux on it was locked up with SYSTEM READ ONLY so i had to run that program for all my USB thumb drives that were connected while i was booting from that tinylinux SSD.
Linux did it am sure.
@@northwestrepair Not sure what happened in your case, but drives going read-only by themselves is something Linux does when it thinks the drive is dying and it doesn't want to make things worse.
dirty unmout fsck would have fixed it.
@@northwestrepair onlly shows that understand the tools one is using is essential.
@@northwestrepair
Yeah, but _why_ did it do it.
I've only been using it seriously for a few years now, but I now use Linux for everything. I have a gaming PC, a router and multiple servers on Linux. ProxMox for the servers and router, even. I've also been putting user friendly distros on the computers of people who are trying to escape MS. Despite all that, I have _never_ seen this.
I've seen all sorts of silly things, like starting x with sudo breaking x's permissions, crappy NTFS support causing NTFS partitions to not mount without clearing the dirty bit, I've seen several types of permissions weirdness with networked shares... But this is not something that looks like a typical Linux breakage/kludge.
There's more going on here than "it's just linux." You might want to look into what caused it to start locking file systems.
"Case sensitivity a faulty logic in the operating system design". That's not the operating system fault, it's a choice by the shell script developer... Add a [to]lower() somewhere.
maybe the drive health is deteriorating, that's why it locks itself
Always 👍🏻 for superb Skills
This dude is awesome..
Pending SD card failure. It's the media, not the OS.
Can be. Have seen it happen with crappy SATA>USB adapters too.
Nope. Another ketchup clown.
for sure, knowing Tony he's probably using the crappiest chinese usb he found out there... review incoming?
Not only, extracting the pen or forcing the shutdown while a write on the filesystem is ongoing. It's how ext filesystem works and is a protection against data losses.
😮
I remember my live linux on usb always somewhat destroy filesystem after just slightly use. When i plugged stick into windows, it reads absurdly high capacity (for example srick was 8GB but system reads terabytes)
i have the same exact card.. i'm having anxiety attacks now
haha , if i was the owner of the card, i would prefer to use the vga as it is now and forget about its problems because there is no way to fix it but the card works anyway.
Hell yeah! New upload 😊
It's so funny you struggling with Linux 😂
Break out the fuming nictric acid, get down to the core and fix it or bypass that core. Now you're talking! 😝
I've always wanted one of those nanometer stages and tool holders.
Excellente vidéo comme d'habitude ❤️👍
So,its a dead corebut card looks so pristine from outside
This is all so over my head that I no longer even have to duck. Either the world is getting smarter or I'm ...I'm ...
sigh
I recently started using a FS that is not case sensitive and it’s so bad. How can you say being case sensitive is faulty logic? Also get familiar with ‘mount, ‘touch’, ‘cat’’ and ‘dmesg’
This reminds me some Old factory OC-ed cards where the GPU is going to fall in same way right after some new driver is relesed. Flashing back some non-OC bios may slove this kind of behave.
After the 50 series release, how many weeks will pass until you get your first one to repair. My guess 3 weeks 😂😂
Dumb question but why would it be certain that it's a dead core vs an ripped or oxidised pad or something underneath it? Would it just not work at all if that were the case?
If it was a ripped, oxidised or crached solderjoint you would either not get the card to properly boot (missing phase), booting in x8, or it would artifact in the same place the whole time (line artifacts).
And he tested to confirm, that this was not the case here by runing Haven, and measuring phases . In adition the test tells him its pixel miscompare.
Atleast that is my experience, but im no NWR so dont take it as gospel :P
So I just heard the fires started at NorthridgeFix 🤣
THAT ONE WAS FUN.....SMOKED AFTER THE FIX🤗🤗 I CAN FIX THAT WAY TOO
Now he can actually work on GPU's without needing a preheater XD
💀
Client $$$ , fires and "don't know"s are flying pretty confidently over there.
Looks like you need file system check - fsck.
In some cases when the system turned off without proper shutdown procedure, file system may be in read only state until fsck confirm its ok.
mount -o remount,rw /
nano! It's really nano! Not vi or vim or emacs. I'm starstruck 🌟
Tony pump more content will ya!
I always thought that artefacting is caused by bad memory, I guess I had wrong impression how it works.
wow
I wish you were closer I have a 1660 super that was dead on reliable, never OCd and did exactly what I wanted it to do.... till it didn't. Same senerio. I think it has a dead Vram chip and not one will touch it in Thailand.
I get similar symptom on my RX680, i.e. TDP 80% with voltage stability problem.
It's in a Mac pro 5,1.
😢
No GPU gets left behind......
5090 repair? :)
NO, I DIDN'T!
Hello N-W 🤘
If you use a FAT filesystem and don't shut it down cleanly, it will have problems. Doesn't matter if it's Windows, Linux, or OS X. Linux will mount unclean filesystems as read-only by default.
Nobody who actually runs Linux runs it on a crusty old FAT filesystem; it'd be ext4 or something. But if you use a more advanced filesystem, Windows won't be able to read it.
Ooohhhh... So this is the same problem that the Linux NTFS driver has. Except that wont even let you mount the drive if the dirty bit is set.
I tried using an NTFS partition for my games drive on this gaming PC, for obvious reasons. It didn't go well. BTRFS hasn't had a single problem, though. I took this as a sign to finally dump Windows completely.
😮
Sometimes if a ntfs filesystem is dirty it will boot read only. You can chkdsk /X [drive[ in windows to fix it. Also if you are not root you can su root. If you are booting with that disk it is probably not ntfs though I assume it is more like ext4 or btrfs.
😮
hello tony 🎉
Really? Right in front of my CachyOS?
Awesome!
Makes me wonder how many 50 series you are going to fix 😂😂
💀😊
Hello Tony
Why no fix?? But i saw many old gpus with artifacts that People fix with lowering voltage or better lower clock mhz easy fix for artifacts because value are too much on some gpus..
I enjoyed all the stray shots at Linux being a PITA 😁
If not wanting download software then in windows terminal you can just
attrib -r e:\ /s
my 1650 does the same but i recovered it with a big undervolt. obviously i lost speed but it doesn't produce any artifacts. do some more tests before giving up.
thats not a proper fix.
@@AbzRaider I said I can fix it, get it back to 100% functionality with a little bit lower performance. Only then it can't be returned to the owner, so it can be solved.
I'm sure Tony can fix it another way though.
Reball the gpu and reflash the firmware.
linux is very popular on server side of things ;)))
It's not just a Linux thing, if Windows also detects a problem with a drive it will forcefully make the partition read-only to avoid further damage to it. At least on Linux you were able to figure out the problem relatively headache free. This is why Windows will never replace Linux for server owners ;)
When you boot that Linux environment the # symbol means that every command is being ran with root permissions which has r/w access to all files irregardless of file permissions or attributes.
When it shows that files are available read only it means that the partition with your Linux environment gets corrupted and automatically mounted as read only.
I think a 3070 getting over 2Ghz on core consistently on Furmark is not normal at all. Even on Timespy, it should be around 1935Mhz, not 2Ghz+ . I suspect something wrong about the vBIOS. Maybe try to reflash it.
I did wonder if Tony should have underclocked the card to around 1905mhz to see if it still glitches - but the low board power draw tells the story of there being something wrong with some of the CUDA coresa
Have no idea. 🤷🏼. Lol. But I liked anyways
No reball? Disappointing
Well I would say it is not a dead core, maybe some kind of internal fault, I would reconsider reballing, a dead core will not even run a test. semi dead maybe, still working better than a 1050 ti xD
Poor GPU 😢
Poor 3070 and yes we did learn something today that Linux is weird 😅
Kinda funny I was gonna ask you if you'd ever recommend getting an oscilloscope for diagnosing and you just used one in this particular video haha 😆
Thanks as always for sharing your curiosity trips:)
Are you human? LOL Keep it ON~
👌👍👌👍
sudo it
"sudo nano test94_30" . sudo-SuperUserDo. Elevate privileges. Once you try you will never use only "nano".
I expect every die from that generation to just stop working one day. Samsung 8nm was a mistake
you really like to poke at us linux users huh lol.
Attribute Changer FTW. Thanks! Finally been able to gut windows of bloat.
umm if you put it on ebay... you dont say it is artifacting.. you say it is untested and you know nothing about it ... :D also -- if Linux gives me too much problem, i use rm -r * :) (DONT DO THIS!!!... I AM KIDDING! lol
I thought you were just using TinyCore for testing but you are indeed know thow to use Linux. Respect.
I did ask for it. Could I ask for a p6000 boardview too, please? Awesome channel and videos, btw!
"Linux makes everything difficult" - Lyceus Anubite
You mean dead core is that there is one dead core out of the 5888 cores in a 3070?
SUDO!!!
Linux > windows
2nd
17th comment
First
Jelly.
second
second
If anyone wants this card message me
I’ll take it. I have cores laying around
@HiimAbyss how may I contact you? There's no way to pm you here.
🙏
So a cheap mining card now I guess🫡
If you found a doner core, can't you repair it? 🥹
Yes. But core costs basically the same as working card would, unless you want to gamble with broken ones.
@ Aliexpress
@@MidnightHunters Its a gamble those core came from once working cards and who can say if the core is even alive.
@ At least Aliexpress is good at refunds
@@MidnightHunters but they cant refund NWR or the clients time