January 6, 20179 yr I was using unraid 6.2.4 Pro with 4 data drives, 1 cache and 1 parity drive. I was able to configure GPU passthrough for a Windows 10 VM with Steam games installed. Since this worked ok, I decided to get a dedicated SSD for that VM. So I stopped my array and powered down the server. My mobo (gigabyte ud3p 970) only has 6 Sata slots so I installed this PCIE Sata card I had laying around (http://www.nix.ru/autocatalog/controllers_Orient/Orient-S3132RAID-RTL-PCI-Ex1-SATA-II-300-2port-ext-2port-int-RAID_72173.html). I installed the SSD (sandisk 120 GB ssd) and powered everything up. I was pleasantly surprised to see that everything was recognized right away by Unraid. I assigned the drive to the array and unraid did it's thing. At this point there were no errors so, using SSH, told unraid to copy the VM vdisk to the new data disk. Everything went peachy. Once this was done, I modified the VM XML to reflect the new location of the Vdisk and started the VM. The VM started and ran for an unknown amount of time. When I checked the server before going to bed, there was a red arrow next to the new SSD and unraid had unmounted it. Is there a problem with the way I installed the new drive? Is the raid card the issue?
January 6, 20179 yr Author Relevant part from my log file: Jan 5 22:13:48 Tower sshd[31544]: Accepted password for root from 192.168.1.229 port 58393 ssh2 Jan 5 22:34:12 Tower kernel: vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem Jan 5 22:34:12 Tower kernel: vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem Jan 5 22:34:18 Tower kernel: ata2.00: disabled Jan 5 22:34:18 Tower kernel: sd 2:0:0:0: [sdb] Synchronizing SCSI cache Jan 5 22:34:18 Tower kernel: sd 2:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=0x04 driverbyte=0x00 Jan 5 22:34:18 Tower kernel: sd 2:0:0:0: [sdb] Stopping disk Jan 5 22:34:18 Tower kernel: sd 2:0:0:0: [sdb] Start/Stop Unit failed: Result: hostbyte=0x04 driverbyte=0x00 Jan 5 22:34:19 Tower kernel: device vnet0 entered promiscuous mode Jan 5 22:34:19 Tower kernel: br0: port 2(vnet0) entered forwarding state Jan 5 22:34:19 Tower kernel: br0: port 2(vnet0) entered forwarding state Jan 5 22:34:20 Tower kernel: vfio-pci 0000:03:00.0: enabling device (0000 -> 0003) Jan 5 22:34:22 Tower kernel: md: disk5 read error, sector=72 Jan 5 22:34:30 Tower kernel: kvm: zapping shadow pages for mmio generation wraparound Jan 5 22:34:30 Tower kernel: kvm: zapping shadow pages for mmio generation wraparound Jan 5 22:34:38 Tower kernel: md: disk5 write error, sector=72 Jan 5 22:48:16 Tower kernel: vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem Jan 5 22:48:16 Tower kernel: vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem Jan 5 22:49:27 Tower kernel: vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem Jan 5 22:49:27 Tower kernel: device vnet1 entered promiscuous mode Jan 5 22:49:27 Tower kernel: br0: port 3(vnet1) entered forwarding state Jan 5 22:49:27 Tower kernel: br0: port 3(vnet1) entered forwarding state Jan 5 22:49:29 Tower kernel: vfio_ecap_init: 0000:01:00.0 hiding ecap 0x1e@0x258 Jan 5 22:49:29 Tower kernel: vfio_ecap_init: 0000:01:00.0 hiding ecap 0x19@0x900 Jan 5 22:49:29 Tower kernel: vfio-pci 0000:00:14.2: enabling device (0000 -> 0002) Jan 5 22:49:31 Tower kernel: kvm: zapping shadow pages for mmio generation wraparound Jan 5 22:49:31 Tower kernel: vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem Jan 5 22:49:33 Tower kernel: kvm: zapping shadow pages for mmio generation wraparound Jan 5 22:49:37 Tower kernel: md: disk5 write error, sector=117220960 Jan 5 23:06:40 Tower emhttp: err: mdcmd: write: No such file or directory Jan 5 23:06:40 Tower kernel: mdcmd (51): spindown 5 Jan 5 23:06:40 Tower kernel: md: do_drive_cmd: lock_bdev error: -2 Jan 5 23:06:48 Tower emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/disk_log sdb Jan 6 00:36:13 Tower emhttp: err: mdcmd: write: No such file or directory Jan 6 00:36:13 Tower kernel: mdcmd (52): spindown 5 Jan 6 00:36:13 Tower kernel: md: do_drive_cmd: lock_bdev error: -2 Jan 6 00:36:41 Tower kernel: mdcmd (53): spinup 5 Jan 6 00:36:41 Tower kernel: md: do_drive_cmd: lock_bdev error: -2 Jan 6 00:36:45 Tower kernel: mdcmd (54): spinup 5 Jan 6 00:36:45 Tower kernel: md: do_drive_cmd: lock_bdev error: -2
January 6, 20179 yr Need the whole syslog (always!), the important part is before that. The key thing I see is that the drive associated with ata2.00 has been dropped, and you need to know why, and what happened to it. Could be a bad drive, but more likely an interface issue with it. Please see Need help? Read me first!, and attach the diagnostics zip.
January 7, 20179 yr Sorry, I was gone for much of the day. A few comments: * I had hoped you would include the Diagnostics. As of v6, we always want the diagnostics instead of the syslog alone, as it includes the syslog plus all SMART reports and a LOT of other useful diagnostic info. I'll do what I can from the syslog. * You have added a SATA controller card with SI3132 chipset, 2 SATA ports, which is fine for older drives, but because the SI3132 is now older technology, it's not a good fit for SSD's. For one thing, it limits I/O speed to 100Mb/s, plus it knows nothing about SSD's or trimming. I'd move the SSD to a motherboard port. I can't say that this is the cause of the SSD being suddenly dropped, because there's no direct clue evident in the syslog, but it's possible. I'd move only the very oldest drives to this card. * You have added the SSD to the array. I can't quickly point to the discussions about this, but as far as I know, it's not advisable currently, because a trim operation may possibly ruin parity. Hopefully, someone else will point to the posts about this, or you can try searching. On that SI3132 card, as far as I can tell, it did not recognize it as an SSD, which in itself is troubling. * The SSD appeared to be OK initially, and you were able to issue spin downs and spin ups to it, but when you added it the array and started the array, it wrote an MBR fine, but then reported a 'Buffer I/O error' on the SSD, not a good sign, but there doesn't appear to be further harm from that. It successfully cleared the drive, quite fast(!), then formatted it with XFS, then mounted it as Disk 5, with no apparent issues. Later it was spun down (spinning down an SSD just means putting it in standby, a lower power condition). * But here's the fatal part - about an hour and 10 minutes after spinning down, the kernel announces the drive is disabled! As an ATA device, there should have been exceptions reported, and attempts to raise it, reset it, but there's nothing. It's just a simple and sudden announcement that the drive is gone, with no explanation at all. I've never seen that happen before! You can ignore the subsequent read and write errors. I have no explanation for the loss of the drive, but I do strongly recommend reconnecting it to a motherboard SATA port. * You have IDE emulation turned on for 2 of your onboard SATA drives. When you next boot, go into the BIOS settings and look for the SATA mode, and change it to a native SATA mode, preferably AHCI if available, anything but IDE emulation mode. It should be slightly faster, and a little safer. You have 2 drives (WD6400AAKS and WD15EARS) attached to the last 2 ports, but they are being treated as IDE drives. Worse, as PATA drives, something is not being recognized correctly, so the kernel thinks they both are using old 40 wire IDE cables, and therefore slowed their top speed down to 33Mb/s! You of course don't have 40 wire IDE cables, but because it's configured to think they are IDE drives, it's confused. Make sure you change that BIOS setting!
January 7, 20179 yr Author Thanks for the detailed response Rob. I've attached the rest of the diagnostics. So say I want to remove the disk from the array and also move it to one of the ports on my motherboard (and thus switching another drive to the S3132). What is the most appropriate way of doing this? Close the array, unassign disk 5, powerdown, do the port switch, start the array again? So you say SSD should not be part of the array, can I leave it unassigned and still access it normally? tower-diagnostics-20170107-0932.zip
January 7, 20179 yr Community Expert Thanks for the detailed response Rob. I've attached the rest of the diagnostics. So say I want to remove the disk from the array and also move it to one of the ports on my motherboard (and thus switching another drive to the S3132). What is the most appropriate way of doing this? Close the array, unassign disk 5, powerdown, do the port switch, start the array again? So you say SSD should not be part of the array, can I leave it unassigned and still access it normally? It's not necessary to unassign the disk to switch the port, but if you want to remove it from the array then you will have to set a new configuration without the disk and rebuild parity. As for accessing normally, depends on what you mean by normally. You can use the Unassigned Devices plugin to access the SSD, but it will just be a single disk that you can't include in user shares, won't have parity protection, etc. You can share the single disk on the network, and your apps, etc. running on the server can also access it.
January 7, 20179 yr Author As for accessing normally, depends on what you mean by normally. You can use the Unassigned Devices plugin to access the SSD, but it will just be a single disk that you can't include in user shares, won't have parity protection, etc. You can share the single disk on the network, and your apps, etc. running on the server can also access it. I want to place the vdisk image on the SSD. Can I leave it unassigned and point the VM to the vdisk on the SSD? Parity protection is not that big of an issue since I already have backups of the vdisk and it is mainly used as a gaming machine.
January 7, 20179 yr Author So I am trying to remove the SSD from the array following these instructions: "How do I remove a hard disk that I do not plan on replacing? The basic method is to go to the Tools page and click New Config, then assign all the drives you want to keep. When you next start the array, it will rebuild parity. Obviously, it is vital that you know what your current drive assignments are, especially the Parity drive, so make notes or screen captures beforehand." When I get to the New Config page, I don't understand what I should do. I can only tick 3 boxes (parity, data and cache) and then apply or done. How do I specify which disks to keep?
January 7, 20179 yr Community Expert When I get to the New Config page, I don't understand what I should do. I can only tick 3 boxes (parity, data and cache) and then apply or done. How do I specify which disks to keep? Haven't done this recently, and I know there have been some recent changes so I don't know what it looks like. Have you tried turning on Help? There is a Help "toggle" at the top right. If you turn it on it will give help for most pages in the webUI. Post a screenshot.
January 7, 20179 yr Community Expert You can retain all assignments then click apply and done, back on the main page unassign the SSD and start array to begin the parity sync.
January 7, 20179 yr Author You can retain all assignments then click apply and done, back on the main page unassign the SSD and start array to begin the parity sync. Thanks, that did the trick. I will try putting the VM on the unassigned ssd. I can currently access my mounted disks at "/mnt/disk/", where are the unassigned disks in the Unraid file structure?
January 7, 20179 yr Author For the benefit of others with a similar skill level as mine: Make sure you have the Unassigned Disk plugin installed before checking the /mnt/disks/ directory....
January 7, 20179 yr Author There is definitely something wrong going on. I have switched the SSD for another drive (Disk 3) on the Sata card but now it is throwing millions of errors while building parity. Does that mean that the Sata card is toast? If yes, any suggestions for a suitable replacement? tower-diagnostics-20170107-1500.zip
January 7, 20179 yr Community Expert Same thing happened again, now with that disk, it got disabled without an apparent reason. I would replace that controller.
January 12, 20179 yr Author Ok, so I got a brand new syba sy-pex40039 controller and added the script from the forum to make sure unraid plays nice with it. But now it fails catastrophically when I try to launch the VM. Not too sure what to do now.... Here are my diagnostics... tower-diagnostics-20170111-20545418.zip
January 13, 20179 yr Author My problem persists it seems. Jan 12 19:13:38 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:14:08 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:14:38 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:15:08 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:15:38 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:16:08 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:16:38 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:17:08 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:17:38 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:18:08 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:18:39 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:19:09 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:19:39 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:20:09 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:20:39 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:21:09 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:21:39 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:22:09 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:22:39 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:23:09 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:23:39 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:24:09 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:24:40 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:25:10 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:25:40 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:26:10 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:26:40 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:27:10 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:27:40 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:28:10 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:28:40 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:29:10 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:29:40 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:30:10 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:30:40 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:31:11 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:31:41 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:32:11 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:32:41 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:33:11 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:33:41 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:34:11 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:34:41 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:35:11 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:35:41 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:36:11 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:36:41 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:37:12 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:37:42 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:38:12 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:38:42 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:39:12 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:39:42 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:40:12 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:40:42 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:41:12 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:41:42 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:42:12 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:42:42 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:43:12 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:43:43 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:44:13 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:44:43 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:45:13 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:45:43 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:46:13 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:46:43 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:47:13 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:47:43 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:48:13 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:48:43 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:49:13 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:49:44 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:50:14 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:50:44 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:51:14 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:51:44 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:52:14 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:52:44 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:53:14 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:53:44 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:54:14 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:54:44 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:55:14 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:55:44 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:56:15 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:56:45 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:57:15 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:57:45 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:58:15 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:58:45 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:59:15 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 19:59:45 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:00:15 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:00:45 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:01:15 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:01:45 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:02:16 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:02:46 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:03:16 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:03:46 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:04:16 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:04:46 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:05:16 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:05:46 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:06:16 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:06:46 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:07:16 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:07:46 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:08:16 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:08:47 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:09:17 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:09:47 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:10:17 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:10:47 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:11:17 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:11:47 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:12:17 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:12:47 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:13:17 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:13:47 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:14:17 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:14:48 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:15:18 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:15:48 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:16:18 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:16:48 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:17:18 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:17:48 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:18:18 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:18:48 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:19:18 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:19:48 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:20:18 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:20:48 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:21:19 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:21:49 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:22:19 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:22:49 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:23:19 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:23:49 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:24:19 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:24:49 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:25:19 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:25:49 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:26:19 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:26:49 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:27:20 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:27:50 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:28:20 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:28:50 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:29:20 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:29:50 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:30:20 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:30:50 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:31:20 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:31:50 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:32:20 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:32:50 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:33:20 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:33:51 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:34:21 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:34:51 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:35:21 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:35:51 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:36:21 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:36:51 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:37:21 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:37:51 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:38:21 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:38:51 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:39:21 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:39:52 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:40:22 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:40:52 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:41:22 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:41:52 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:42:22 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:42:52 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:43:22 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:43:52 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:44:22 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. Jan 12 20:44:52 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. .
January 13, 20179 yr Community Expert Jan 11 20:53:17 Tower kernel: XFS (sdh1): metadata I/O error: block 0x6fcc02c ("xlog_iodone") error 5 numblks 64 Jan 11 20:53:17 Tower kernel: XFS (sdh1): xfs_do_force_shutdown(0x2) called from line 1197 of file fs/xfs/xfs_log.c. Return address = 0xffffffff8128bb59 Jan 11 20:53:17 Tower kernel: XFS (sdh1): Log I/O Error Detected. Shutting down filesystem Jan 11 20:53:17 Tower kernel: XFS (sdh1): Please umount the filesystem and rectify the problem(s) Jan 11 20:53:17 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. You need to check file system on the Sandisk SSD which I'm guessing is an unassigned device, unmount it and on the console run: xfs_repair -v /dev/sdh1
January 14, 20179 yr Author Jan 11 20:53:17 Tower kernel: XFS (sdh1): metadata I/O error: block 0x6fcc02c ("xlog_iodone") error 5 numblks 64 Jan 11 20:53:17 Tower kernel: XFS (sdh1): xfs_do_force_shutdown(0x2) called from line 1197 of file fs/xfs/xfs_log.c. Return address = 0xffffffff8128bb59 Jan 11 20:53:17 Tower kernel: XFS (sdh1): Log I/O Error Detected. Shutting down filesystem Jan 11 20:53:17 Tower kernel: XFS (sdh1): Please umount the filesystem and rectify the problem(s) Jan 11 20:53:17 Tower kernel: XFS (sdh1): xfs_log_force: error -5 returned. You need to check file system on the Sandisk SSD which I'm guessing is an unassigned device, unmount it and on the console run: xfs_repair -v /dev/sdh1 Hmmm... When I try the above, it say /dev/sdh1: No such file or directory /dev/sdh1: No such file or directory fatal error -- couldn't initialize XFS library
January 14, 20179 yr Author Reboot, check that the disk is still sdh and try again. It had changed name to SDI. But now it says: ... found candidate secondary superblock... unable to verify superblock, continuing... ... Sorry, could not find valid secondary superblock Exiting now. Can I just reformat it?
January 14, 20179 yr Community Expert You can if there's no important data there, but make sure you didn't just forget the 1 at the end: xfs_repair -v /dev/sdi1
January 14, 20179 yr Author You can if there's no important data there, but make sure you didn't just forget the 1 at the end: xfs_repair -v /dev/sdi1 Sorry, this is all black magic to me... Here is what it says with the missing digit: xfs_repair -v /dev/sdi1 Phase 1 - find and verify superblock... - block cache size set to 1529832 entries Phase 2 - using internal log - zero log... zero_log: head block 6724 tail block 6720 ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this.
Archived
This topic is now archived and is closed to further replies.