hawihoney
-
Posts
3,513 -
Joined
-
Last visited
-
Days Won
7
hawihoney's Achievements
-
I try to avoid that - thats my reason to ask. Three arrays were affected during the power outtage. 1 array was working and does parity check currently. 2 arrays were spun-down completely. Parity check on them takes 35 hours each. I'm pretty sure that a spun-down array is save, but only the developer knows.
-
If the array is spun down after (in my case) 15 minutes, is it possible that it's content is not synced (cache written to disks and applied to parity)? We had a power outtage yesterday. I know that two DAS (Direct Attached Storage) boxes were spun down completely before this crash. Is it possible that parity is out of sync in that situation? I guess no, must be save. What do you think? Thanks.
-
[6.12.13] Unraid does format single-device pool as BTRFS, should be XFS
hawihoney commented on hawihoney's report in Stable Releases
Thanks worked. -
That's what I found out exactly. See above.
-
[6.12.13] Unraid does format single-device pool as BTRFS, should be XFS
hawihoney commented on hawihoney's report in Stable Releases
Why should an average user click on help if the text "Default file system format" is clear enough? But the problem is: It's labeled wrong, at least misleading. IMHO this label should be changed to "Default file system format (arrays)" or something like this. And if you consider a change. Why not add a second option "Default file system format (pools)" and preset it with btrfs? That would it make clear for anyone. -
[6.12.13] Unraid does format single-device pool as BTRFS, should be XFS
hawihoney commented on hawihoney's report in Stable Releases
Thanks. Please change the label (Default file system). It's confusing then. Didn't find it. Where should I set it? The pool or the individual pool device? I'm pretty sure that I looked before trusting the default setting. -
[6.12.13] Unraid does format single-device pool as BTRFS, should be XFS
hawihoney commented on hawihoney's report in Stable Releases
I double checked but could not find a way to set the file system of the pool. So I trusted the default setting (XFS). Something must have changed during the years, because my old pool has XFS (see image below). I suggest to change that wording - the label - to something more correct like "Default filesystem for array devices" !!! Time for a third reboot to change that. BTRFS is no option here ... Look at that temperature. The XFS pool is in use. The BTRFS pool is used as backup once a day and not in use otherwise. It's sleeping currently. -
This setting is default: New single-device pool gets formatted as BTRFS. Why? Is there a hidden setting somewhere else? Thanks.
-
With these settings in syslinux.cfg the second NVMe was missing completely. After removing this setting this NVMe is still not visible. Looking like an hardware error. I remember these kinds of errors years ago. I could solve that with Shutdown/Restart instead of Reboot. Next time I will try Shutdown/Restart again. ***EDIT*** Couldn't wait. Did a complete shutdown and did restart with the Powerknob on the Supermicro case. Bingo. NVMe2 is back again. I must remember this. Never do a reboot on my system, shutdown the system completely instead.
-
The interesting part is that this device was available after reboot for a short period of time. And after that it was gone silently. This combo was running happily for years with previous Unraid versions. Is this correct? I will reboot then and report. Thanks.
-
Yes. I always wanted both NVMe as a 2-device pool. But I don't trust BTRFS and ZFS seems way to complicated to me. So I replicate the first pool device to the second one mounted thru Unassigned Devices via User Scripts. With multi-Array support - whenever it will arrive - I will change that to a 2-device Unraid array.
-
My system has two NVMe attached to the motherboard. This combo worked throughout the latest releases without any problems. With the installation of 6.12.13 one of the two NVMe throws errors now: Aug 27 08:19:17 Tower unassigned.devices: Mounting partition 'nvme1n1p1' at mountpoint '/mnt/disks/NVMe2'... Aug 27 08:19:17 Tower unassigned.devices: Mount cmd: /sbin/mount -t 'xfs' -o rw,relatime,discard '/dev/nvme1n1p1' '/mnt/disks/NVMe2' Aug 27 08:19:17 Tower kernel: XFS (nvme1n1p1): Mounting V5 Filesystem Aug 27 08:19:17 Tower kernel: XFS (nvme1n1p1): Ending clean mount Aug 27 08:19:17 Tower unassigned.devices: Successfully mounted '/dev/nvme1n1p1' on '/mnt/disks/NVMe2'. Aug 27 08:19:21 Tower emhttpd: shcmd (197): /usr/local/sbin/mount_image '/mnt/pool_nvme/system/docker/' /var/lib/docker 10 Aug 27 08:19:24 Tower emhttpd: shcmd (214): /usr/local/sbin/mount_image '/mnt/pool_nvme/system/libvirt.img' /etc/libvirt 1 Aug 27 08:35:19 Tower emhttpd: spinning down /dev/nvme1n1 Aug 27 08:35:19 Tower emhttpd: sdspin /dev/nvme1n1 down: 25 Aug 27 12:34:49 Tower kernel: nvme nvme1: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0xffff Aug 27 12:34:49 Tower kernel: nvme nvme1: Does your device have a faulty power saving mode enabled? Aug 27 12:34:49 Tower kernel: nvme nvme1: Try "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off" and report a bug Aug 27 12:34:49 Tower kernel: nvme 0000:09:00.0: Unable to change power state from D3cold to D0, device inaccessible Aug 27 12:34:49 Tower kernel: nvme nvme1: Removing after probe failure status: -19 Aug 27 12:34:49 Tower kernel: nvme1n1: detected capacity change from 1953525168 to 0 Aug 27 13:48:39 Tower kernel: XFS (nvme1n1p1): metadata I/O error in "xfs_imap_to_bp+0x50/0x70 [xfs]" at daddr 0x3ae0bca0 len 32 error 5 Aug 27 13:48:39 Tower kernel: XFS (nvme1n1p1): metadata I/O error in "xfs_imap_to_bp+0x50/0x70 [xfs]" at daddr 0x3ae0bca0 len 32 error 5 Aug 27 13:48:39 Tower kernel: XFS (nvme1n1p1): metadata I/O error in "xfs_imap_to_bp+0x50/0x70 [xfs]" at daddr 0x3ae0bca0 len 32 error 5 Aug 27 13:48:39 Tower kernel: XFS (nvme1n1p1): metadata I/O error in "xfs_imap_to_bp+0x50/0x70 [xfs]" at daddr 0x3ae0bca0 len 32 error 5 Aug 27 13:48:39 Tower kernel: XFS (nvme1n1p1): metadata I/O error in "xfs_imap_to_bp+0x50/0x70 [xfs]" at daddr 0x3ae0bca0 len 32 error 5 Aug 27 13:49:03 Tower kernel: XFS (nvme1n1p1): log I/O error -5 Aug 27 13:49:03 Tower kernel: XFS (nvme1n1p1): Filesystem has been shut down due to log error (0x2). Aug 27 13:49:03 Tower kernel: XFS (nvme1n1p1): Please unmount the filesystem and rectify the problem(s). Should I go back to to the previous Unraid release? Diagnostiics attached. Thanks in advance. tower-diagnostics-20240827-1549.zip
-
Ooops, that it was. Thanks a lot. I switched that to once a month to avoid repeating notifications. Wish I could set it to notify once.
-
I doubt that. My main server is at over 3 month uptime currently. Still no update notification. There must be something else that's failing.
-
You're talking about these? Still no update banner in my browser. First time in many years as I wrote.
