我是 Ubuntu 的新手。-R
我知道我可以通过以下选项在只读模式下使用 vim 打开文件:
vim -R <filename> //Gives warning if I try to write
但是,如果我用 nano 做同样的事情,我可以自由地编写文件:
nano -R <filename> //I can still write
我究竟做错了什么?如何使用 nano 以只读模式打开文件?
我是 Ubuntu 的新手。-R
我知道我可以通过以下选项在只读模式下使用 vim 打开文件:
vim -R <filename> //Gives warning if I try to write
但是,如果我用 nano 做同样的事情,我可以自由地编写文件:
nano -R <filename> //I can still write
我究竟做错了什么?如何使用 nano 以只读模式打开文件?
我有一个在 Windows 管理员运行的远程位置的 Ubuntu 18.04 VM 上运行的无头 Odoo 服务器。我的 / 处于只读状态,因此触摸 /forcefsck 只是回复无法触摸...:只读文件系统。
是否有任何我可以在 reboot 或 shutdown -r 命令调用的重启参数将 forcefsck 添加到重启中?或任何其他方式让我的系统备份和运行正常?
谢谢你的时间
我想配置我的 docker 守护进程。为此,我必须修改 daemon.json 文件,但不幸的是,它位于只读挂载的文件系统上;
root@shinwey:/snap/docker/current/config# ls -ltr
total 1
-rw-r--r-- 1 root root 72 Jun 8 22:18 daemon.json
root@shinwey:/snap/docker/current/config# touch daemon.json
touch: cannot touch 'daemon.json': Read-only file system
root@shinwey:/snap/docker/current/config# df .
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/loop3 128896 128896 0 100% /snap/docker/471
我尝试使用“snap get docker”,因为该命令处理配置,但没有成功;
root@shinwey:/snap/docker/current/config# snap get docker
error: snap "docker" has no configuration
是否有任何特定的“快照”命令来更新应用程序配置?
任何帮助将不胜感激
每当我尝试启动 Ubuntu 时,我都会收到Intrafms
提示。我发现我可以使用 修复它
fsck /dev/sda7
,对所有故障排除提示说“是”,然后在完成后使用exit
. 大多数情况下,这往往会让我进入 Ubuntu。但是有时我会收到多条错误消息,说 {file} 不可写,请联系您的管理员了解详细信息,当我尝试启动 Discord 时(Discord 已成为我的文件系统程序的“金丝雀”,因为它喜欢编写临时目录)终端回应说它无法创建必要的目录,因为 /dev/sda7 是只读的。
intrafms
提示,/dev/sda7 contains a filesystem with errors. preforming check /dev/sda7 |=========> | 25% complete
然后当它完成检查时,它告诉我 /de/sda7 需要手动 fsck。然后我继续,就好像我正在启动进入正常模式一样。然后我遇到了一个典型的恢复模式屏幕,它经常告诉我我的文件系统是只读的。幸运的是,我可以使用恢复菜单中的检查文件系统工具以读/写方式挂载 /dev/sda7。然后我继续启动,但是当我重新启动以获取完整的图形驱动程序时,我又回到了开始的地方
Model: TOSHIBA MQ04ABF100 (JU001C)
Size: 1.0 TB (1,000,204,886,016 bytes)
Partitioning: GUID Partition Table
Serial Number: 6827CUSFT
Assessment: Disk is OK, 4264 bad sectors (35° C / 95° F)
它还告诉我 /dev/sda7 正在使用ext4 (Version 1.0)
,并且我还有一个未使用的 225GB 分区 (/dev/sda6)。
当我尝试新的修复或获取新的重要信息时,我会更新这个问题。
编辑 1:即使其他程序正在运行,我也会反复收到以下通知:
Configuration file "/home/asher/.config/kio_httprc" not writable.
Please contact your system administrator.
Configuration file "/home/potatoes/.config/kded5rc" not writable.
Please contact your system administrator.
我还做了拼写和语法检查
编辑 2:在正常的 Ubuntu 中一段时间后,文件系统恢复为只读。我不知道为什么会这样。
编辑 3:
这是输出 grep -i FPDMA /var/log/syslog*
Binary file /var/log/syslog matches
/var/log/syslog.1:Nov 22 11:22:37 asher-HP-Pavilion-x360-Convertible-14-ba1xx kernel: [33451.806034] ata3.00: failed command: READ FPDMA QUEUED
/var/log/syslog.1:Nov 22 11:22:37 asher-HP-Pavilion-x360-Convertible-14-ba1xx kernel: [33451.806059] ata3.00: failed command: READ FPDMA QUEUED
/var/log/syslog.1:Nov 22 11:22:37 asher-HP-Pavilion-x360-Convertible-14-ba1xx kernel: [33451.806079] ata3.00: failed command: READ FPDMA QUEUED
/var/log/syslog.1:Nov 22 16:33:43 asher-HP-Pavilion-x360-Convertible-14-ba1xx kernel: [50291.446008] ata3.00: failed command: READ FPDMA QUEUED
/var/log/syslog.1:Nov 22 16:33:49 asher-HP-Pavilion-x360-Convertible-14-ba1xx kernel: [50297.493682] ata3.00: failed command: READ FPDMA QUEUED
/var/log/syslog.1:Nov 22 16:33:50 asher-HP-Pavilion-x360-Convertible-14-ba1xx kernel: [50297.885180] ata3.00: failed command: READ FPDMA QUEUED
/var/log/syslog.1:Nov 22 17:23:44 asher-HP-Pavilion-x360-Convertible-14-ba1xx kernel: [53291.812459] ata3.00: failed command: READ FPDMA QUEUED
/var/log/syslog.1:Nov 22 17:23:44 asher-HP-Pavilion-x360-Convertible-14-ba1xx kernel: [53291.812483] ata3.00: failed command: READ FPDMA QUEUED
/var/log/syslog.1:Nov 22 17:23:44 asher-HP-Pavilion-x360-Convertible-14-ba1xx kernel: [53291.812503] ata3.00: failed command: READ FPDMA QUEUED
/var/log/syslog.1:Nov 22 17:23:44 asher-HP-Pavilion-x360-Convertible-14-ba1xx kernel: [53291.812516] ata3.00: failed command: READ FPDMA QUEUED
/var/log/syslog.1:Nov 22 17:23:44 asher-HP-Pavilion-x360-Convertible-14-ba1xx kernel: [53291.812534] ata3.00: failed command: READ FPDMA QUEUED
/var/log/syslog.1:Nov 22 17:39:42 asher-HP-Pavilion-x360-Convertible-14-ba1xx kernel: [54250.146483] ata3.00: failed command: READ FPDMA QUEUED
grep: /var/log/syslog.1: Input/output error
编辑 4:建议有效,但我会在 SMART 测试中留下一条临别信息:
Overall Assessment: Disk is OK, 4663 bad sectors
感谢您的帮助!
更新:对于任何有类似问题的人,请阅读解决方案的评论
在我的情况下,我有一个双引导系统和一些分布在 3 个 HDD 上的分区。它们都在启动时自动安装在我的 KDE 上,我从来没有遇到过在它们之间删除、创建或传输文件的任何问题,但是突然间我的写权限被拒绝了。ls -l
考虑到我所有分区的输出仍然给我这个,这很奇怪:
alex@alex-ubuntu:/media/alex$ ls -l
total 148
drwxrwxrwx 1 alex alex 65536 Oct 12 18:14 Backup
drwxrwxrwx 1 alex alex 4096 Mar 30 2019 DCC68E14C68DEF58
drwxrwxrwx 1 alex alex 4096 Oct 12 18:14 Downloads
drwxrwxrwx 1 alex alex 4096 Oct 12 18:14 Games
drwxrwxrwx 1 alex alex 4096 Oct 12 18:14 Videos
drwxrwxrwx 1 alex alex 8192 Oct 12 19:11 Windows
甚至用于复制或创建文件的 sudo 命令都不再起作用:
alex@alex-ubuntu:/media/alex/Videos$ sudo touch test.txt
[sudo] password for alex:
touch: cannot touch 'test.txt': Read-only file system
alex@alex-ubuntu:/media/alex/Videos$
我做了一些研究,但我发现的所有类似情况都是用户没有完全许可或root
仍然拥有所有权的情况,所以它几乎就像使用chmod
或chown
解决问题一样简单。我完全不知道是什么原因造成的,尤其是考虑到我的外置硬盘在连接时仍然可以完美运行。
这是mount
输出:
alex@alex-ubuntu:~$ mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,noexec,relatime,size=2994076k,nr_inodes=748519,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=607456k,mode=755)
/dev/sdc5 on / type ext4 (rw,relatime,errors=remount-ro)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=28,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=434)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
/var/lib/snapd/snaps/core18_1885.snap on /snap/core18/1885 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/exercism_5.snap on /snap/exercism/5 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/core_9993.snap on /snap/core/9993 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/gtk-common-themes_1506.snap on /snap/gtk-common-themes/1506 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/gnome-3-28-1804_145.snap on /snap/gnome-3-28-1804/145 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/discord_115.snap on /snap/discord/115 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/heroku_3993.snap on /snap/heroku/3993 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/postman_127.snap on /snap/postman/127 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/snapd_9279.snap on /snap/snapd/9279 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/vlc_1700.snap on /snap/vlc/1700 type squashfs (ro,nodev,relatime,x-gdu.hide)
/dev/sdc7 on /home type ext4 (rw,relatime)
/var/lib/snapd/snaps/snapd_9607.snap on /snap/snapd/9607 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/core_10126.snap on /snap/core/10126 type squashfs (ro,nodev,relatime,x-gdu.hide)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=607452k,mode=700,uid=1000,gid=1000)
/dev/sda1 on /media/alex/Videos type fuseblk (ro,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096,uhelper=udisks2)
/dev/sdb2 on /media/alex/Downloads type fuseblk (ro,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096,uhelper=udisks2)
/dev/sdb1 on /media/alex/Backup type fuseblk (ro,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096,uhelper=udisks2)
/dev/sdc2 on /media/alex/DCC68E14C68DEF58 type fuseblk (ro,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096,uhelper=udisks2)
/dev/sdc1 on /media/alex/Windows type fuseblk (ro,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096,uhelper=udisks2)
/dev/sdc3 on /media/alex/Games type fuseblk (ro,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096,uhelper=udisks2)
/dev/fuse on /run/user/1000/doc type fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
我有一台装有新安装的 Ubuntu Budgie 20.04 的华硕笔记本电脑,安装在 dev/sdb2 上,这是一个 1TB Crucial M.2 SSD。
相当经常(大约 50% 的时间),在我登录并开始工作后不久,Ubuntu 会关闭所有打开的应用程序并冻结。这似乎是一个缓慢的过程,应用程序关闭,然后 Budgie DE 将停止,最后鼠标变得无响应。此时,我可以使用 CTRL + F2 访问登录屏幕,但是当我提供用户名时,它会抛出错误:
[ 844.940093] blk_update_request: I/O error, dev sdb, sector 1009020696 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
然后再次显示登录提示。如果我再次尝试登录,我会收到很多 systemd 警报:
[ 861.655386] systemd-journald[376]: Failed to write entry (22 items, 745 bytes), ignoring: Read-only file system
[ 861.655543] systemd-journald[376]: Failed to write entry (22 items, 756 bytes), ignoring: Read-only file system
[ 861.655835] systemd-journald[376]: Failed to write entry (22 items, 745 bytes), ignoring: Read-only file system
[ 861.656284] systemd-journald[376]: Failed to write entry (22 items, 756 bytes), ignoring: Read-only file system
[ 861.656532] systemd-journald[376]: Failed to write entry (22 items, 745 bytes), ignoring: Read-only file system
此时,我通过按住电源按钮强制关机,重新启动,系统通常可以正常工作以进行下次启动。
我一直在监视磁盘 SMART 测试,它始终显示 2 个坏块。我已经尝试完全格式化驱动器并重新安装操作系统,但没有成功。
我一直在搜索论坛并在谷歌上搜索错误消息,但没有成功。
这是硬件错误,我需要更换驱动器,还是可以修复一些软件?另外,我还在尝试学习 Ubuntu 系统,所以如果有人能解释错误的含义,那就太好了。提前致谢。
我在 Windows 10 的双启动中运行 Ubuntu 20.04。我的设置配置方式是有一个带有 Windows 和 Ubuntu 操作系统的 SSD 和一个包含我所有数据的第二个驱动器,例如下载和文档等。磁盘在 NTFS 方案下分区。
首先,我对简单地在启动时自动安装该驱动器感兴趣,我通过转到磁盘 > 选择驱动器 > 编辑安装选项 > 启动时安装来管理它。然而,几天后我发现自己无法编辑挂载磁盘中的任何文件。新建文件夹和粘贴选项是灰色的,我既不能保存任何新文件也不能编辑以前的文件。用户权限显示了属于“root”的文件,因此我无法更改任何内容。禁用自动挂载后,文件权限现在显示我的用户名而不是 root,但我仍然无法编辑任何内容。
我已经尝试了很多解决方案,甚至很多都成功了,但是几天后事情又回到了原来的状态,没有明显的原因。我真的很想知道这里有什么问题以及如何解决。
谢谢!
我已经在 Xubuntu 18.04 上安装了Lethe,以阻止用户按照我们如何在 Ubuntu 18.04 上安装 Lethe 所做的所有更改?
如何恢复正常开机和正常读写?
不卸载,而只是输入更新或其他添加。
我有一个操作系统,但我没有任何 GRUB。
我尝试修复 GRUB,但我唯一能得到的是带有此消息的最小 grub:
支持最小的 BASH 类行编辑。对于第一个单词,TAB 列出了可能的命令完成。任何其他选项卡列出可能的设备或文件完成。
如果重新启动开始但使用只读驱动器。
我怎样才能解锁这个?没有完整的 grub 还是只有最少的 grub?
这很常见,当我的文件权限更改为read-only
. 我立即重新启动我的电脑,这不会启动,所以我强行关闭电源,然后我输入fsck /dev/sda2
. 问题出在哪里?为什么这总是发生?电脑八个月了。
我很担心,因为我上次sudo fsck -f /dev/sda2
在 Live Ubuntu 中输入时,输出显示如下:
Pass 1: Checking inodes, blocks, and sizes
Inode 19411393 seems to contain garbage. Clear? yes
...
Inode 19412112 seems to contain garbage. Clear? yes
...
Pass 2: Checking directory structure
Entry 'Captura de pantalla de 2020-04-14 17-02-34.png' in /home/pasta/ImM-CM-!genes (19398749) has deleted/unused inode 19411936. Clear? yes
...
Entry 'bdcc59467787cae82ff54abaec1dd5497e4d0d' in /home/pasta/.cache/mesa_shader_cache/35 (19398823) has deleted/unused inode 19411992. Clear? yes
...
Pass 5: Checking group summary information
Block bitmap differences: -(625760--625791) ... -(500 OF THESE, MORE OR LESS) ... -(159426726--159426729)
Fix? yes
的输出dmesg
,引起了我的注意:
[ 39.721010] pcieport 0000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 39.721019] pcieport 0000:00:1c.5: AER: device [8086:9d15] error status/mask=00000001/00002000
[ 39.721024] pcieport 0000:00:1c.5: AER: [ 0] RxErr
...
[ 170.652599] blk_update_request: I/O error, dev sdb, sector 4096 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 170.652736] blk_update_request: I/O error, dev sdb, sector 4096 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 170.652744] Buffer I/O error on dev sdb1, logical block 256, async page read
sudo smartctl -a /dev/sda2
之后的输出sudo smartctl -t long /dev/sda2
:
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-5.3.0-46-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Device Model: TOSHIBA MQ04ABF100
Serial Number: X8JBP3K2T
LU WWN Device Id: 5 000039 8d268714d
Firmware Version: JU001J
User Capacity: 1.000.204.886.016 bytes [1,00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Form Factor: 2.5 inches
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: ACS-3 T13/2161-D revision 5
SATA Version is: SATA >3.2 (0x1ff), 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Tue Apr 14 22:33:42 2020 -04
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 120) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 172) minutes.
SCT capabilities: (0x003d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0
3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always - 1294
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 636
5 Reallocated_Sector_Ct 0x0033 100 100 050 Pre-fail Always - 0
7 Seek_Error_Rate 0x000b 100 095 050 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 100 100 050 Pre-fail Offline - 0
9 Power_On_Hours 0x0032 096 096 000 Old_age Always - 1743
10 Spin_Retry_Count 0x0033 112 100 030 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 451
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 1359
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 23
193 Load_Cycle_Count 0x0032 095 095 000 Old_age Always - 50104
194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 35 (Min/Max 13/45)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
220 Disk_Shift 0x0002 100 100 000 Old_age Always - 0
222 Loaded_Hours 0x0032 097 097 000 Old_age Always - 1533
223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 0
224 Load_Friction 0x0022 100 100 000 Old_age Always - 0
226 Load-in_Time 0x0026 100 100 000 Old_age Always - 264
240 Head_Flying_Hours 0x0001 100 100 001 Pre-fail Offline - 0
SMART Error Log Version: 1
ATA Error Count: 1
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 1 occurred at disk power-on lifetime: 1096 hours (45 days + 16 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 31 00 02 59 d7 a9
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
ea 00 00 00 00 00 a0 00 05:01:42.830 FLUSH CACHE EXT
61 58 30 38 f9 20 40 00 05:01:42.830 WRITE FPDMA QUEUED
61 08 80 08 f9 1b 40 00 05:01:42.829 WRITE FPDMA QUEUED
61 08 78 a0 b8 52 40 00 05:01:42.788 WRITE FPDMA QUEUED
61 30 70 58 0c 50 40 00 05:01:42.788 WRITE FPDMA QUEUED
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed without error 00% 1743 -
# 2 Extended offline Completed without error 00% 1728 -
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.