May 12, 201610 yr So I just moved 4TB off of a reiserFS formatted drive so I could finally switch all my drives to xfs. However, after formatting it to xfs nothing can write to it. Windows just hangs after moving about 200mb and dolphin hangs or eventually says Disk is Full. Any thoughts? I dont see anything in my dolphin or system logs. I ran a SMART short test and it passed fine.
May 12, 201610 yr Logged into the console, can you write to it as the root user? Can you read from it, ls or df it? Have you tried formatting it again (since you can't write to it you have no data on it to lose) or running a filesystem check? Does it actually write any data to the disk or, as I suspect, is the 200 MB only going as far as the RAM cache? What does your syslog say? Any SMART errors? SMART extended test? Post diagnostics.
May 12, 201610 yr Author Logged into the console, can you write to it as the root user? Can you read from it, ls or df it? Have you tried formatting it again (since you can't write to it you have no data on it to lose) or running a filesystem check? Does it actually write any data to the disk or, as I suspect, is the 200 MB only going as far as the RAM cache? What does your syslog say? Any SMART errors? SMART extended test? Post diagnostics. so oddly enough 3rd reboot was the charm... haha. I can now write to it. The syslogs showed nothing that I noticed.
May 12, 201610 yr Well, I'm pleased to hear that it works, but I think there must be some underlying problem that remains unfixed. I hope you manage to resolve it before it bites you.
May 12, 201610 yr Community Expert Logged into the console, can you write to it as the root user? Can you read from it, ls or df it? Have you tried formatting it again (since you can't write to it you have no data on it to lose) or running a filesystem check? Does it actually write any data to the disk or, as I suspect, is the 200 MB only going as far as the RAM cache? What does your syslog say? Any SMART errors? SMART extended test? Post diagnostics. so oddly enough 3rd reboot was the charm... haha. I can now write to it. The syslogs showed nothing that I noticed. Since you haven't posted diagnostics not much we can add. The "3rd reboot was the charm" sounds similar to voodoo programming though.
May 12, 201610 yr Author Logged into the console, can you write to it as the root user? Can you read from it, ls or df it? Have you tried formatting it again (since you can't write to it you have no data on it to lose) or running a filesystem check? Does it actually write any data to the disk or, as I suspect, is the 200 MB only going as far as the RAM cache? What does your syslog say? Any SMART errors? SMART extended test? Post diagnostics. so oddly enough 3rd reboot was the charm... haha. I can now write to it. The syslogs showed nothing that I noticed. Since you haven't posted diagnostics not much we can add. The "3rd reboot was the charm" sounds similar to voodoo programming though. the voodoo got it running though. My guess is something was left undone prior to rebooting (after format). By me trying to copy to it it left data corrupted or in a fuzzy state. After the reboot it might have stated the same. Honestly not sure, the machine cleanly rebooted all 3 times, and on the third time it worked fine.
Archived
This topic is now archived and is closed to further replies.