Upgraded DNS-323-A official to ALT-F 0.1rc5 fsck.ext4 error

[raywillia...@gmail.com]

Since i bought 2x4tb HDD and officialy it does't supported i moved to ALT-f (thank you very much for your work, developers!).

Installed in mirror raid. 

1. I allways get "Unable to automatically fix md0, mounting Read Only: fsck 1.41.14 (22-Dec-2010)

fsck.ext4: Device or resource busy while trying to open /dev/md0
Filesystem mounted or opened exclusively by another program?"

in web-ui and i dont know what to do 

2. Cpu is often at 100% load, and i dont do anything with hdd, only web-ui , i think something is wrong with it?

please, advice 

[Norbert Horváth]

You should telnet or SSH into the NAS to see what is eating the CPU ("ps aux" or "top"), it may help. If it's fsck, just let it do its work.
You can try stopping all the services, Disk->Filesystem, FS Operations>ForceFix (you can try a "Check" first after stopping all the services), or if you are familiar with Linux shells, you can run fsck manually from command line.

[raywillia...@gmail.com]

o joined with ssh and trying to enter fsck commands but with no luck.

What should i enter?

[root@STORE]# fsck -AR -t ext4 -y

fsck 1.41.14 (22-Dec-2010)

[root@STORE]# fsck -A

fsck 1.41.14 (22-Dec-2010)

[raywillia...@gmail.com]

i also tryed turn off all the services and do manual umount but it allways says it busy, and i dont know with what

[root@STORE]# umount /mnt/md0

umount: can't umount /mnt/md0: Device or resource busy

TOP now look fine:

Mem: 46936K used, 13752K free, 0K shrd, 1628K buff, 711960K cached

CPU:   0% usr   0% sys   0% nic  99% idle   0% io   0% irq   0% sirq

Load average: 0.02 0.07 0.06 1/39 1722

  PID  PPID USER     STAT   VSZ %VSZ %CPU COMMAND

 1722  1147 root     R     1200   2%   0% top

 1138   476 root     S     1204   2%   0% dropbear -i

 1147  1138 root     S     1216   2%   0% -sh

    1     0 root     S     1204   2%   0% init

  476     1 root     S     1204   2%   0% inetd

  746     1 root     S     1204   2%   0% /bin/sh --

  720     2 root     SW       0   0%   0% [md0_raid1]

   70     2 root     SW<      0   0%   0% [kworker/0:1H]

    3     2 root     SW       0   0%   0% [ksoftirqd/0]

 3470     2 root     SW       0   0%   0% [kworker/u2:2]

   15     2 root     SW       0   0%   0% [kswapd0]

 3705     2 root     SW       0   0%   0% [kworker/u2:0]

   67     2 root     SW<      0   0%   0% [loop0]

 1015     2 root     SW       0   0%   0% [jbd2/md0-8]

   29     2 root     SW       0   0%   0% [scsi_eh_0]

   31     2 root     SW       0   0%   0% [scsi_eh_1]

 1243     2 root     SW       0   0%   0% [kworker/0:0]

    2     0 root     SW       0   0%   0% [kthreadd]

 4054     2 root     SW       0   0%   0% [kworker/0:1]

 1435     2 root     SW       0   0%   0% [kworker/0:2]

   16     2 root     SW       0   0%   0% [fsnotify_mark]

   12     2 root     SW<      0   0%   0% [ata_sff]

    7     2 root     SW<      0   0%   0% [khelper]

    9     2 root     SW<      0   0%   0% [crypto]

    5     2 root     SW<      0   0%   0% [kworker/0:0H]

   33     2 root     SW       0   0%   0% [scsi_eh_2]

    8     2 root     SW<      0   0%   0% [writeback]

   30     2 root     SW<      0   0%   0% [scsi_tmf_0]

   10     2 root     SW<      0   0%   0% [bioset]

   11     2 root     SW<      0   0%   0% [kblockd]

  719     2 root     SW<      0   0%   0% [bioset]

   34     2 root     SW<      0   0%   0% [scsi_tmf_2]

   35     2 root     SW       0   0%   0% [scsi_eh_3]

   32     2 root     SW<      0   0%   0% [scsi_tmf_1]

 1060     2 root     SW<      0   0%   0% [ext4-rsv-conver]

   51     2 root     SW<      0   0%   0% [deferwq]

   13     2 root     SW<      0   0%   0% [md]

   36     2 root     SW<      0   0%   0% [scsi_tmf_3]

   50     2 root     SW<      0   0%   0% [raid5wq]

[Rolf Pedersen]

Hi,
I don't do raid but, reading this group list, I see some rather common new installations where the user doesn't wait for the initial disk check to finish.  With 4TB disks, that can be a long time and cpu load will be high.
That's just my impression and it might not relate to your problem at all.
Otherwise, the symptoms might be found in a search or some guidance in the documentation.  The alt-f group, linked in the footer of every email, contains the following info, in case you did not try that.

