fizzy6868 Posted June 24, 2023 Share Posted June 24, 2023 ok i had the system lockup on me and had to hard reset but for some reason the cache drives are now Unmountable i had them set up so the one would mirror the other of backups if drive false but i am consired as i dont know what to do as now i have no cache. please help i cant work out what has happend and really need the data thanks fawkesserver-diagnostics-20230624-0917.zip KIOXIA-EXCERIA_SATA_SSD_118C224EEFJ2_Disk1.txt KIOXIA-EXCERIA_SATA_SSD_Z09C223UEFJ2_BackUp.txt Quote Link to comment
JorgeB Posted June 24, 2023 Share Posted June 24, 2023 This may help if the problem is manly the log tree: btrfs rescue zero-log /dev/sdg1 Pool was already detecting data corruption, you have RAM speed higher then it should be for your config, and that's a known issue with Ryzen, if the command above works you should correct that then run memtest and scrub the pool. Quote Link to comment
fizzy6868 Posted June 24, 2023 Author Share Posted June 24, 2023 Thanks so much for a fast reply. I will give this ago I don't know why the RAM speed is higher as I have never messed with the ram Quote Link to comment
fizzy6868 Posted June 24, 2023 Author Share Posted June 24, 2023 1 hour ago, JorgeB said: This may help if the problem is manly the log tree: btrfs rescue zero-log /dev/sdg1 Pool was already detecting data corruption, you have RAM speed higher then it should be for your config, and that's a known issue with Ryzen, if the command above works you should correct that then run memtest and scrub the pool. when i try to scrub i am getting an error csum2 so i done a filesystem scan and getting this error could you shed some light on what i need to do next ? thanks btrfs_check_status.txt Quote Link to comment
JorgeB Posted June 24, 2023 Share Posted June 24, 2023 That is not a scrub, does the pool mount after running the command above? Quote Link to comment
fizzy6868 Posted June 24, 2023 Author Share Posted June 24, 2023 yes it does mount then went to do a scrub and could not complete it. it would just abort scrub.txt fawkesserver-diagnostics-20230624-1453.zip Quote Link to comment
JorgeB Posted June 25, 2023 Share Posted June 25, 2023 19 hours ago, fizzy6868 said: it would just abort In that case suggest backing up and re-creating the pool. Quote Link to comment
Alpha2011 Posted June 25, 2023 Share Posted June 25, 2023 Hi all, I am having this issue today. Initially unraid sent a ton of messages indicating : BTRFS warning (device sdg1): csum failed root (similar to this ) I tried o perfom a btrfss_scrub but it did not proceed . I rebooted the system and my Cache ssd (m.2) is now missing. This is all the log i can get without being able of starting the array. text error warn system array login Jun 25 16:06:01 Tower kernel: mdcmd (28): import 27 Jun 25 16:06:01 Tower kernel: mdcmd (29): import 28 Jun 25 16:06:01 Tower kernel: mdcmd (30): import 29 Jun 25 16:06:01 Tower kernel: md: import_slot: 29 empty Jun 25 16:06:01 Tower emhttpd: import 30 cache device: no device Jun 25 16:06:01 Tower emhttpd: import 31 cache device: (sdb) SanDisk_SD6SB1M-128G-1006_141262402316 Jun 25 16:06:01 Tower emhttpd: import flash device: sda Jun 25 16:06:01 Tower root: Starting apcupsd power management: /sbin/apcupsd Jun 25 16:06:01 Tower apcupsd[4263]: apcupsd 3.14.14 (31 May 2016) slackware startup succeeded Jun 25 16:06:01 Tower apcupsd[4263]: NIS server startup succeeded Jun 25 16:06:01 Tower emhttpd: read SMART /dev/sdd Jun 25 16:06:01 Tower emhttpd: read SMART /dev/sde Jun 25 16:06:01 Tower emhttpd: read SMART /dev/sdb Jun 25 16:06:01 Tower emhttpd: read SMART /dev/sdf Jun 25 16:06:01 Tower emhttpd: read SMART /dev/sdc Jun 25 16:06:01 Tower emhttpd: read SMART /dev/sda Jun 25 16:06:01 Tower emhttpd: Starting services... Jun 25 16:06:01 Tower emhttpd: shcmd (13): /etc/rc.d/rc.samba restart Jun 25 16:06:01 Tower wsdd2[1173]: 'Terminated' signal received. Jun 25 16:06:01 Tower winbindd[1176]: [2023/06/25 16:06:01.611354, 0] ../../source3/winbindd/winbindd.c:247(winbindd_sig_term_handler) Jun 25 16:06:01 Tower winbindd[1176]: Got sig[15] terminate (is_parent=1) Jun 25 16:06:01 Tower winbindd[1177]: [2023/06/25 16:06:01.611359, 0] ../../source3/winbindd/winbindd.c:247(winbindd_sig_term_handler) Jun 25 16:06:01 Tower winbindd[1177]: Got sig[15] terminate (is_parent=0) Jun 25 16:06:01 Tower wsdd2[1173]: terminating. Jun 25 16:06:01 Tower winbindd[2517]: [2023/06/25 16:06:01.611434, 0] ../../source3/winbindd/winbindd.c:247(winbindd_sig_term_handler) Jun 25 16:06:01 Tower winbindd[2517]: Got sig[15] terminate (is_parent=0) Jun 25 16:06:03 Tower root: Starting Samba: /usr/sbin/smbd -D Jun 25 16:06:03 Tower smbd[4335]: [2023/06/25 16:06:03.803177, 0] ../../source3/smbd/server.c:1734(main) Jun 25 16:06:03 Tower smbd[4335]: smbd version 4.15.7 started. Jun 25 16:06:03 Tower smbd[4335]: Copyright Andrew Tridgell and the Samba Team 1992-2021 Jun 25 16:06:03 Tower root: /usr/sbin/wsdd2 -d Jun 25 16:06:03 Tower wsdd2[4349]: starting. Jun 25 16:06:03 Tower root: /usr/sbin/winbindd -D Jun 25 16:06:03 Tower winbindd[4350]: [2023/06/25 16:06:03.867361, 0] ../../source3/winbindd/winbindd.c:1722(main) Jun 25 16:06:03 Tower winbindd[4350]: winbindd version 4.15.7 started. Jun 25 16:06:03 Tower winbindd[4350]: Copyright Andrew Tridgell and the Samba Team 1992-2021 Jun 25 16:06:03 Tower winbindd[4352]: [2023/06/25 16:06:03.871376, 0] ../../source3/winbindd/winbindd_cache.c:3085(initialize_winbindd_cache) Jun 25 16:06:03 Tower winbindd[4352]: initialize_winbindd_cache: clearing cache and re-creating with version number 2 Jun 25 16:06:03 Tower emhttpd: shcmd (16): /etc/rc.d/rc.nfsd start Jun 25 16:06:03 Tower kernel: RPC: Registered named UNIX socket transport module. Jun 25 16:06:03 Tower kernel: RPC: Registered udp transport module. Jun 25 16:06:03 Tower kernel: RPC: Registered tcp transport module. Jun 25 16:06:03 Tower kernel: RPC: Registered tcp NFSv4.1 backchannel transport module. Jun 25 16:06:03 Tower kernel: Installing knfsd (copyright (C) 1996 [email protected]). Jun 25 16:06:03 Tower root: Starting RPC portmapper: /sbin/rpcbind -w Jun 25 16:06:03 Tower root: Starting RPC NSM (Network Status Monitor): /sbin/rpc.statd Jun 25 16:06:03 Tower rpc.statd[4379]: Version 2.5.4 starting Jun 25 16:06:03 Tower sm-notify[4380]: Version 2.5.4 starting Jun 25 16:06:03 Tower rpc.statd[4379]: Failed to read /var/lib/nfs/state: Success Jun 25 16:06:03 Tower rpc.statd[4379]: Initializing NSM state Jun 25 16:06:03 Tower root: Starting NFS server daemons: Jun 25 16:06:03 Tower root: /usr/sbin/exportfs -r Jun 25 16:06:03 Tower root: /usr/sbin/rpc.nfsd 8 Jun 25 16:06:05 Tower kernel: NFSD: Using UMH upcall client tracking operations. Jun 25 16:06:05 Tower kernel: NFSD: starting 90-second grace period (net f0000000) Jun 25 16:06:05 Tower root: /usr/sbin/rpc.mountd Jun 25 16:06:05 Tower rpc.mountd[4397]: Version 2.5.4 starting Jun 25 16:06:05 Tower emhttpd: shcmd (18): /etc/rc.d/rc.avahidaemon start Jun 25 16:06:05 Tower root: Starting Avahi mDNS/DNS-SD Daemon: /usr/sbin/avahi-daemon -D Jun 25 16:06:05 Tower avahi-daemon[4409]: Found user 'avahi' (UID 61) and group 'avahi' (GID 214). Jun 25 16:06:05 Tower avahi-daemon[4409]: Successfully dropped root privileges. Jun 25 16:06:05 Tower avahi-daemon[4409]: avahi-daemon 0.8 starting up. Jun 25 16:06:05 Tower avahi-daemon[4409]: Successfully called chroot(). Jun 25 16:06:05 Tower avahi-daemon[4409]: Successfully dropped remaining capabilities. Jun 25 16:06:05 Tower avahi-daemon[4409]: Loading service file /services/sftp-ssh.service. Jun 25 16:06:05 Tower avahi-daemon[4409]: Loading service file /services/smb.service. Jun 25 16:06:05 Tower avahi-daemon[4409]: Loading service file /services/ssh.service. Jun 25 16:06:05 Tower avahi-daemon[4409]: Joining mDNS multicast group on interface br0.IPv4 with address 192.168.1.102. Jun 25 16:06:05 Tower avahi-daemon[4409]: New relevant interface br0.IPv4 for mDNS. Jun 25 16:06:05 Tower avahi-daemon[4409]: Joining mDNS multicast group on interface lo.IPv6 with address ::1. Jun 25 16:06:05 Tower avahi-daemon[4409]: New relevant interface lo.IPv6 for mDNS. Jun 25 16:06:05 Tower avahi-daemon[4409]: Joining mDNS multicast group on interface lo.IPv4 with address 127.0.0.1. Jun 25 16:06:05 Tower avahi-daemon[4409]: New relevant interface lo.IPv4 for mDNS. Jun 25 16:06:05 Tower avahi-daemon[4409]: Network interface enumeration completed. Jun 25 16:06:05 Tower avahi-daemon[4409]: Registering new address record for 192.168.1.102 on br0.IPv4. Jun 25 16:06:05 Tower avahi-daemon[4409]: Registering new address record for ::1 on lo.*. Jun 25 16:06:05 Tower avahi-daemon[4409]: Registering new address record for 127.0.0.1 on lo.IPv4. Jun 25 16:06:05 Tower emhttpd: shcmd (19): /etc/rc.d/rc.avahidnsconfd start Jun 25 16:06:05 Tower root: Starting Avahi mDNS/DNS-SD DNS Server Configuration Daemon: /usr/sbin/avahi-dnsconfd -D Jun 25 16:06:05 Tower avahi-dnsconfd[4418]: Successfully connected to Avahi daemon. Jun 25 16:06:05 Tower emhttpd: Autostart disabled Jun 25 16:06:05 Tower emhttpd: shcmd (24): /etc/rc.d/rc.php-fpm start Jun 25 16:06:05 Tower root: Starting php-fpm done Jun 25 16:06:05 Tower emhttpd: shcmd (25): /etc/rc.d/rc.nginx start Jun 25 16:06:05 Tower root: Starting Nginx server daemon... Jun 25 16:06:05 Tower avahi-daemon[4409]: Server startup complete. Host name is Tower.local. Local service cookie is 3182271114. Jun 25 16:06:06 Tower avahi-daemon[4409]: Service "Tower" (/services/ssh.service) successfully established. Jun 25 16:06:06 Tower avahi-daemon[4409]: Service "Tower" (/services/smb.service) successfully established. Jun 25 16:06:06 Tower avahi-daemon[4409]: Service "Tower" (/services/sftp-ssh.service) successfully established. Jun 25 16:06:28 Tower webGUI: Successful login user root from Please let me know what else i can do . Thank you in advance . Quote Link to comment
JorgeB Posted June 26, 2023 Share Posted June 26, 2023 8 hours ago, Alpha2011 said: Please let me know what else i can do . Please post the diagnostics. Quote Link to comment
Alpha2011 Posted June 26, 2023 Share Posted June 26, 2023 Thank you, here it is . tower-diagnostics-20230626-0850.zip Quote Link to comment
JorgeB Posted June 26, 2023 Share Posted June 26, 2023 7 minutes ago, Alpha2011 said: here it is . After array start please. Quote Link to comment
Alpha2011 Posted June 26, 2023 Share Posted June 26, 2023 tower-diagnostics-20230626-1031.zip Hi , the option to start the array was greyed out. I hit the check mark on the option to start the array without the cache drive. Quote Link to comment
JorgeB Posted June 26, 2023 Share Posted June 26, 2023 1 minute ago, Alpha2011 said: Hi , the option to start the array was greyed out. Sorry, I missed that the cache device was now missing, try power cycling the server (not just rebooting) or re-seating the device. Quote Link to comment
Alpha2011 Posted June 26, 2023 Share Posted June 26, 2023 Ok, Power cycling brought back the SSD. Attached are the diagnostic files with the array back online. tower-diagnostics-20230626-1045.zip Quote Link to comment
JorgeB Posted June 26, 2023 Share Posted June 26, 2023 Everything looks good so far, if it drops again save the diags before rebooting. Quote Link to comment
Alpha2011 Posted June 26, 2023 Share Posted June 26, 2023 Understood , thank you for your time. 1 Quote Link to comment
Recommended Posts
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.