Nusrat Nuriyev
asked on
FAILURE - WRITE_DMA status=41<READY,ERROR> error=10<NID_NOT_FOUND> LBA=12078
Error while trying to check with fsck.
FAILURE - WRITE_DMA status=41<READY,ERROR&g t; error=10<NID_NOT_FOUND& gt; LBA=12078
Probably, it occurs even when system just works.
FreeBSD 8.3 on Virtual Machine.
There are a lot of such error occurs.
FAILURE - WRITE_DMA status=41<READY,ERROR&g
Probably, it occurs even when system just works.
FreeBSD 8.3 on Virtual Machine.
There are a lot of such error occurs.
Is there flash media under the hood? It is very unhappy when you read sector that was never written.
ASKER
There is no flash drive.
this error occurs when fsck for /dev/ad0s1a it's a virtual hard disk partition
this error occurs when fsck for /dev/ad0s1a it's a virtual hard disk partition
Go up tp [request attention] button and state your virtualisation technology and ask to add topic areas related.
ASKER
Also in my host computer /home/nn/.kde/share/dolphi nrc is for reading.
When I try to change it's mod it says : read only file system.
Also, now, when I try to boot to virtual machine it says "read-only file system" and throw me to the rescue mode to the /bin/sh intepreter.
Probably, these problems have same nature.
When I try to change it's mod it says : read only file system.
Also, now, when I try to boot to virtual machine it says "read-only file system" and throw me to the rescue mode to the /bin/sh intepreter.
Probably, these problems have same nature.
It means that your disk is faulty. Boot in single mode, run smartctl -a /dev/sda (where sda is your disk)
and seek replacement, then save as much data as possible.
and seek replacement, then save as much data as possible.
ASKER
gheist, here are some logs. how could I forcibly run fsck?
Is your verdict final?
smart.txt
systemd-fsck.txt
Is your verdict final?
smart.txt
systemd-fsck.txt
smartctl -T long
lets meet in 6h or so...
lets meet in 6h or so...
ASKER
okay, I will make test tomorrow, it will take 172 minutes.
SMART indicates 4h15min...
ASKER
I have started smartctl -t long /dev/sda
So, after a few hours. I should provide you smartctl -a , so you can look up the values and tell whether something wrong, do I get the workflow right?
So, after a few hours. I should provide you smartctl -a , so you can look up the values and tell whether something wrong, do I get the workflow right?
It is in last lines about diagnostic tests
either test succeeds or fails.
In first case we go fix filesystem (you can download fedora ISO to help with that
In later you go shopping...
either test succeeds or fails.
In first case we go fix filesystem (you can download fedora ISO to help with that
In later you go shopping...
ASKER
smartctl -a /dev/sda > /tmp/smartctl.txt
gheist, Could you explain the overall structure of smartctl report?
I see
Completed: read failure?
It doesn't sound very good.
Okay, seems to me shopping is unavoidable?
gheist, Could you explain the overall structure of smartctl report?
I see
Completed: read failure?
It doesn't sound very good.
Okay, seems to me shopping is unavoidable?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.