Alt-F is a free alternative firmware for the DLINK DNS-320/320L/321/323/325/327L and compatible NAS.

This site has a search facility at the page top, so please use it first before posting questions.

Also read the online help available on some webUI pages (hit theicon near the page title), the FAQ, or browse the Wiki.

Attach the relevant log files (System->Utilities->View Logs, System Configuration and others) and/or a screenshot of the Status or other relevant pages, not forgetting to refer your box model and hardware revision level.

Please use a descriptive subject line when posting, so others will easily find it and benefice with the discussion, and mark the question as "Answered", "Completed" or "No action needed" when appropriate.

“The quality of the answer is directly proportional to the amount of work you put into the question”.

Rolf

On 08/04/2016 06:34 AM, raywillia...@gmail.com wrote:

i also tryed turn off all the services and do manual umount but it allways says it busy, and i dont know with what

[root@STORE]# umount /mnt/md0

umount: can't umount /mnt/md0: Device or resource busy

--
You received this message because you are subscribed to the Google Groups "Alt-F" group.
To unsubscribe from this group and stop receiving emails from it, send an email to alt-f+un...@googlegroups.com.
Visit this group at https://groups.google.com/group/alt-f.
For more options, visit https://groups.google.com/d/optout.

[raywillia...@gmail.com]

thank you, but your answer is not relevant. 

I used search box and read FAQ before post.

I have posted enough info i think, i will wait for Norbert Horváth , he lead me right way i think.

dmesg

ata1: hard resetting link
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0xe000 SErr 0x0 action 0x6 frozen
ata1.00: cmd 61/00:68:40:f1:20/04:00:00:00:00/40 tag 13 ncq 524288 out
         res 40/00:30:78:30:01/00:02:00:00:00/40 Emask 0x4 (timeout)
ata1.00: cmd 61/00:70:40:f5:20/02:00:00:00:00/40 tag 14 ncq 262144 out
         res 40/00:08:90:64:00/00:00:00:00:00/40 Emask 0x4 (timeout)
ata1.00: cmd 60/08:78:d0:80:01/00:00:00:00:00/40 tag 15 ncq 4096 in
         res 40/00:08:90:64:00/00:00:00:00:00/40 Emask 0x4 (timeout)
ata1: hard resetting link
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: configured for UDMA/133
ata1: EH complete
ata1: limiting SATA link speed to 1.5 Gbps
ata1.00: exception Emask 0x100 SAct 0x1000000 SErr 0x400000 action 0x6 frozen
ata1.00: edma_err_cause=04000000 pp_flags=00000003
ata1.00: cmd 61/80:c0:40:aa:21/01:00:00:00:00/40 tag 24 ncq 196608 out
         res 51/84:80:40:aa:21/84:01:00:00:00/40 Emask 0x10 (ATA bus error)
ata1: hard resetting link
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata1.00: configured for UDMA/133
ata1: EH complete
EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled
md: md0: resync done.
RAID1 conf printout:
 --- wd:2 rd:2
 disk 0, wo:0, o:1, dev:sdb2
 disk 1, wo:0, o:1, dev:sda2
UDP: bad checksum. From 192.168.0.69:58137 to 255.255.255.255:1947 ulen 48
UDP: bad checksum. From 192.168.0.69:58137 to 255.255.255.255:1947 ulen 48
UDP: bad checksum. From 192.168.0.44:62322 to 255.255.255.255:1947 ulen 48
UDP: bad checksum. From 192.168.0.54:59284 to 255.255.255.255:1947 ulen 48
UDP: bad checksum. From 192.168.0.54:50683 to 192.168.0.255:1947 ulen 48
UDP: bad checksum. From 192.168.0.44:62322 to 255.255.255.255:1947 ulen 48
UDP: bad checksum. From 192.168.0.54:50683 to 255.255.255.255:1947 ulen 48
UDP: bad checksum. From 192.168.0.54:50683 to 255.255.255.255:1947 ulen 48
UDP: bad checksum. From 192.168.0.54:61211 to 255.255.255.255:1947 ulen 48

[Norbert Horváth]

top looks okay, "lsof /mnt/md0" shows what files are open under md0 and which processes opened them, this may also help EDIT: sorry, lsof may not work, at least mine does not run, like some lib is missing

"mount /mnt/md0 -n -o remount,ro" this remounts md0 read-only, after that fsck may start successfully

[Ray William]

Yes, lsof is not working.

This is what i faced next:

[root@STORE]# mount /mnt/md0 -n -o remount,ro

[root@STORE]# fsck /dev/md0 

fsck 1.41.14 (22-Dec-2010)

e2fsck 1.41.14 (22-Dec-2010)

/dev/md0 is mounted.  

WARNING!!!  The filesystem is mounted.   If you continue you ***WILL***

cause ***SEVERE*** filesystem damage.

Do you really want to continue (y/n)? 

Is it ok to answer YES?