plugout.net

by **serram** » Mon Sep 14, 2020 6:18 pm

Ok, I think something go wrong...

Code: Select all: root@fvdwsl-base:/ # plugout download 6495 login successful file='/tmp/fvdw-sl-18-2-disk-monitoring.tgz' logout successful root@fvdwsl-base:/ # tar -xf /tmp/fvdw-sl-18-2-disk-monitoring.tgz tar: Unexpected EOF in archive tar: Unexpected EOF in archive tar: Error is not recoverable: exiting now root@fvdwsl-base:/ # root@fvdwsl-base:/ # diskmon 15 root@fvdwsl-base:/ # root@fvdwsl-base:/ # ps axf PID TTY STAT TIME COMMAND 2 ? S 0:00 [kthreadd] 4 ? I< 0:00 \_ [kworker/0:0H] 5 ? I 0:00 \_ [kworker/u2:0] 6 ? I< 0:00 \_ [mm_percpu_wq] 7 ? S 0:01 \_ [ksoftirqd/0] 8 ? I 0:02 \_ [rcu_preempt] 9 ? I 0:00 \_ [rcu_sched] 10 ? I 0:00 \_ [rcu_bh] 11 ? I< 0:00 \_ [netns] 276 ? S 0:00 \_ [oom_reaper] 277 ? I< 0:00 \_ [writeback] 279 ? I< 0:00 \_ [crypto] 280 ? I< 0:00 \_ [kintegrityd] 282 ? I< 0:00 \_ [kblockd] 288 ? I< 0:00 \_ [ata_sff] 306 ? I< 0:00 \_ [md] 398 ? I< 0:00 \_ [rpciod] 399 ? I< 0:00 \_ [xprtiod] 400 ? S 0:00 \_ [kswapd0] 411 ? I< 0:00 \_ [nfsiod] 412 ? I< 0:00 \_ [cifsiod] 413 ? I< 0:00 \_ [cifsoplockd] 414 ? S 0:00 \_ [jfsIO] 418 ? S 0:00 \_ [jfsCommit] 419 ? S 0:00 \_ [jfsSync] 420 ? I< 0:00 \_ [xfsalloc] 421 ? I< 0:00 \_ [xfs_mru_cache] 562 ? S 0:00 \_ [scsi_eh_0] 563 ? I< 0:00 \_ [scsi_tmf_0] 567 ? I< 0:00 \_ [smflush] 572 ? S 0:00 \_ [spi0] 573 ? I 0:00 \_ [kworker/u2:3] 643 ? S< 0:00 \_ [aoe_tx0] 644 ? S< 0:00 \_ [aoe_ktio0] 659 ? I< 0:00 \_ [raid5wq] 662 ? I< 0:00 \_ [dm_bufio_cache] 663 ? I< 0:00 \_ [kmpathd] 664 ? I< 0:00 \_ [kmpath_handlerd] 682 ? I< 0:00 \_ [ipv6_addrconf] 685 ? I< 0:00 \_ [dsa_ordered] 713 ? I< 0:00 \_ [kworker/0:1H] 714 ? S 0:00 \_ [jbd2/sda7-8] 715 ? I< 0:00 \_ [ext4-rsv-conver] 735 ? S 0:00 \_ [jbd2/sda2-8] 736 ? I< 0:00 \_ [ext4-rsv-conver] 765 ? I< 0:00 \_ [iscsi_eh] 785 ? S 0:00 \_ [jbd2/sda5-8] 786 ? I< 0:00 \_ [ext4-rsv-conver] 1257 ? S 0:00 \_ [jbd2/sda8-8] 1258 ? I< 0:00 \_ [ext4-rsv-conver] 5331 ? I 0:00 \_ [kworker/0:1] 5334 ? I 0:00 \_ [kworker/0:2] 5419 ? I 0:00 \_ [kworker/0:0] 1 ? Ss 0:02 init 774 ? Ss 0:00 /usr/sbin/buttonsd 937 ? S<s 0:00 /sbin/udevd --daemon 1308 ? Ss 0:07 /usr/bin/httpd -f httpd.conf -d /etc 1309 ? S 0:07 \_ /usr/bin/httpd -f httpd.conf -d /etc 1554 ? S 0:05 \_ /usr/bin/httpd -f httpd.conf -d /etc 1312 ? Ss 0:33 /usr/sbin/noflushd -n 30 /dev/sda 1341 ? Ss 0:00 /usr/bin/discoverd 1349 ? Ss 0:00 /usr/bin/rpcbind 1367 ? Ss 0:00 dropbear -p 22 -r /rw_fs/etc/dropbear/dropbear_rsa_ho 5335 ? Ss 0:00 \_ dropbear -p 22 -r /rw_fs/etc/dropbear/dropbear_rs 5336 pts/0 Ss 0:00 \_ -sh 5504 pts/0 R+ 0:00 \_ ps afx 1386 ? Ss 0:00 /usr/sbin/hostd 7200 1432 ? Ssl 0:11 /usr/local/bin/minidlna -f /direct-usb/minidlna/minid 1459 ? Ss 0:12 /usr/sbin/nmbd -D -l /var/log/samba 1461 ? Ss 0:01 /usr/sbin/smbd -D -l /var/log/samba 1468 ? S 0:00 \_ /usr/sbin/smbd -D -l /var/log/samba 1470 ? S 0:00 \_ /usr/sbin/smbd -D -l /var/log/samba 1552 ? Ss 0:01 /bin/ntpd -p time.windows.com -p pool.ntp.org root@fvdwsl-base:/ #

