Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

One of the Cache SSD shown as SpinDown but log spamming IO Error?

Featured Replies

During the 4 years of running this server, I've never seen it once spin down on the Cache SSD until a while back, but I didn't put too much thought into it until today when I open up the Logs, it's being spammed with IO Error on the SSD that's shown as Spindown, and pressing the Dot doesn't seems to wake it up either.

During this Period, the Entire Server remained functional on every aspect besides Parity I suppose (Even tho UnRAID didn't show the RAID 1 being broken, but running SCRUB indicates that it's all errors after the reboot)

Tho despite the graceful Shutdown after I found out about the I/O Error, both Docker.img and VM seem to be completely corrupted (And also seems to be the only file that was corrupted? All the other Docker containers that were running in the cache seem to be running just fine after I rebuild the docker.img)

After reboot, besides the CRC Error have jump to 20 (hasn't changed since) and the broken docker.img, everything else seems to be running fine

The issue is mostly fixed, so I just wanna ask if anyone knows what could have happened from the log? And if possible, how to prevent it? Since the UnRAID never figures out the drive failed (Might not even be the drive even), it also never sends an Email to notify me about the problem.

Here's the Log File before the reboot and after the reboot

Thanks in advanced!

Before Reboot Diag.zip After Reboot Diag.zip

I would start by reseating the cable connecting this SSD and see if the errors stop.

  • Community Expert

The data before the reboot show that a pool device dropped offline, can't see the start of the problem, since it had already rotated, but this is typically a power/connection issue.

Since Unraid doesn't currently monitor pool devices, I recommend using the script here, so that you are notified if it happens again:

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-700582

  • Author
6 hours ago, WN1X said:

I would start by reseating the cable connecting this SSD and see if the errors stop.

Sadly I'm no where near the server atm but for now the CRC error is no longer increasing, stayed at 20 for the last few days.

  • Author
6 hours ago, JorgeB said:

The data before the reboot show that a pool device dropped offline, can't see the start of the problem, since it had already rotated, but this is typically a power/connection issue.

Since Unraid doesn't currently monitor pool devices, I recommend using the script here, so that you are notified if it happens again:

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-700582

Ya I believe it's the Samsung one that drop offline, tho I do randomly get an error with BTRFS Drive missing during the next reboot for some reason on the other pool drive. (Tho it seems to be there after the reboot so I'm not sure lol)

  • Author
6 hours ago, JorgeB said:

The data before the reboot show that a pool device dropped offline, can't see the start of the problem, since it had already rotated, but this is typically a power/connection issue.

Since Unraid doesn't currently monitor pool devices, I recommend using the script here, so that you are notified if it happens again:

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-700582

Also that's a post from 2018, It still can't show BTRFS Error? xD

  • Community Expert
10 hours ago, LunarstarPony said:

Also that's a post from 2018, It still can't show BTRFS Error?

I'm afraid not, I've been requesting for that to be added since 2016...

  • Author
18 hours ago, JorgeB said:

I'm afraid not, I've been requesting for that to be added since 2016...

oof, did you think a reformat is necessary in my case with this? Someone in the Discord said they wouldn't trust this Cache Pool anymore without a full format on the cache drives, SCRUB already indicate that nothiugn is wrong atm.

  • Community Expert

Since there wasn't any filesystem corruption and the scrub was done, I don't see the need for that.

  • Author
56 minutes ago, JorgeB said:

Since there wasn't any filesystem corruption and the scrub was done, I don't see the need for that.

Gotcha Thx! I'll try to move everything back then!

  • Author
1 hour ago, JorgeB said:

Since there wasn't any filesystem corruption and the scrub was done, I don't see the need for that.

BTW By chance did you know about a way of backup Docker.img and libverb just in case it corrupted again? During this whole thing, the only thing that is corrupt is these 2 files

  • Community Expert

Docker image can easily be recreated; libvirt should be backed up every time you add or change a VM, and you just need to copy the file.

  • Author
3 hours ago, JorgeB said:

