A20 nand出现read only filesystem

静思心远 2017-03-06 03:35:27
打印信息:
manage.sh....
/opt_arma104/start/getIP.sh: line 2: can't create /opt_arma104/start/getIp.txt: Read-only file system
main QT----
[ 15.278524] EXT4-fs error (device nandd): ext4_lookup:1050: inode #119: comm a10ui: deleted inode referenced: 375
[ 15.290486] EXT4-fs error (device nandd): ext4_lookup:1050: inode #119: comm a10ui: deleted inode referenced: 375
[ 15.309862] EXT4-fs error (device nandd): ext4_lookup:1050: inode #119: comm a10ui: deleted inode referenced: 375
[ 15.339620] EXT4-fs error (device nandd): ext4_lookup:1050: inode #119: comm a10ui: deleted inode referenced: 375
[ 15.367372] EXT4-fs error (device nandd): ext4_lookup:1050: inode #119: comm a10ui: deleted inode referenced: 375
[ 15.379706] EXT4-fs error (device nandd): ext4_lookup:1050: inode #119: comm a10ui: deleted inode referenced: 375
[ 15.391484] EXT4-fs error (device nandd): ext4_lookup:1050: inode #119: comm a10ui: deleted inode referenced: 375
[ 15.403174] EXT4-fs error (device nandd): ext4_lookup:1050: inode #119: comm a10ui: deleted inode referenced: 375
[ 15.419868] EXT4-fs error (device nandd): ext4_lookup:1050: inode #119: comm a10ui: deleted inode referenced: 375
[ 15.432238] EXT4-fs error (device nandd): ext4_lookup:1050: inode #119: comm a10ui: deleted inode referenced: 375
[ 15.443966] EXT4-fs error (device nandd): ext4_lookup:1050: inode #119: comm a10ui: deleted inode referenced: 375
[ 15.455645] EXT4-fs error (device nandd): ext4_lookup:1050: inode #119: comm a10ui: deleted inode referenced: 375
QVNCServer created on port 5900
[ 16.709996] EXT4-fs error (device nandd): ext4_lookup:1050: inode #355: comm a10ui: deleted inode referenced: 372
[ 16.722559] EXT4-fs error (device nandd): ext4_lookup:1050: inode #355: comm a10ui: deleted inode referenced: 372
/opt_arma104/start/getIP.sh: line 2: can't create /opt_arma104/start/getIp.txt: Read-only file system
/opt_arma104/start/ipstatus.sh: line 2: can't create /opt_arma104/start/ipstatus.txt: Read-only file system
this is parent_progress()
this is child_progress()
UdpNetwork error
有大牛知道如何解 Read-only file system?
...全文
951 5 打赏 收藏 转发到动态 举报
写回复
用AI写文章
5 条回复
切换为时间正序
请发表友善的回复…
发表回复
qq_23437717 2017-08-21
  • 打赏
  • 举报
回复
遇到一次类似问题,A20,机器启动什么的都正常,段时间后客户反映系统无限重启,抓出log,提示 Read-only file system,先去检查是否开机时文件系统权限是否正常,一切正常,看来是此权限被更改了,查资料得知,Linux内核有这样一个机制:当你对我的分区读写出现错误时,我会提供三种错误处理机制:a,忽视;b,重新挂载为只读;c,好像是oops. 查看源代码,发现它的默认处理机制是配置为b,我把它改为a,类似问题没在出现过过。但究其原因,是对分区的读写出了问题,我做的只是更改了它错误处理机制。 希望对你有帮助。 这个具体是改什么地方呢,我现在也遇到了同样的问题
zs_2016 2017-04-05
  • 打赏
  • 举报
回复
遇到一次类似问题,A20,机器启动什么的都正常,段时间后客户反映系统无限重启,抓出log,提示 Read-only file system,先去检查是否开机时文件系统权限是否正常,一切正常,看来是此权限被更改了,查资料得知,Linux内核有这样一个机制:当你对我的分区读写出现错误时,我会提供三种错误处理机制:a,忽视;b,重新挂载为只读;c,好像是oops. 查看源代码,发现它的默认处理机制是配置为b,我把它改为a,类似问题没在出现过过。但究其原因,是对分区的读写出了问题,我做的只是更改了它错误处理机制。 希望对你有帮助。
静思心远 2017-03-15
  • 打赏
  • 举报
回复
目前推测是 nand flash问题,但是不知道问题出在哪里了
91program 2017-03-07
  • 打赏
  • 举报
回复
看 LOG 应该是 Linux 相关的吧,给你移动到 Linux 相关的论坛。
幽饮烛 2017-03-07
  • 打赏
  • 举报
回复
这看起来像是硬盘分区的文件系统出问题了? 用 root 执行 fsck 检查一下分区

1,317

社区成员

发帖
与我相关
我的任务
社区描述
主要是开发驱动技术
社区管理员
  • 驱动程序开发区社区
加入社区
  • 近7日
  • 近30日
  • 至今
社区公告
暂无公告

试试用AI创作助手写篇文章吧