by **Jocko** » Mon Sep 14, 2020 6:23 pm

Indeed the attached file was corrupted.

So uploaded again and the command is now

Code: Select all: plugout download 6496

by **serram** » Mon Sep 14, 2020 8:15 pm

Finally I unpluged the LAN cable when I checked that the diskmon was running.
I waited until the disk remain still, and then I waited until it do a spin up again, and at that precise time I plug the cable and I opened a shell session, I killed the diskmon process and check the content of log1 and log2 files.
log2 is empty.
The disk did a spin up at 21:48h, so the content of the file log1 at that moment is:

Code: Select all: ==== Mon Sep 14 21:48:28 CEST 2020 ==== [261961.371279] jbd2/sda5-8(785): WRITE block 556192 on sda5 (8 sectors) [261961.371316] jbd2/sda5-8(785): WRITE block 556200 on sda5 (8 sectors) [261961.371334] jbd2/sda5-8(785): WRITE block 556208 on sda5 (8 sectors) [261961.371348] jbd2/sda5-8(785): WRITE block 556216 on sda5 (8 sectors) [261961.371361] jbd2/sda5-8(785): WRITE block 556224 on sda5 (8 sectors) [261961.371374] jbd2/sda5-8(785): WRITE block 556232 on sda5 (8 sectors) [261967.080307] jbd2/sda5-8(785): WRITE block 556240 on sda5 (8 sectors) [261967.201449] noflushd(1312): WRITE block 0 on sda5 (8 sectors) [261967.201494] noflushd(1312): WRITE block 8 on sda5 (8 sectors) [261967.201518] noflushd(1312): WRITE block 786856 on sda5 (8 sectors) [261967.201544] noflushd(1312): WRITE block 786864 on sda5 (8 sectors) [261967.201564] noflushd(1312): WRITE block 790608 on sda5 (8 sectors) [261974.171276] jbd2/sda5-8(785): WRITE block 556248 on sda5 (8 sectors) [261974.171316] jbd2/sda5-8(785): WRITE block 556256 on sda5 (8 sectors) [261974.171334] jbd2/sda5-8(785): WRITE block 556264 on sda5 (8 sectors) [261974.171349] jbd2/sda5-8(785): WRITE block 556272 on sda5 (8 sectors) [261974.171362] jbd2/sda5-8(785): WRITE block 556280 on sda5 (8 sectors) [261974.171375] jbd2/sda5-8(785): WRITE block 556288 on sda5 (8 sectors) [261974.171934] jbd2/sda5-8(785): WRITE block 556296 on sda5 (8 sectors) [261990.940686] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled ==== Mon Sep 14 21:49:32 CEST 2020 ==== [262025.051295] jbd2/sda2-8(735): WRITE block 4178 on sda2 (2 sectors) [262025.051336] jbd2/sda2-8(735): WRITE block 4180 on sda2 (2 sectors) [262025.051705] jbd2/sda2-8(735): WRITE block 4182 on sda2 (2 sectors) [262025.371245] jbd2/sda5-8(785): WRITE block 556304 on sda5 (8 sectors) [262025.371275] jbd2/sda5-8(785): WRITE block 556312 on sda5 (8 sectors) [262025.371292] jbd2/sda5-8(785): WRITE block 556320 on sda5 (8 sectors) [262025.371714] jbd2/sda5-8(785): WRITE block 556328 on sda5 (8 sectors) Logging stopped : Mon Sep 14 21:49:49 CEST 2020 Logging stopped : Mon Sep 14 21:49:49 CEST 2020

