Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.
Original topic: 集群异常宕机使用tiup命令报错Error: mkdir /tmp/4767475860915002421: read-only file system
[TiDB Usage Environment] Production Environment / Testing / PoC
[TiDB Version]
[Reproduction Path] What operations were performed to encounter the issue
Physical machine storage was damaged, after repair, starting the machine using tiup reports an error: Error: mkdir /tmp/4767475860915002421: read-only file system
[Encountered Issue: Issue Phenomenon and Impact]
[Resource Configuration] Enter TiDB Dashboard - Cluster Info - Hosts and take a screenshot of this page
[Attachment: Screenshot/Log/Monitoring]
There is an issue with the disk. Check the status of the mounted disk. Use the mount command to see if the remarks indicate “ro”.
Are you looking at the data storage directory /dev/sdb1?
Can you manually create a directory under tmp to see if it can be created?
Tried it, can’t create, and the same error occurs.
Use df -h
to check which disk partition is read-only, then unmount and remount it to see if it resolves the issue.
Additionally, is this control machine independent? If it’s urgent, I suggest migrating tiup to a new machine to ensure the cluster is fine, and then fix the control machine later.
Check the folder permissions with ll /
:
drwxrwxrwt. 33 root root 4096 Sep 1 16:57 tmp
The disk is probably damaged.
There are no issues with permissions; I guess the disk on the IT side hasn’t been fixed.
Yes, just one central control machine. I’m planning to do that and move it to the new central control machine.
Is this also a disk failure?
Reporting “Read-only file system” usually indicates a disk problem.
Crashed, after mentioning last time that the SST file was corrupted and IT said there was a disk issue, it wasn’t fixed, and today everything went down 
Physical machine or virtual machine, what type of disk is it?
Disk issues or permissions
Your data disk is mounted in read-only mode. Check what is written in /etc/fstab? Or first unmount /dev/sdb1, then remount it and see what error it reports.
You might consider changing the machine; repairing it is too troublesome.
No permission for this disk, please check the disk.