Docker image can easily be recreated; libvirt should be backed up every time you add or change a VM, and you just need to copy the file.

Do I need to go into Maintance Mode or Disable VM or Docker before copy them?

  • Community Expert

It should be OK to copy with the VM service running, but if you can disable it first, it would be better.

  • Author
4 minutes ago, JorgeB said:

It should be OK to copy with the VM service running, but if you can disable it first, it would be better.

Gotcha Thx!

  • Author
4 hours ago, JorgeB said:

It should be OK to copy with the VM service running, but if you can disable it first, it would be better.

A just as things starting to cool down, It appears the Samsung Drive that was previously working has dropped completely

  • Author

Tho After booting up, I've noticed that It's trying to run Scrub on it, is there any reason to do so at this time since there's only one drive until I get a replacement?

It's also running at 200KiB/s and is estimate to finish in 500 hours lol

  • Community Expert

Post new diags please.

  • Community Expert

There was a call trace when btrfs deleted the pool device:

Aug 24 00:39:15 Lunar-UnRAID kernel: BTRFS info (device sdf1): balance: ended with status: 0

Aug 24 00:39:15 Lunar-UnRAID kernel: BTRFS info (device sdf1): device deleted: missing

Aug 24 00:39:16 Lunar-UnRAID kernel: BUG: unable to handle page fault for address: 000000040000000f

Aug 24 00:39:16 Lunar-UnRAID kernel: #PF: supervisor read access in kernel mode

Aug 24 00:39:16 Lunar-UnRAID kernel: #PF: error_code(0x0000) - not-present page

Aug 24 00:39:16 Lunar-UnRAID kernel: PGD 0 P4D 0