I don't really know if this is a helpfull information...
I've attached the whole file log1

by **Jocko** » Mon Sep 14, 2020 9:07 pm

Thank you

So only two threads doing I/O on your period: JBD2 (it's a kernel thread to handle the fs journaling) and noflushd
I don't think the behavior of jbd2 is right with the sda5 partition. Maybe there is a fs problem on this side

Can you post

Code: Select all: file -bs /dev/sda5 tune2fs -l /dev/sda5 e2fsck -nf /dev/sda5

by **serram** » Tue Sep 15, 2020 10:21 pm

Before anything, thank you so much for your help.
And now, this is the output of the three comands:

Code: Select all: root@fvdwsl-base:/ # file -bs /dev/sda5 Linux rev 1.0 ext3 filesystem data, UUID=303f35a6-e43b-45f5-9be2-3e5086594885 (needs journal recovery) (large files) ---------------------- root@fvdwsl-base:/ # tune2fs -l /dev/sda5 tune2fs 1.43.4 (31-Jan-2017) Filesystem volume name: <none> Last mounted on: /rw_fs Filesystem UUID: 303f35a6-e43b-45f5-9be2-3e5086594885 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file Filesystem flags: unsigned_directory_hash Default mount options: (none) Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 52304 Block count: 208845 Reserved block count: 2088 Free blocks: 200551 Free inodes: 52196 First block: 0 Block size: 4096 Fragment size: 4096 Reserved GDT blocks: 50 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 7472 Inode blocks per group: 467 Filesystem created: Thu Aug 27 20:44:45 2020 Last mount time: Fri Sep 11 21:02:36 2020 Last write time: Fri Sep 11 21:02:36 2020 Mount count: 11 Maximum mount count: 22 Last checked: Thu Aug 27 20:44:45 2020 Check interval: 15552000 (6 months) Next check after: Tue Feb 23 19:44:45 2021 Lifetime writes: 1780 kB Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Journal inode: 8 First orphan inode: 37407 Default directory hash: half_md4 Directory Hash Seed: c2059567-cdcc-42e6-adf2-530731e9449e Journal backup: inode blocks ---------------------- root@fvdwsl-base:/ # e2fsck -nf /dev/sda5 e2fsck 1.43.4 (31-Jan-2017) Warning! /dev/sda5 is mounted. Warning: skipping journal recovery because doing a read-only filesystem check. Pass 1: Checking inodes, blocks, and sizes Deleted inode 37407 has zero dtime. Fix? no Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information Free blocks count wrong (200551, counted=200538). Fix? no Inode bitmap differences: -37407 Fix? no Free inodes count wrong (52196, counted=52182). Fix? no /dev/sda5: ********** WARNING: Filesystem still has errors ********** /dev/sda5: 108/52304 files (8.3% non-contiguous), 8294/208845 blocks

by **Jocko** » Wed Sep 16, 2020 7:26 am

Hi

:corner I didnot notice e2fsck does not examine the journal when the partition is mounted... and I do not think the detected inode error may explain the JBD2 behaviour.

Anyhow we can run e2fsck to fix the inode error and then will check at the same time the journal. You have to use fvdw-sl console because you can not unmount sda5 (partition used by the firmware)

So start the console and select the Action "Standalone kernel load and start". With a cloudbox you have to select the kirkwood standalone kernel version.
Then run

Code: Select all: /fvdw-sl-programs.sh

and select the option 4: "upload-glibc-tools-archive.sh:Upload and extract glibc mini and tools"

So run e2fsck with these options

Code: Select all: e2fsck -fy /dev/sda5

and post its output.
After you can restart the nas

Code: Select all: reboot -f

by **serram** » Wed Sep 16, 2020 10:00 pm

I'm having problems with telnet connection (the last part of the action "Standalone kernel load and start").
The telnet program try to connect with the lacie cloudbox but something goes wrong becouse finally the message is "Connection with 192.168.1.50/telnet timed out".
The IP number is correct.
The exact name of the kernel file that i choose is "UIMAGE-3142-KIRKWOOD-171-standalone".
I only have a Ethernet connection active.
The PC is wired connected to the rooter.
I'm using the fvdw-sl-console downloaded here: http://plugout.net/viewtopic.php?f=7&t=3086

Sorry, but I'm very brand new in all of this.
Any help will be welcome.

by **serram** » Wed Sep 16, 2020 10:34 pm

I've realized that I have a new antivirus software version (kaspersky). Maybe it's the guilty of this situation...
I've tried to stop the firewall, but I can't do it now becouse I think the installation of the antivirus is wrong (it ask for a password to stop the antivirus protection...). That is the normal behavior of the machines in the organization where I work. But now I'm using my home personal computer!!
Tomorrow I will remove the antivirus software and reinstall again checking that I pick the correct version for home computers...
I didn't install the current antivirus version in my PC, it updated automatically without asking anything... One day I was connected to my work VPN when it happened, so probably there was a mistake asuming my PC was a machine of my organization.... Anyway, sorry for this boring history...

by **Jocko** » Thu Sep 17, 2020 8:14 am

Hi

There is also another issue.
It seems you set manually an ip with fvdw-sl for your nas (192.168.1.50). I think you did not understand a point.

If 192.168.1.50 is the IP used by the nas in a regular boot, you do not have to set this Ip with fvdw-sl console.
Indeed when you load a standalone kernel, it is the nas it-self which sets a temporary IP. With your LAN settings, it will be 192.168.1.252 and fvdw-sl console/telnet will send request on this IP
So keep the default settings with fvdw-sl console.

About kernel version, you use the right file

by **serram** » Thu Sep 17, 2020 10:34 pm

Ok, thank you for your indications.

I still have not managed to fix the problem with my antivirus.

Just in case, I've tried again the telnet connection keeping the default settings with fvdw-sl console (using the IP 192.168.1.252), but I always got the same error "Connection with 192.168.1.252/telnet timed out".

So, I guess the antivirus firewall can be the problem now ...

I'll post again here when I could try it with the firewall disabled.

plugout.net

Hard Disk wake up very frecuently

Re: Hard Disk wake up very frecuently

Re: Hard Disk wake up very frecuently

Re: Hard Disk wake up very frecuently

Re: Hard Disk wake up very frecuently

Re: Hard Disk wake up very frecuently

Re: Hard Disk wake up very frecuently

Re: Hard Disk wake up very frecuently

Re: Hard Disk wake up very frecuently

Re: Hard Disk wake up very frecuently

Re: Hard Disk wake up very frecuently

Who is online