rickypeepee Posted February 18, 2023 Share Posted February 18, 2023 (edited) As per title. This is an old array that I'm trying to extract some data from. Old motherboard/cpu were toast so replaced with new hardware. Haven't used unraid in a while so the upgrade webui features are quite lovely! However, I'm having difficulty starting this array. It's stuck on mounting, forever. Here's a snapshot of my system log: Feb 18 10:03:44 COSMOS winbindd[1200]: [2023/02/18 10:03:44.819126, 0] ../../source3/winbindd/winbindd_dual.c:1957(winbindd_sig_term_handler) Feb 18 10:03:44 COSMOS winbindd[1203]: Got sig[15] terminate (is_parent=0) Feb 18 10:03:44 COSMOS winbindd[1200]: Got sig[15] terminate (is_parent=1) Feb 18 10:03:44 COSMOS wsdd2[1197]: terminating. Feb 18 10:03:45 COSMOS ntpd[1146]: receive: Unexpected origin timestamp 0xe79b9180.cc595880 does not match aorg 0000000000.00000000 from [email protected] xmt 0xe79b9181.48ca1b47 Feb 18 10:03:45 COSMOS ntpd[1146]: receive: Unexpected origin timestamp 0xe79b9180.cc5cd5b1 does not match aorg 0000000000.00000000 from [email protected] xmt 0xe79b9181.48c5bb59 Feb 18 10:03:45 COSMOS ntpd[1146]: receive: Unexpected origin timestamp 0xe79b9180.cc5f3260 does not match aorg 0000000000.00000000 from [email protected] xmt 0xe79b9181.49467c8a Feb 18 10:03:47 COSMOS root: Starting Samba: /usr/sbin/smbd -D Feb 18 10:03:47 COSMOS smbd[1399]: [2023/02/18 10:03:47.620215, 0] ../../source3/smbd/server.c:1741(main) Feb 18 10:03:47 COSMOS smbd[1399]: smbd version 4.17.3 started. Feb 18 10:03:47 COSMOS smbd[1399]: Copyright Andrew Tridgell and the Samba Team 1992-2022 Feb 18 10:03:47 COSMOS root: /usr/sbin/wsdd2 -d Feb 18 10:03:47 COSMOS wsdd2[1413]: starting. Feb 18 10:03:47 COSMOS root: /usr/sbin/winbindd -D Feb 18 10:03:47 COSMOS winbindd[1414]: [2023/02/18 10:03:47.692940, 0] ../../source3/winbindd/winbindd.c:1440(main) Feb 18 10:03:47 COSMOS winbindd[1414]: winbindd version 4.17.3 started. Feb 18 10:03:47 COSMOS winbindd[1414]: Copyright Andrew Tridgell and the Samba Team 1992-2022 Feb 18 10:03:47 COSMOS winbindd[1416]: [2023/02/18 10:03:47.696654, 0] ../../source3/winbindd/winbindd_cache.c:3116(initialize_winbindd_cache) Feb 18 10:03:47 COSMOS winbindd[1416]: initialize_winbindd_cache: clearing cache and re-creating with version number 2 Feb 18 10:03:47 COSMOS emhttpd: shcmd (17): /etc/rc.d/rc.avahidaemon start Feb 18 10:03:47 COSMOS root: Starting Avahi mDNS/DNS-SD Daemon: /usr/sbin/avahi-daemon -D Feb 18 10:03:47 COSMOS avahi-daemon[1433]: Found user 'avahi' (UID 61) and group 'avahi' (GID 214). Feb 18 10:03:47 COSMOS avahi-daemon[1433]: Successfully dropped root privileges. Feb 18 10:03:47 COSMOS avahi-daemon[1433]: avahi-daemon 0.8 starting up. Feb 18 10:03:47 COSMOS avahi-daemon[1433]: Successfully called chroot(). Feb 18 10:03:47 COSMOS avahi-daemon[1433]: Successfully dropped remaining capabilities. Feb 18 10:03:47 COSMOS avahi-daemon[1433]: Loading service file /services/sftp-ssh.service. Feb 18 10:03:47 COSMOS avahi-daemon[1433]: Loading service file /services/smb.service. Feb 18 10:03:47 COSMOS avahi-daemon[1433]: Loading service file /services/ssh.service. Feb 18 10:03:47 COSMOS avahi-daemon[1433]: Joining mDNS multicast group on interface br0.IPv4 with address 192.168.5.220. Feb 18 10:03:47 COSMOS avahi-daemon[1433]: New relevant interface br0.IPv4 for mDNS. Feb 18 10:03:47 COSMOS avahi-daemon[1433]: Joining mDNS multicast group on interface lo.IPv6 with address ::1. Feb 18 10:03:47 COSMOS avahi-daemon[1433]: New relevant interface lo.IPv6 for mDNS. Feb 18 10:03:47 COSMOS avahi-daemon[1433]: Joining mDNS multicast group on interface lo.IPv4 with address 127.0.0.1. Feb 18 10:03:47 COSMOS avahi-daemon[1433]: New relevant interface lo.IPv4 for mDNS. Feb 18 10:03:47 COSMOS avahi-daemon[1433]: Network interface enumeration completed. Feb 18 10:03:47 COSMOS avahi-daemon[1433]: Registering new address record for 192.168.5.220 on br0.IPv4. Feb 18 10:03:47 COSMOS avahi-daemon[1433]: Registering new address record for ::1 on lo.*. Feb 18 10:03:47 COSMOS avahi-daemon[1433]: Registering new address record for 127.0.0.1 on lo.IPv4. Feb 18 10:03:47 COSMOS emhttpd: shcmd (18): /etc/rc.d/rc.avahidnsconfd start Feb 18 10:03:47 COSMOS root: Starting Avahi mDNS/DNS-SD DNS Server Configuration Daemon: /usr/sbin/avahi-dnsconfd -D Feb 18 10:03:47 COSMOS avahi-dnsconfd[1444]: Successfully connected to Avahi daemon. Feb 18 10:03:47 COSMOS emhttpd: Autostart disabled (safe mode specified) Feb 18 10:03:47 COSMOS emhttpd: shcmd (23): /etc/rc.d/rc.php-fpm start Feb 18 10:03:47 COSMOS root: Starting php-fpm done Feb 18 10:03:47 COSMOS emhttpd: shcmd (24): /etc/rc.d/rc.nginx start Feb 18 10:03:47 COSMOS root: Starting Nginx server daemon... Feb 18 10:03:48 COSMOS avahi-daemon[1433]: Server startup complete. Host name is COSMOS.local. Local service cookie is 3632660315. Feb 18 10:03:49 COSMOS avahi-daemon[1433]: Service "COSMOS" (/services/ssh.service) successfully established. Feb 18 10:03:49 COSMOS avahi-daemon[1433]: Service "COSMOS" (/services/smb.service) successfully established. Feb 18 10:03:49 COSMOS avahi-daemon[1433]: Service "COSMOS" (/services/sftp-ssh.service) successfully established. Feb 18 10:04:10 COSMOS webGUI: Successful login user root from 192.168.5.225 Feb 18 10:04:18 COSMOS dbus-daemon[1523]: [session uid=0 pid=1519] Activating service name='org.a11y.Bus' requested by ':1.2' (uid=0 pid=2021 comm="sakura") Feb 18 10:04:18 COSMOS dbus-daemon[1523]: [session uid=0 pid=1519] Successfully activated service 'org.a11y.Bus' Feb 18 10:04:20 COSMOS root: error: /webGui/include/InitCharts.php: wrong csrf_token Feb 18 10:05:37 COSMOS emhttpd: shcmd (130): /usr/local/sbin/set_ncq sdf 1 Feb 18 10:05:37 COSMOS kernel: mdcmd (31): set md_num_stripes 1280 Feb 18 10:05:37 COSMOS kernel: mdcmd (32): set md_queue_limit 80 Feb 18 10:05:37 COSMOS kernel: mdcmd (33): set md_sync_limit 5 Feb 18 10:05:37 COSMOS kernel: mdcmd (34): set md_write_method Feb 18 10:05:37 COSMOS root: set_ncq: setting sdf queue_depth to 1 Feb 18 10:05:37 COSMOS emhttpd: shcmd (131): /usr/local/sbin/set_ncq sde 1 Feb 18 10:05:37 COSMOS root: set_ncq: setting sde queue_depth to 1 Feb 18 10:05:37 COSMOS emhttpd: shcmd (132): /usr/local/sbin/set_ncq sdd 1 Feb 18 10:05:37 COSMOS root: set_ncq: setting sdd queue_depth to 1 Feb 18 10:05:37 COSMOS emhttpd: shcmd (133): /usr/local/sbin/set_ncq sdc 1 Feb 18 10:05:37 COSMOS root: set_ncq: setting sdc queue_depth to 1 Feb 18 10:05:37 COSMOS emhttpd: shcmd (134): /usr/local/sbin/set_ncq sdb 1 Feb 18 10:05:37 COSMOS root: set_ncq: setting sdb queue_depth to 1 Feb 18 10:05:37 COSMOS kernel: mdcmd (35): start STOPPED Feb 18 10:05:37 COSMOS kernel: unraid: allocating 31110K for 1280 stripes (6 disks) Feb 18 10:05:37 COSMOS kernel: md1: running, size: 1465138552 blocks Feb 18 10:05:37 COSMOS kernel: md2: running, size: 1465138552 blocks Feb 18 10:05:37 COSMOS kernel: md3: running, size: 1465138552 blocks Feb 18 10:05:37 COSMOS kernel: md4: running, size: 976762552 blocks Feb 18 10:05:37 COSMOS emhttpd: shcmd (135): udevadm settle Feb 18 10:05:38 COSMOS emhttpd: Opening encrypted volumes... Feb 18 10:05:38 COSMOS emhttpd: shcmd (136): touch /boot/config/forcesync Feb 18 10:05:38 COSMOS emhttpd: Mounting disks... Feb 18 10:05:38 COSMOS emhttpd: shcmd (138): mkdir -p /mnt/disk1 Feb 18 10:05:38 COSMOS emhttpd: shcmd (139): mount -t reiserfs -o noatime,user_xattr,acl /dev/md1 /mnt/disk1 Feb 18 10:05:38 COSMOS kernel: REISERFS warning: read_super_block: reiserfs filesystem is deprecated and scheduled to be removed from the kernel in 2025 Feb 18 10:05:38 COSMOS kernel: REISERFS (device md1): found reiserfs format "3.6" with standard journal Feb 18 10:05:38 COSMOS kernel: REISERFS (device md1): using ordered data mode Feb 18 10:05:38 COSMOS kernel: reiserfs: using flush barriers Feb 18 10:05:39 COSMOS kernel: REISERFS (device md1): journal params: device md1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Feb 18 10:05:39 COSMOS kernel: REISERFS (device md1): checking transaction log (md1) Feb 18 10:08:35 COSMOS nginx: 2023/02/18 10:08:35 [error] 1496#1496: *660 upstream timed out (110: Connection timed out) while reading upstream, client: 192.168.5.225, server: , request: "POST /update.htm HTTP/1.1", upstream: "http://unix:/var/run/emhttpd.socket:/update.htm", host: "cosmos.local", referrer: "http://cosmos.local/Main" Feb 18 10:09:46 COSMOS ntpd[1146]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Feb 18 10:11:09 COSMOS webGUI: Successful login user root from 192.168.5.225 CPU Usage is at 100% for at least one of the cores: The filesystem uses reiserfs, which probably wasn't a great choice in hindsight. Active processes as shown: I have no clue how to proceed. Any recommendations? Full syslog attached. cosmos-syslog-20230218-1837.zip Edited February 18, 2023 by rickypeepee syslog addition Quote Link to comment
trurl Posted February 18, 2023 Share Posted February 18, 2023 1 hour ago, rickypeepee said: filesystem uses reiserf Scheduled for removal 2025 Attach Diagnostics to your NEXT post in this thread Quote Link to comment
rickypeepee Posted February 18, 2023 Author Share Posted February 18, 2023 Diagnostics attached. cosmos-diagnostics-20230218-1515.zip Quote Link to comment
trurl Posted February 18, 2023 Share Posted February 18, 2023 Not sure if this applies to your situation or not. Quote Link to comment
trurl Posted February 18, 2023 Share Posted February 18, 2023 Here is the news about reiser Quote Link to comment
trurl Posted February 18, 2023 Share Posted February 18, 2023 Don't see a lot of users on reiser anymore, don't know if your problems might be related to that or not. If your webUI is working OK, go to Disk Settings and disable autostart. If you can't do that, shutdown and you can edit config/disk.cfg on the flash drive in your PC to accomplish the same thing. Reboot and start the array in Maintenance mode so you can check filesystem on all your disks. Quote Link to comment
Solution JorgeB Posted February 19, 2023 Solution Share Posted February 19, 2023 17 hours ago, rickypeepee said: Feb 18 10:05:39 COSMOS kernel: REISERFS (device md1): checking transaction log (md1) With reiser this can take a long time, more than 1 hour, if the disk was not cleanly unmounted, suggest converting to XFS ASAP Quote Link to comment
rickypeepee Posted February 19, 2023 Author Share Posted February 19, 2023 3 hours ago, JorgeB said: With reiser this can take a long time, more than 1 hour, if the disk was not cleanly unmounted, suggest converting to XFS ASAP This was it. I just left it overnight and the array was up and running a parity check by the time I woke up. Extracting my data now For the next step in my upgrade, I'm dropping in totally fresh new drives and I'll be sure to use XFS this time! Thank you all for taking a look at this issue! Quote Link to comment
trurl Posted February 19, 2023 Share Posted February 19, 2023 32 minutes ago, rickypeepee said: dropping in totally fresh new drives and I'll be sure to use XFS this time You still need to convert the reiser disks. Quote Link to comment
rickypeepee Posted February 19, 2023 Author Share Posted February 19, 2023 (edited) 35 minutes ago, trurl said: You still need to convert the reiser disks. I'm no longer using the old drives. At all. I just needed the data from them. They'll get a low level format then donation. Edited February 19, 2023 by rickypeepee Quote Link to comment
trurl Posted February 19, 2023 Share Posted February 19, 2023 Just now, rickypeepee said: I'm no longer using the old drives. At all. I just needed the data from them. After you copy their data, do you know how to remove them from the array? Quote Link to comment
rickypeepee Posted February 19, 2023 Author Share Posted February 19, 2023 4 minutes ago, trurl said: After you copy their data, do you know how to remove them from the array? Just planning to use a new config. The old array is getting retired 🙃 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.