Aug 24 00:39:16 Lunar-UnRAID kernel: Oops: Oops: 0000 [#4] PREEMPT SMP NOPTI

Aug 24 00:39:16 Lunar-UnRAID kernel: CPU: 7 UID: 201 PID: 64366 Comm: P[proc] Tainted: P D O 6.12.24-Unraid #1

Aug 24 00:39:16 Lunar-UnRAID kernel: Tainted: [P]=PROPRIETARY_MODULE, [D]=DIE, [O]=OOT_MODULE

Aug 24 00:39:16 Lunar-UnRAID kernel: Hardware name: System manufacturer System Product Name/TUF B450M-PLUS GAMING, BIOS 4622 09/29/2024

Aug 24 00:39:16 Lunar-UnRAID kernel: RIP: 0010:sysfs_kf_seq_show+0x22/0xc0

Aug 24 00:39:16 Lunar-UnRAID kernel: Code: 90 90 90 90 90 90 90 90 0f 1f 44 00 00 55 53 48 8b 77 70 48 89 fb 48 8b 06 48 8b 40 08 4c 8b 40 68 49 8b 68 28 48 85 ed 74 04 <48> 8b 6d 08 48 83 7d 00 00 75 09 0f 0b b8 ea ff ff ff eb 7c 48 8b

Aug 24 00:39:16 Lunar-UnRAID kernel: RSP: 0018:ffffc9000aba7de0 EFLAGS: 00010202

Aug 24 00:39:16 Lunar-UnRAID kernel: RAX: ffff88817d438ee0 RBX: ffff88824b396f00 RCX: 0000000000000001

Aug 24 00:39:16 Lunar-UnRAID kernel: RDX: ffff8882099149c0 RSI: ffff8882099149c0 RDI: ffff88824b396f00

Aug 24 00:39:16 Lunar-UnRAID kernel: RBP: 0000000400000007 R08: ffff8881079841d0 R09: 00000000ffffffff

Aug 24 00:39:16 Lunar-UnRAID kernel: R10: 0000000000000000 R11: 0000000000000078 R12: ffffc9000aba7e88

Aug 24 00:39:16 Lunar-UnRAID kernel: R13: ffffc9000aba7f08 R14: ffff88824b396f00 R15: 0000000000000078

Aug 24 00:39:16 Lunar-UnRAID kernel: FS: 000014f9d6ffe6c0(0000) GS:ffff88880edc0000(0000) knlGS:0000000000000000

Aug 24 00:39:16 Lunar-UnRAID kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

Aug 24 00:39:16 Lunar-UnRAID kernel: CR2: 000000040000000f CR3: 0000000154678000 CR4: 0000000000350ef0

Aug 24 00:39:16 Lunar-UnRAID kernel: Call Trace:

Aug 24 00:39:16 Lunar-UnRAID kernel: <TASK>

Aug 24 00:39:16 Lunar-UnRAID kernel: seq_read_iter+0x16e/0x350

Aug 24 00:39:16 Lunar-UnRAID kernel: vfs_read+0x12e/0x1c0

Aug 24 00:39:16 Lunar-UnRAID kernel: ksys_read+0x78/0xc0

Aug 24 00:39:16 Lunar-UnRAID kernel: do_syscall_64+0x68/0xe0

Aug 24 00:39:16 Lunar-UnRAID kernel: entry_SYSCALL_64_after_hwframe+0x76/0x7e

Aug 24 00:39:16 Lunar-UnRAID kernel: RIP: 0033:0x14f9fe2a49ee

Aug 24 00:39:16 Lunar-UnRAID kernel: Code: 08 0f 85 f5 4b ff ff 49 89 fb 48 89 f0 48 89 d7 48 89 ce 4c 89 c2 4d 89 ca 4c 8b 44 24 08 4c 8b 4c 24 10 4c 89 5c 24 08 0f 05 <c3> 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 80 00 00 00 00 48 83 ec 08

Aug 24 00:39:16 Lunar-UnRAID kernel: RSP: 002b:000014f9d6ff6978 EFLAGS: 00000246 ORIG_RAX: 0000000000000000

Aug 24 00:39:16 Lunar-UnRAID kernel: RAX: ffffffffffffffda RBX: 000014f9d6ffe6c0 RCX: 000014f9fe2a49ee

Aug 24 00:39:16 Lunar-UnRAID kernel: RDX: 0000000000000078 RSI: 000014f9d6ff69f0 RDI: 00000000000001fb

Aug 24 00:39:16 Lunar-UnRAID kernel: RBP: 000014f9d6ff6ab0 R08: 0000000000000000 R09: 0000000000000000

Aug 24 00:39:16 Lunar-UnRAID kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 000014f9d6ff69f0

Aug 24 00:39:16 Lunar-UnRAID kernel: R13: 00005612e16daba3 R14: 00005612dd04efb0 R15: 00005612e16dab90

Aug 24 00:39:16 Lunar-UnRAID kernel: </TASK>

Aug 24 00:39:16 Lunar-UnRAID kernel: Modules linked in: wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha udp_diag macvlan xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle iptable_mangle vhost_net tun vhost vhost_iotlb tap veth nf_conntrack_netlink xt_nat xt_tcpudp xt_conntrack xt_MASQUERADE nfnetlink xfrm_user xfrm_algo ip6table_nat iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype nvidia_uvm(PO) md_mod zfs(PO) spl(O) ntfs3 tcp_diag inet_diag it87(O) hwmon_vid ip6table_filter ip6_tables iptable_filter ip_tables x_tables af_packet cfg80211 rfkill 8021q garp mrp bridge stp llc bonding tls nvidia_drm(PO) nvidia_modeset(PO) edac_mce_amd edac_core intel_rapl_common iosf_mbi kvm_amd nvidia(PO) kvm drm_ttm_helper ttm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel video sha512_ssse3 sha256_ssse3 sha1_ssse3 drm_kms_helper aesni_intel crypto_simd wmi_bmof drm cryptd rapl joydev mpt3sas backlight i2c_piix4 agpgart i2c_smbus

Aug 24 00:39:16 Lunar-UnRAID kernel: r8169 input_leds k10temp ccp sr_mod i2c_core cdrom raid_class tpm_crb scsi_transport_sas ahci realtek tpm_tis libahci led_class tpm_tis_core wmi tpm libaescfb ecdh_generic ecc button

Aug 24 00:39:16 Lunar-UnRAID kernel: CR2: 000000040000000f

Aug 24 00:39:16 Lunar-UnRAID kernel: ---[ end trace 0000000000000000 ]---

Aug 24 00:39:16 Lunar-UnRAID kernel: RIP: 0010:scsi_block_when_processing_errors+0x24/0xc0

Aug 24 00:39:16 Lunar-UnRAID kernel: Code: 90 90 90 90 90 90 0f 1f 44 00 00 55 53 48 83 ec 30 65 48 8b 1c 25 28 00 00 00 48 89 5c 24 28 48 89 fb e8 6f 96 34 00 48 8b 13 <8b> 82 38 02 00 00 83 e8 05 83 f8 02 76 09 f6 82 f8 01 00 00 10 74

Aug 24 00:39:16 Lunar-UnRAID kernel: RSP: 0018:ffffc90000d97cc8 EFLAGS: 00010246

Aug 24 00:39:16 Lunar-UnRAID kernel: RAX: 0000000000000000 RBX: ffff888107a38000 RCX: 0000000000000000

Aug 24 00:39:16 Lunar-UnRAID kernel: RDX: 0000000000000000 RSI: ffffc90000d97d98 RDI: ffff888107a38000

Aug 24 00:39:16 Lunar-UnRAID kernel: RBP: ffffc90000d97d10 R08: ffffc90000d97d98 R09: 0000000000000002

Aug 24 00:39:16 Lunar-UnRAID kernel: R10: 0000000000000000 R11: 000000000000024c R12: ffff888107a38000

Aug 24 00:39:16 Lunar-UnRAID kernel: R13: 0000000000000000 R14: ffffc90000d97d18 R15: ffff888107aa9900

Aug 24 00:39:16 Lunar-UnRAID kernel: FS: 000014f9d6ffe6c0(0000) GS:ffff88880edc0000(0000) knlGS:0000000000000000

Aug 24 00:39:16 Lunar-UnRAID kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

Aug 24 00:39:16 Lunar-UnRAID kernel: CR2: 000000040000000f CR3: 0000000154678000 CR4: 0000000000350ef0

You can try rebooting and running another scrub, but if it crashes again, it would be better to backup and reformat the pool.

  • Author
2 hours ago, JorgeB said:

There was a call trace when btrfs deleted the pool device:

Aug 24 00:39:15 Lunar-UnRAID kernel: BTRFS info (device sdf1): balance: ended with status: 0

Aug 24 00:39:15 Lunar-UnRAID kernel: BTRFS info (device sdf1): device deleted: missing

Aug 24 00:39:16 Lunar-UnRAID kernel: BUG: unable to handle page fault for address: 000000040000000f

Aug 24 00:39:16 Lunar-UnRAID kernel: #PF: supervisor read access in kernel mode

Aug 24 00:39:16 Lunar-UnRAID kernel: #PF: error_code(0x0000) - not-present page

Aug 24 00:39:16 Lunar-UnRAID kernel: PGD 0 P4D 0

Aug 24 00:39:16 Lunar-UnRAID kernel: Oops: Oops: 0000 [#4] PREEMPT SMP NOPTI

Aug 24 00:39:16 Lunar-UnRAID kernel: CPU: 7 UID: 201 PID: 64366 Comm: P[proc] Tainted: P D O 6.12.24-Unraid #1

Aug 24 00:39:16 Lunar-UnRAID kernel: Tainted: [P]=PROPRIETARY_MODULE, [D]=DIE, [O]=OOT_MODULE

Aug 24 00:39:16 Lunar-UnRAID kernel: Hardware name: System manufacturer System Product Name/TUF B450M-PLUS GAMING, BIOS 4622 09/29/2024

Aug 24 00:39:16 Lunar-UnRAID kernel: RIP: 0010:sysfs_kf_seq_show+0x22/0xc0

Aug 24 00:39:16 Lunar-UnRAID kernel: Code: 90 90 90 90 90 90 90 90 0f 1f 44 00 00 55 53 48 8b 77 70 48 89 fb 48 8b 06 48 8b 40 08 4c 8b 40 68 49 8b 68 28 48 85 ed 74 04 <48> 8b 6d 08 48 83 7d 00 00 75 09 0f 0b b8 ea ff ff ff eb 7c 48 8b

Aug 24 00:39:16 Lunar-UnRAID kernel: RSP: 0018:ffffc9000aba7de0 EFLAGS: 00010202

Aug 24 00:39:16 Lunar-UnRAID kernel: RAX: ffff88817d438ee0 RBX: ffff88824b396f00 RCX: 0000000000000001

Aug 24 00:39:16 Lunar-UnRAID kernel: RDX: ffff8882099149c0 RSI: ffff8882099149c0 RDI: ffff88824b396f00

Aug 24 00:39:16 Lunar-UnRAID kernel: RBP: 0000000400000007 R08: ffff8881079841d0 R09: 00000000ffffffff

Aug 24 00:39:16 Lunar-UnRAID kernel: R10: 0000000000000000 R11: 0000000000000078 R12: ffffc9000aba7e88

Aug 24 00:39:16 Lunar-UnRAID kernel: R13: ffffc9000aba7f08 R14: ffff88824b396f00 R15: 0000000000000078

Aug 24 00:39:16 Lunar-UnRAID kernel: FS: 000014f9d6ffe6c0(0000) GS:ffff88880edc0000(0000) knlGS:0000000000000000

Aug 24 00:39:16 Lunar-UnRAID kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

Aug 24 00:39:16 Lunar-UnRAID kernel: CR2: 000000040000000f CR3: 0000000154678000 CR4: 0000000000350ef0

Aug 24 00:39:16 Lunar-UnRAID kernel: Call Trace:

Aug 24 00:39:16 Lunar-UnRAID kernel: <TASK>

Aug 24 00:39:16 Lunar-UnRAID kernel: seq_read_iter+0x16e/0x350

Aug 24 00:39:16 Lunar-UnRAID kernel: vfs_read+0x12e/0x1c0

Aug 24 00:39:16 Lunar-UnRAID kernel: ksys_read+0x78/0xc0

Aug 24 00:39:16 Lunar-UnRAID kernel: do_syscall_64+0x68/0xe0

Aug 24 00:39:16 Lunar-UnRAID kernel: entry_SYSCALL_64_after_hwframe+0x76/0x7e

Aug 24 00:39:16 Lunar-UnRAID kernel: RIP: 0033:0x14f9fe2a49ee

Aug 24 00:39:16 Lunar-UnRAID kernel: Code: 08 0f 85 f5 4b ff ff 49 89 fb 48 89 f0 48 89 d7 48 89 ce 4c 89 c2 4d 89 ca 4c 8b 44 24 08 4c 8b 4c 24 10 4c 89 5c 24 08 0f 05 <c3> 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 80 00 00 00 00 48 83 ec 08

Aug 24 00:39:16 Lunar-UnRAID kernel: RSP: 002b:000014f9d6ff6978 EFLAGS: 00000246 ORIG_RAX: 0000000000000000

Aug 24 00:39:16 Lunar-UnRAID kernel: RAX: ffffffffffffffda RBX: 000014f9d6ffe6c0 RCX: 000014f9fe2a49ee

Aug 24 00:39:16 Lunar-UnRAID kernel: RDX: 0000000000000078 RSI: 000014f9d6ff69f0 RDI: 00000000000001fb

Aug 24 00:39:16 Lunar-UnRAID kernel: RBP: 000014f9d6ff6ab0 R08: 0000000000000000 R09: 0000000000000000

Aug 24 00:39:16 Lunar-UnRAID kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 000014f9d6ff69f0

Aug 24 00:39:16 Lunar-UnRAID kernel: R13: 00005612e16daba3 R14: 00005612dd04efb0 R15: 00005612e16dab90

Aug 24 00:39:16 Lunar-UnRAID kernel: </TASK>

Aug 24 00:39:16 Lunar-UnRAID kernel: Modules linked in: wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha udp_diag macvlan xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle iptable_mangle vhost_net tun vhost vhost_iotlb tap veth nf_conntrack_netlink xt_nat xt_tcpudp xt_conntrack xt_MASQUERADE nfnetlink xfrm_user xfrm_algo ip6table_nat iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype nvidia_uvm(PO) md_mod zfs(PO) spl(O) ntfs3 tcp_diag inet_diag it87(O) hwmon_vid ip6table_filter ip6_tables iptable_filter ip_tables x_tables af_packet cfg80211 rfkill 8021q garp mrp bridge stp llc bonding tls nvidia_drm(PO) nvidia_modeset(PO) edac_mce_amd edac_core intel_rapl_common iosf_mbi kvm_amd nvidia(PO) kvm drm_ttm_helper ttm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel video sha512_ssse3 sha256_ssse3 sha1_ssse3 drm_kms_helper aesni_intel crypto_simd wmi_bmof drm cryptd rapl joydev mpt3sas backlight i2c_piix4 agpgart i2c_smbus

Aug 24 00:39:16 Lunar-UnRAID kernel: r8169 input_leds k10temp ccp sr_mod i2c_core cdrom raid_class tpm_crb scsi_transport_sas ahci realtek tpm_tis libahci led_class tpm_tis_core wmi tpm libaescfb ecdh_generic ecc button

Aug 24 00:39:16 Lunar-UnRAID kernel: CR2: 000000040000000f

Aug 24 00:39:16 Lunar-UnRAID kernel: ---[ end trace 0000000000000000 ]---

Aug 24 00:39:16 Lunar-UnRAID kernel: RIP: 0010:scsi_block_when_processing_errors+0x24/0xc0

Aug 24 00:39:16 Lunar-UnRAID kernel: Code: 90 90 90 90 90 90 0f 1f 44 00 00 55 53 48 83 ec 30 65 48 8b 1c 25 28 00 00 00 48 89 5c 24 28 48 89 fb e8 6f 96 34 00 48 8b 13 <8b> 82 38 02 00 00 83 e8 05 83 f8 02 76 09 f6 82 f8 01 00 00 10 74

Aug 24 00:39:16 Lunar-UnRAID kernel: RSP: 0018:ffffc90000d97cc8 EFLAGS: 00010246

Aug 24 00:39:16 Lunar-UnRAID kernel: RAX: 0000000000000000 RBX: ffff888107a38000 RCX: 0000000000000000

Aug 24 00:39:16 Lunar-UnRAID kernel: RDX: 0000000000000000 RSI: ffffc90000d97d98 RDI: ffff888107a38000

Aug 24 00:39:16 Lunar-UnRAID kernel: RBP: ffffc90000d97d10 R08: ffffc90000d97d98 R09: 0000000000000002

Aug 24 00:39:16 Lunar-UnRAID kernel: R10: 0000000000000000 R11: 000000000000024c R12: ffff888107a38000

Aug 24 00:39:16 Lunar-UnRAID kernel: R13: 0000000000000000 R14: ffffc90000d97d18 R15: ffff888107aa9900

Aug 24 00:39:16 Lunar-UnRAID kernel: FS: 000014f9d6ffe6c0(0000) GS:ffff88880edc0000(0000) knlGS:0000000000000000

Aug 24 00:39:16 Lunar-UnRAID kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

Aug 24 00:39:16 Lunar-UnRAID kernel: CR2: 000000040000000f CR3: 0000000154678000 CR4: 0000000000350ef0

You can try rebooting and running another scrub, but if it crashes again, it would be better to backup and reformat the pool.

No It's not crashing rn I even try to look BIOS, even BIOS doesn't seems to be detecting the Samsung Drive anymore. That drive is just like Gone xD

Edited by LunarstarPony

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.