April 19, 20215 yr hello. This morning we had couple power fails and for some reason my UPS didnt protect the server. After work I check the system and non of my vms are working. They were all located on Unassigned drive (Ultra M.2). Can not mount the drive and drive log says: Apr 19 17:45:06 Tower unassigned.devices: Adding disk '/dev/nvme0n1p1'... Apr 19 17:45:06 Tower unassigned.devices: Mount drive command: /sbin/mount -t xfs -o rw,noatime,nodiratime,discard '/dev/nvme0n1p1' '/mnt/disks/Samsung_SSD_970' Apr 19 17:45:06 Tower kernel: XFS (nvme0n1p1): Mounting V5 Filesystem Apr 19 17:45:06 Tower kernel: print_req_error: critical medium error, dev nvme0n1, sector 488502266 Apr 19 17:45:06 Tower kernel: print_req_error: critical medium error, dev nvme0n1, sector 488504266 Apr 19 17:45:06 Tower kernel: XFS (nvme0n1p1): xfs_do_force_shutdown(0x1) called from line 1270 of file fs/xfs/xfs_buf.c. Return address = 0000000089f929dd Apr 19 17:45:06 Tower kernel: XFS (nvme0n1p1): I/O Error Detected. Shutting down filesystem Apr 19 17:45:06 Tower kernel: XFS (nvme0n1p1): Please umount the filesystem and rectify the problem(s) Apr 19 17:45:06 Tower kernel: XFS (nvme0n1p1): metadata I/O error in "xlog_bwrite" at daddr 0x1d1df3ba len 8192 error 61 Apr 19 17:45:06 Tower kernel: XFS (nvme0n1p1): failed to locate log tail Apr 19 17:45:06 Tower kernel: XFS (nvme0n1p1): log mount/recovery failed: error -61 Apr 19 17:45:06 Tower kernel: XFS (nvme0n1p1): log mount failed Apr 19 17:45:06 Tower kernel: print_req_error: critical medium error, dev nvme0n1, sector 0 Apr 19 17:45:06 Tower unassigned.devices: Mount of '/dev/nvme0n1p1' failed: 'mount: /mnt/disks/Samsung_SSD_970: mount(2) system call failed: No data available. ' Is that drive fried and data lost ar anything could be done? Any help very appreciated. Thanks tower-diagnostics-20210419-1735.zip Edited April 29, 20215 yr by Tibbar [SOLVED]
April 20, 20215 yr Community Expert 8 hours ago, Tibbar said: Is that drive fried Looks like it is: SMART overall-health self-assessment test result: FAILED! - available spare has fallen below threshold - media has been placed in read only mode You can try mounting in read-only mode, if it works you can copy the data.
April 20, 20215 yr Author 13 hours ago, JorgeB said: You can try mounting in read-only mode, if it works you can copy the data. Thanks for reply. How do I mount it in read-only mode? It is Unassigned drive that was hosting my VM's. Thanks.
April 20, 20215 yr 10 minutes ago, Tibbar said: How do I mount it in read-only mode? Try something like cd ~ mkdir Samsung mount -t xfs -o ro /dev/nvme0n1p1 Samsung
April 20, 20215 yr Author 2 hours ago, John_M said: Try something like cd ~ mkdir Samsung mount -t xfs -o ro /dev/nvme0n1p1 Samsung Response I get is : mount: /root/Samsung: mount(2) system call failed: No data available.
April 24, 20215 yr Author On 4/21/2021 at 2:49 AM, JorgeB said: See if you can clone it with ddrescue. Big THANK YOU to @JorgeB. It worked like a charm.Was able to retrieve all the data. Linux 4.19.98-Unraid. Last login: Tue Apr 20 19:19:53 -0400 2021 on /dev/pts/0. root@Tower:~# ddrescue -f /dev/nvme0n1 /dev/sdo /boot/ddrescue.log GNU ddrescue 1.23 Press Ctrl-C to interrupt ipos: 500107 MB, non-trimmed: 0 B, current rate: 1099 MB/s opos: 500107 MB, non-scraped: 0 B, average rate: 113 MB/s non-tried: 0 B, bad-sector: 0 B, error rate: 0 B/s rescued: 500107 MB, bad areas: 0, run time: 1h 13m 19s pct rescued: 100.00%, read errors: 0, remaining time: n/a time since last successful read: n/a Finished root@Tower:~# Still don't know if that drive is completely dead or not. Again Thank You.
Archived
This topic is now archived and is closed to further replies.