Hi, a few weeks ago I'm having continuous unmounting of the volumes in my nas.
I do not understand the real cause of the problem, I only think it may depend on scanning the Plex server, but I'm not sure.
But I am sure the problem happen with NTFS volumes. In fact this happens with disks 3 and 4 configured MyArchive NTFS, and with the E-SATA unit, but it never happened with disk 2 configured in MyArchive EXT4.
Now I have the ADM 3.1.5.RJ42, but the problem already occurs from 2-3 releases.
Does anyone have similar problems? Can it depend on ADM or app updates?
Thank you in advance.
AS6104T MyArchive random unmount
Moderator: Lillian.W@AST
-
iobi
- Posts: 19
- youtube meble na wymiar Warszawa
- Joined: Mon Feb 13, 2017 6:00 pm
-
orion
- Posts: 3485
- Joined: Wed May 29, 2013 11:09 am
Re: AS6104T MyArchive random unmount
There should be detailed log in system. But you can only get it if you are familiar with Linux. I think the best way for you is to send a support request to asustor to check it.
-
iobi
- Posts: 19
- Joined: Mon Feb 13, 2017 6:00 pm
Re: AS6104T MyArchive random unmount
Hi everyone, after months I go back to my problem.
I wrote to the Asustor service that suggested me to reverse the discs, but it did not give results.
I upgraded the ram (2GB to 8GB) which mitigated the problem, now the unmount problems are only on the internal disks.
After a few months (personal problems and silence from assistance) I have rehearsed.
The result: by removing Disk 3 the problem does not exist. I hypothesized that being an old and "standard" disk could annoy the sata 4 slot and create the problem.
So I decided (with some acrobatics among nas) to install another hard drive: Western Digital Green 1TB (WD10EZRX). I waited for the normal on / off scheduling scheduled today, and unfortunately the problem was re-proposed. Always on Disc 4.
Also today I did another test: I again inverted the disks in the slots, and now the problem has moved to Disk 2.
I honestly do not understand what the cause may be.
Does anyone have any ideas ?! I think it was only to reset to factory conditions of the nas.
I wrote to the Asustor service that suggested me to reverse the discs, but it did not give results.
I upgraded the ram (2GB to 8GB) which mitigated the problem, now the unmount problems are only on the internal disks.
After a few months (personal problems and silence from assistance) I have rehearsed.
The result: by removing Disk 3 the problem does not exist. I hypothesized that being an old and "standard" disk could annoy the sata 4 slot and create the problem.
So I decided (with some acrobatics among nas) to install another hard drive: Western Digital Green 1TB (WD10EZRX). I waited for the normal on / off scheduling scheduled today, and unfortunately the problem was re-proposed. Always on Disc 4.
Also today I did another test: I again inverted the disks in the slots, and now the problem has moved to Disk 2.
I honestly do not understand what the cause may be.
Does anyone have any ideas ?! I think it was only to reset to factory conditions of the nas.
-
orion
- Posts: 3485
- Joined: Wed May 29, 2013 11:09 am
Re: AS6104T MyArchive random unmount
No ideas without more detailed information. So, you applied the original DRAM for your tests? Can you gather "dmesg" when the problem happened?
-
iobi
- Posts: 19
- Joined: Mon Feb 13, 2017 6:00 pm
Re: AS6104T MyArchive random unmount
Dear Orion, thank you for your reply.
No, for my tests I have not reinstalled the original RAM because from the upgrade I have never had any problems for my uses, and in any case the problem existed even before the update (and I sincerely prefer not to open the nas).
I do not know if I can capture a "dmesg" because I do not have linux / unix knowledge, I can impute some simple putty commands (learned on qnap) and nothing more.
No, for my tests I have not reinstalled the original RAM because from the upgrade I have never had any problems for my uses, and in any case the problem existed even before the update (and I sincerely prefer not to open the nas).
I do not know if I can capture a "dmesg" because I do not have linux / unix knowledge, I can impute some simple putty commands (learned on qnap) and nothing more.
-
orion
- Posts: 3485
- Joined: Wed May 29, 2013 11:09 am
Re: AS6104T MyArchive random unmount
I actually recommend you to apply the original DRAM to have another try. Although it's hardly caused by DRAM, there are still possibilities by it for this issue. (failures randomly especially)
You can run "dmesg" easily if you know how to use putty. You can login to NAS (using ssh on putty, user name: "root", password is the same as "admin"). Then type "dmesg". It will show you a lot of information. Simply paste the information here. Note: you need to execute the command AFTER the problem happened!
You can run "dmesg" easily if you know how to use putty. You can login to NAS (using ssh on putty, user name: "root", password is the same as "admin"). Then type "dmesg". It will show you a lot of information. Simply paste the information here. Note: you need to execute the command AFTER the problem happened!
Code: Select all
demsg
-
iobi
- Posts: 19
- Joined: Mon Feb 13, 2017 6:00 pm
Re: AS6104T MyArchive random unmount
OK, I promise - when I have more time - to do a test with the original ram.
For now I have done this test:
1) I waited for the scheduled restart of the nas (I had to set a shutdown and a start after 5 minutes, because from the purchase the reboot 1 time out of 4 went to block);
2) I did the "dmesg" when the volume was dismounted;
3) I reassembled the volume;
4) I made the "dmesg" WITH the volume mounted.
I can not attach .txt files, so I paste the text of the dmesg here
BEFORE
AFTER
For now I have done this test:
1) I waited for the scheduled restart of the nas (I had to set a shutdown and a start after 5 minutes, because from the purchase the reboot 1 time out of 4 went to block);
2) I did the "dmesg" when the volume was dismounted;
3) I reassembled the volume;
4) I made the "dmesg" WITH the volume mounted.
I can not attach .txt files, so I paste the text of the dmesg here
BEFORE
Code: Select all
[ 7.514585] IPVS: Registered protocols (TCP, UDP)
[ 7.519392] IPVS: Connection hash table configured (size=4096, memory=64Kbyte s)
[ 7.526807] IPVS: Creating netns size=1936 id=0
[ 7.531446] IPVS: ipvs loaded.
[ 7.534635] arp_tables: (C) 2002 David S. Miller
[ 7.539723] NET: Registered protocol family 10
[ 7.544725] NET: Registered protocol family 17
[ 7.549204] 8021q: 802.1Q VLAN Support v1.8
[ 7.553454] Key type dns_resolver registered
[ 7.558227] microcode: CPU0 sig=0x406c3, pf=0x1, revision=0x351
[ 7.564185] microcode: CPU1 sig=0x406c3, pf=0x1, revision=0x351
[ 7.570204] microcode: Microcode Update Driver: v2.01 <tigran@aivazian.fsnet. co.uk>, Peter Oruba
[ 7.579038] SSE version of gcm_enc/dec engaged.
[ 7.581890] usb 1-1: new full-speed USB device number 2 using xhci_hcd
[ 7.591337] registered taskstats version 1
[ 7.596606] Btrfs loaded, debug=on
[ 7.600921] Magic number: 3:435:178
[ 7.604606] hash matches /asustor/branch3_2_2019_01_17/x64_g3/source/linux- 4.4.24/drivers/base/power/main.c:1211
[ 7.615137] acpi device:0e: hash matches
[ 7.619107] platform: hash matches
[ 7.622629] console [netcon0] enabled
[ 7.626309] netconsole: network logging started
[ 7.630914] rtc_cmos 00:04: setting system clock to 2019-01-21 12:10:40 UTC ( 1548072640)
[ 7.639804] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[ 7.645823] EDD information not available.
[ 7.650066] PM: Hibernation image not present or could not be loaded.
[ 7.653209] Freeing unused kernel memory: 888K (ffffffff81ca6000 - ffffffff81 d84000)
[ 7.661208] Write protecting the kernel read-only data: 12288k
[ 7.668658] Freeing unused kernel memory: 1516K (ffff880001685000 - ffff88000 1800000)
[ 7.686303] Freeing unused kernel memory: 932K (ffff880001b17000 - ffff880001 c00000)
[ 7.764500] usb 1-1: New USB device found, idVendor=0a12, idProduct=0001
[ 7.771461] usb 1-1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 7.778858] usb 1-1: Product: CSR8510 A10
[ 7.936913] usb 1-3: new high-speed USB device number 3 using xhci_hcd
[ 8.110513] usb 1-3: New USB device found, idVendor=125f, idProduct=601a
[ 8.117492] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 8.124873] usb 1-3: Product: IUM01-512MFHL
[ 8.129224] usb 1-3: Manufacturer: ADATA
[ 8.133297] usb 1-3: SerialNumber: 120825741539000430
[ 8.139203] usb 1-3: ep 0x81 - rounding interval to 128 microframes, ep desc says 255 microframes
[ 8.148485] usb 1-3: ep 0x2 - rounding interval to 128 microframes, ep desc s ays 255 microframes
[ 8.158023] usb-storage 1-3:1.0: USB Mass Storage device detected
[ 8.168131] scsi host6: usb-storage 1-3:1.0
[ 8.325950] usb 1-4: new high-speed USB device number 4 using xhci_hcd
[ 8.498183] usb 1-4: New USB device found, idVendor=1a40, idProduct=0101
[ 8.505120] usb 1-4: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 8.512515] usb 1-4: Product: USB 2.0 Hub [MTT]
[ 8.517843] hub 1-4:1.0: USB hub found
[ 8.523071] hub 1-4:1.0: 4 ports detected
[ 9.174862] scsi 6:0:0:0: Direct-Access ADATA IUM01-512MFHL 0100 PQ : 0 ANSI: 0 CCS
[ 9.184807] sd 6:0:0:0: Attached scsi generic sg5 type 0
[ 9.191013] sd 6:0:0:0: [sdf] 1007616 512-byte logical blocks: (516 MB/492 Mi B)
[ 9.200688] sd 6:0:0:0: [sdf] Write Protect is off
[ 9.205730] sd 6:0:0:0: [sdf] Mode Sense: 43 00 00 00
[ 9.214380] sd 6:0:0:0: [sdf] No Caching mode page found
[ 9.220002] sd 6:0:0:0: [sdf] Assuming drive cache: write through
[ 9.253177] sdf: sdf1 sdf2 sdf3
[ 9.560406] sd 6:0:0:0: [sdf] Attached SCSI removable disk
[ 9.675104] EXT4-fs (sdf3): mounted filesystem with ordered data mode. Opts: (null)
[ 9.697185] nasmand (768): /proc/865/oom_adj is deprecated, please use /proc/ 865/oom_score_adj instead.
[ 9.811679] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 9.898829] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[ 10.022227] random: dd: uninitialized urandom read (512 bytes read, 126 bits of entropy available)
[ 10.094668] random: nonblocking pool is initialized
[ 10.102986] EXT4-fs (sdf3): mounted filesystem with ordered data mode. Opts: (null)
[ 10.824749] md: md0 stopped.
[ 10.832266] md: bind<sda2>
[ 10.857587] md/raid1:md0: active with 1 out of 4 mirrors
[ 10.863406] asustor add disk dev md0
[ 10.863474] md0: detected capacity change from 0 to 2145386496
[ 11.038012] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: ( null)
[ 11.096567] EXT4-fs (md0): re-mounted. Opts: (null)
[ 11.284817] EXT4-fs (loop0): mounted filesystem without journal. Opts: (null)
[ 11.312622] EXT4-fs (sdf3): mounted filesystem with ordered data mode. Opts: (null)
[ 13.631490] tg3 0000:03:00.0 eth0: Link is up at 1000 Mbps, full duplex
[ 13.638744] tg3 0000:03:00.0 eth0: Flow control is on for TX and on for RX
[ 13.646105] tg3 0000:03:00.0 eth0: EEE is enabled
[ 13.651286] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 19.187574] md: md126 stopped.
[ 19.216833] md: bind<sda3>
[ 19.229985] md/raid1:md126: active with 1 out of 4 mirrors
[ 19.235992] asustor add disk dev md126
[ 19.236051] md126: detected capacity change from 0 to 2145386496
[ 19.312909] Adding 2095100k swap on /dev/md126. Priority:-1 extents:1 across :2095100k
[ 19.355140] md: md1 stopped.
[ 19.360005] md: bind<sda4>
[ 19.387364] md/raid1:md1: active with 1 out of 1 mirrors
[ 19.393191] asustor add disk dev md1
[ 19.393252] md1: detected capacity change from 0 to 995506520064
[ 19.814886] EXT4-fs (md1): mounted filesystem with ordered data mode. Opts: u srjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv1
[ 20.840222] bridge: automatic filtering via arp/ip/ip6tables has been depreca ted. Update your scripts to load br_netfilter if you need this.
[ 22.418017] EXT4-fs (sdd2): mounted filesystem with ordered data mode. Opts: usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv1
[ 22.872785] jnl: driver (UFSD_HEAD lke_9.5.7_b449) loaded at ffffffffa002f000
[ 22.903088] ufsd: module license 'Commercial product' taints kernel.
[ 22.910200] Disabling lock debugging due to kernel taint
[ 22.947518] ufsd: driver (UFSD_HEAD lke_9.5.7_b449, acl, ioctl, sd2(5), tr, c ar) loaded at ffffffffa003e000
[ 22.947518] NTFSJ support included
[ 22.947518] Hfs+J support included
[ 22.947518] Build_for__Asustor_AS-6xx_k4.1.0_2016-02-01_lke_9.5.7_b449
[ 22.972703] ufsd: PAGE_SIZE=4K, THREAD_SIZE=16k
[ 22.979886] ufsd: Kernel .config hash: original 0x9d41e7bd, current matched.
[ 23.377637] ufsd: "mount" (sdc1): is mounted as NTFS at 2019-01-21 12:10:56
[ 28.584751] ufsd: "mount" (sde1): is mounted as NTFS at 2019-01-21 12:11:01
[ 28.929781] ufsd: "mount" (sdb1): is mounted as NTFS at 2019-01-21 12:11:01
[ 46.202078] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 62.694660] sys_stat: module is from the staging directory, the quality is un known, you have been warned.
[ 62.859970] [drm] Initialized drm 1.1.0 20060810
[ 63.058844] [drm] Memory usable by graphics device = 2048M
[ 63.064592] [drm] Replacing VGA console driver
[ 63.069617] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 63.076502] [drm] Driver supports precise vblank timestamp query.
[ 63.107826] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+me m,decodes=io+mem:owns=io+mem
[ 63.252061] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
[ 63.475331] acpi device:2b: registered as cooling_device3
[ 63.481159] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/L NXVIDEO:00/input/input7
[ 63.551343] i915 0000:00:02.0: No connectors reported connected with modes
[ 63.558915] [drm] Cannot find any crtc or sizes - going 1024x768
[ 63.576666] fbcon: inteldrmfb (fb0) is primary device
[ 63.576882] Console: switching to colour frame buffer device 128x48
[ 63.631460] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[ 63.659245] intelfb: intelfb_init
[ 63.659252] intelfb: Framebuffer driver for Intel(R) 830M/845G/852GM/855GM/86 5G/915G/915GM/945G/945GM/945GME/965G/965GM chipsets
[ 63.671939] intelfb: Version 0.9.6
[ 63.934541] snd_hda_intel 0000:00:1b.0: bound 0000:00:02.0 (ops i915_audio_co mponent_bind_ops [i915])
[ 63.983829] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC887-VD: line _outs=4 (0x14/0x16/0x15/0x17/0x0) type:line
[ 63.995202] snd_hda_codec_realtek hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0 /0x0/0x0)
[ 64.003438] snd_hda_codec_realtek hdaudioC0D0: hp_outs=1 (0x1b/0x0/0x0/0x0 /0x0)
[ 64.011317] snd_hda_codec_realtek hdaudioC0D0: mono: mono_out=0x0
[ 64.017897] snd_hda_codec_realtek hdaudioC0D0: dig-out=0x1e/0x0
[ 64.024353] snd_hda_codec_realtek hdaudioC0D0: inputs:
[ 64.029969] snd_hda_codec_realtek hdaudioC0D0: Rear Mic=0x18
[ 64.036297] snd_hda_codec_realtek hdaudioC0D0: Front Mic=0x19
[ 64.042774] snd_hda_codec_realtek hdaudioC0D0: Line=0x1a
[ 64.050048] snd_hda_codec_realtek hdaudioC0D0: CD=0x1c
[ 64.130753] input: HDA Intel PCH Rear Mic as /devices/pci0000:00/0000:00:1b.0 /sound/card0/input8
[ 64.167845] input: HDA Intel PCH Front Mic as /devices/pci0000:00/0000:00:1b. 0/sound/card0/input9
[ 64.253892] input: HDA Intel PCH Line as /devices/pci0000:00/0000:00:1b.0/sou nd/card0/input10
[ 64.344538] input: HDA Intel PCH Line Out Front as /devices/pci0000:00/0000:0 0:1b.0/sound/card0/input11
[ 64.454551] input: HDA Intel PCH Line Out Surround as /devices/pci0000:00/000 0:00:1b.0/sound/card0/input12
[ 64.525380] input: HDA Intel PCH Line Out CLFE as /devices/pci0000:00/0000:00 :1b.0/sound/card0/input13
[ 64.559072] input: HDA Intel PCH Line Out Side as /devices/pci0000:00/0000:00 :1b.0/sound/card0/input14
[ 64.588929] input: HDA Intel PCH Front Headphone as /devices/pci0000:00/0000: 00:1b.0/sound/card0/input15
[ 64.631163] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00 :1b.0/sound/card0/input16
[ 64.675972] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00 :1b.0/sound/card0/input17
[ 66.415938] iscsi-scst: ***WARNING***: CONFIG_TCP_ZERO_COPY_TRANSFER_COMPLETI ON_NOTIFICATION not enabled in your kernel. ISCSI-SCST will be working with not the best performance. Refer README file for details.
[ 66.824811] Loading iSCSI transport class v2.0-870.
[ 66.933471] iscsi: registered transport (tcp)
[ 70.390095] usbip_core: USB/IP Core v1.0.0
[ 70.467384] usbip-host 1-1:1.0: 1-1 is not in match_busid table... skip!
[ 70.474745] usbip-host 1-1:1.1: 1-1 is not in match_busid table... skip!
[ 70.482315] usbcore: registered new interface driver usbip-host
[ 70.488812] usbip_host: USB/IP Host Driver v1.0.0
[ 74.450127] cryptodev: driver 1.8 loaded.
[ 78.092592] Bluetooth: Core ver 2.21
[ 78.096364] NET: Registered protocol family 31
[ 78.101035] Bluetooth: HCI device and connection manager initialized
[ 78.107717] Bluetooth: HCI socket layer initialized
[ 78.112897] Bluetooth: L2CAP socket layer initialized
[ 78.118211] Bluetooth: SCO socket layer initialized
[ 78.162991] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 78.168563] Bluetooth: BNEP filters: protocol multicast
[ 78.174016] Bluetooth: BNEP socket layer initialized
[ 78.215387] Bluetooth: RFCOMM TTY layer initialized
[ 78.220523] Bluetooth: RFCOMM socket layer initialized
[ 78.225934] Bluetooth: RFCOMM ver 1.11
[ 78.272129] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 78.278642] Bluetooth: HIDP socket layer initialized
[ 78.400047] Bluetooth: HCI UART driver ver 2.3
[ 78.404693] Bluetooth: HCI UART protocol H4 registered
[ 78.410035] Bluetooth: HCI UART protocol BCSP registered
[ 78.415562] Bluetooth: HCI UART protocol LL registered
[ 78.420953] Bluetooth: HCI UART protocol ATH3K registered
[ 78.426569] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 78.433122] Bluetooth: HCI UART protocol Intel registered
[ 78.438770] Bluetooth: HCI UART protocol BCM registered
[ 78.444161] Bluetooth: HCI UART protocol QCA registered
[ 78.534606] usbcore: registered new interface driver btusb
[ 79.169031] Bluetooth: Unable to create CMAC crypto context
[ 87.113718] usbcore: registered new interface driver snd-usb-audio
>[ 170.260647] udevd[5766]: starting version 3.2
>[ 170.288363] udevd[5775]: starting eudev-3.2
Code: Select all
[ 7.526807] IPVS: Creating netns size=1936 id=0
[ 7.531446] IPVS: ipvs loaded.
[ 7.534635] arp_tables: (C) 2002 David S. Miller
[ 7.539723] NET: Registered protocol family 10
[ 7.544725] NET: Registered protocol family 17
[ 7.549204] 8021q: 802.1Q VLAN Support v1.8
[ 7.553454] Key type dns_resolver registered
[ 7.558227] microcode: CPU0 sig=0x406c3, pf=0x1, revision=0x351
[ 7.564185] microcode: CPU1 sig=0x406c3, pf=0x1, revision=0x351
[ 7.570204] microcode: Microcode Update Driver: v2.01 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
[ 7.579038] SSE version of gcm_enc/dec engaged.
[ 7.581890] usb 1-1: new full-speed USB device number 2 using xhci_hcd
[ 7.591337] registered taskstats version 1
[ 7.596606] Btrfs loaded, debug=on
[ 7.600921] Magic number: 3:435:178
[ 7.604606] hash matches /asustor/branch3_2_2019_01_17/x64_g3/source/linux-4.4.24/drivers/base/power/main.c:1211
[ 7.615137] acpi device:0e: hash matches
[ 7.619107] platform: hash matches
[ 7.622629] console [netcon0] enabled
[ 7.626309] netconsole: network logging started
[ 7.630914] rtc_cmos 00:04: setting system clock to 2019-01-21 12:10:40 UTC (1548072640)
[ 7.639804] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[ 7.645823] EDD information not available.
[ 7.650066] PM: Hibernation image not present or could not be loaded.
[ 7.653209] Freeing unused kernel memory: 888K (ffffffff81ca6000 - ffffffff81d84000)
[ 7.661208] Write protecting the kernel read-only data: 12288k
[ 7.668658] Freeing unused kernel memory: 1516K (ffff880001685000 - ffff880001800000)
[ 7.686303] Freeing unused kernel memory: 932K (ffff880001b17000 - ffff880001c00000)
[ 7.764500] usb 1-1: New USB device found, idVendor=0a12, idProduct=0001
[ 7.771461] usb 1-1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 7.778858] usb 1-1: Product: CSR8510 A10
[ 7.936913] usb 1-3: new high-speed USB device number 3 using xhci_hcd
[ 8.110513] usb 1-3: New USB device found, idVendor=125f, idProduct=601a
[ 8.117492] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 8.124873] usb 1-3: Product: IUM01-512MFHL
[ 8.129224] usb 1-3: Manufacturer: ADATA
[ 8.133297] usb 1-3: SerialNumber: 120825741539000430
[ 8.139203] usb 1-3: ep 0x81 - rounding interval to 128 microframes, ep desc says 255 microframes
[ 8.148485] usb 1-3: ep 0x2 - rounding interval to 128 microframes, ep desc says 255 microframes
[ 8.158023] usb-storage 1-3:1.0: USB Mass Storage device detected
[ 8.168131] scsi host6: usb-storage 1-3:1.0
[ 8.325950] usb 1-4: new high-speed USB device number 4 using xhci_hcd
[ 8.498183] usb 1-4: New USB device found, idVendor=1a40, idProduct=0101
[ 8.505120] usb 1-4: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 8.512515] usb 1-4: Product: USB 2.0 Hub [MTT]
[ 8.517843] hub 1-4:1.0: USB hub found
[ 8.523071] hub 1-4:1.0: 4 ports detected
[ 9.174862] scsi 6:0:0:0: Direct-Access ADATA IUM01-512MFHL 0100 PQ: 0 ANSI: 0 CCS
[ 9.184807] sd 6:0:0:0: Attached scsi generic sg5 type 0
[ 9.191013] sd 6:0:0:0: [sdf] 1007616 512-byte logical blocks: (516 MB/492 MiB)
[ 9.200688] sd 6:0:0:0: [sdf] Write Protect is off
[ 9.205730] sd 6:0:0:0: [sdf] Mode Sense: 43 00 00 00
[ 9.214380] sd 6:0:0:0: [sdf] No Caching mode page found
[ 9.220002] sd 6:0:0:0: [sdf] Assuming drive cache: write through
[ 9.253177] sdf: sdf1 sdf2 sdf3
[ 9.560406] sd 6:0:0:0: [sdf] Attached SCSI removable disk
[ 9.675104] EXT4-fs (sdf3): mounted filesystem with ordered data mode. Opts: (null)
[ 9.697185] nasmand (768): /proc/865/oom_adj is deprecated, please use /proc/865/oom_score_adj instead.
[ 9.811679] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 9.898829] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[ 10.022227] random: dd: uninitialized urandom read (512 bytes read, 126 bits of entropy available)
[ 10.094668] random: nonblocking pool is initialized
[ 10.102986] EXT4-fs (sdf3): mounted filesystem with ordered data mode. Opts: (null)
[ 10.824749] md: md0 stopped.
[ 10.832266] md: bind<sda2>
[ 10.857587] md/raid1:md0: active with 1 out of 4 mirrors
[ 10.863406] asustor add disk dev md0
[ 10.863474] md0: detected capacity change from 0 to 2145386496
[ 11.038012] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
[ 11.096567] EXT4-fs (md0): re-mounted. Opts: (null)
[ 11.284817] EXT4-fs (loop0): mounted filesystem without journal. Opts: (null)
[ 11.312622] EXT4-fs (sdf3): mounted filesystem with ordered data mode. Opts: (null)
[ 13.631490] tg3 0000:03:00.0 eth0: Link is up at 1000 Mbps, full duplex
[ 13.638744] tg3 0000:03:00.0 eth0: Flow control is on for TX and on for RX
[ 13.646105] tg3 0000:03:00.0 eth0: EEE is enabled
[ 13.651286] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 19.187574] md: md126 stopped.
[ 19.216833] md: bind<sda3>
[ 19.229985] md/raid1:md126: active with 1 out of 4 mirrors
[ 19.235992] asustor add disk dev md126
[ 19.236051] md126: detected capacity change from 0 to 2145386496
[ 19.312909] Adding 2095100k swap on /dev/md126. Priority:-1 extents:1 across:2095100k
[ 19.355140] md: md1 stopped.
[ 19.360005] md: bind<sda4>
[ 19.387364] md/raid1:md1: active with 1 out of 1 mirrors
[ 19.393191] asustor add disk dev md1
[ 19.393252] md1: detected capacity change from 0 to 995506520064
[ 19.814886] EXT4-fs (md1): mounted filesystem with ordered data mode. Opts: usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv1
[ 20.840222] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
[ 22.418017] EXT4-fs (sdd2): mounted filesystem with ordered data mode. Opts: usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv1
[ 22.872785] jnl: driver (UFSD_HEAD lke_9.5.7_b449) loaded at ffffffffa002f000
[ 22.903088] ufsd: module license 'Commercial product' taints kernel.
[ 22.910200] Disabling lock debugging due to kernel taint
[ 22.947518] ufsd: driver (UFSD_HEAD lke_9.5.7_b449, acl, ioctl, sd2(5), tr, car) loaded at ffffffffa003e000
[ 22.947518] NTFSJ support included
[ 22.947518] Hfs+J support included
[ 22.947518] Build_for__Asustor_AS-6xx_k4.1.0_2016-02-01_lke_9.5.7_b449
[ 22.972703] ufsd: PAGE_SIZE=4K, THREAD_SIZE=16k
[ 22.979886] ufsd: Kernel .config hash: original 0x9d41e7bd, current matched.
[ 23.377637] ufsd: "mount" (sdc1): is mounted as NTFS at 2019-01-21 12:10:56
[ 28.584751] ufsd: "mount" (sde1): is mounted as NTFS at 2019-01-21 12:11:01
[ 28.929781] ufsd: "mount" (sdb1): is mounted as NTFS at 2019-01-21 12:11:01
[ 46.202078] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 62.694660] sys_stat: module is from the staging directory, the quality is unknown, you have been warned.
[ 62.859970] [drm] Initialized drm 1.1.0 20060810
[ 63.058844] [drm] Memory usable by graphics device = 2048M
[ 63.064592] [drm] Replacing VGA console driver
[ 63.069617] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 63.076502] [drm] Driver supports precise vblank timestamp query.
[ 63.107826] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[ 63.252061] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
[ 63.475331] acpi device:2b: registered as cooling_device3
[ 63.481159] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input7
[ 63.551343] i915 0000:00:02.0: No connectors reported connected with modes
[ 63.558915] [drm] Cannot find any crtc or sizes - going 1024x768
[ 63.576666] fbcon: inteldrmfb (fb0) is primary device
[ 63.576882] Console: switching to colour frame buffer device 128x48
[ 63.631460] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[ 63.659245] intelfb: intelfb_init
[ 63.659252] intelfb: Framebuffer driver for Intel(R) 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/945GME/965G/965GM chipsets
[ 63.671939] intelfb: Version 0.9.6
[ 63.934541] snd_hda_intel 0000:00:1b.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[ 63.983829] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC887-VD: line_outs=4 (0x14/0x16/0x15/0x17/0x0) type:line
[ 63.995202] snd_hda_codec_realtek hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[ 64.003438] snd_hda_codec_realtek hdaudioC0D0: hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
[ 64.011317] snd_hda_codec_realtek hdaudioC0D0: mono: mono_out=0x0
[ 64.017897] snd_hda_codec_realtek hdaudioC0D0: dig-out=0x1e/0x0
[ 64.024353] snd_hda_codec_realtek hdaudioC0D0: inputs:
[ 64.029969] snd_hda_codec_realtek hdaudioC0D0: Rear Mic=0x18
[ 64.036297] snd_hda_codec_realtek hdaudioC0D0: Front Mic=0x19
[ 64.042774] snd_hda_codec_realtek hdaudioC0D0: Line=0x1a
[ 64.050048] snd_hda_codec_realtek hdaudioC0D0: CD=0x1c
[ 64.130753] input: HDA Intel PCH Rear Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input8
[ 64.167845] input: HDA Intel PCH Front Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
[ 64.253892] input: HDA Intel PCH Line as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
[ 64.344538] input: HDA Intel PCH Line Out Front as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
[ 64.454551] input: HDA Intel PCH Line Out Surround as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12
[ 64.525380] input: HDA Intel PCH Line Out CLFE as /devices/pci0000:00/0000:00:1b.0/sound/card0/input13
[ 64.559072] input: HDA Intel PCH Line Out Side as /devices/pci0000:00/0000:00:1b.0/sound/card0/input14
[ 64.588929] input: HDA Intel PCH Front Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input15
[ 64.631163] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input16
[ 64.675972] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input17
[ 66.415938] iscsi-scst: ***WARNING***: CONFIG_TCP_ZERO_COPY_TRANSFER_COMPLETION_NOTIFICATION not enabled in your kernel. ISCSI-SCST will be working with not the best performance. Refer README file for details.
[ 66.824811] Loading iSCSI transport class v2.0-870.
[ 66.933471] iscsi: registered transport (tcp)
[ 70.390095] usbip_core: USB/IP Core v1.0.0
[ 70.467384] usbip-host 1-1:1.0: 1-1 is not in match_busid table... skip!
[ 70.474745] usbip-host 1-1:1.1: 1-1 is not in match_busid table... skip!
[ 70.482315] usbcore: registered new interface driver usbip-host
[ 70.488812] usbip_host: USB/IP Host Driver v1.0.0
[ 74.450127] cryptodev: driver 1.8 loaded.
[ 78.092592] Bluetooth: Core ver 2.21
[ 78.096364] NET: Registered protocol family 31
[ 78.101035] Bluetooth: HCI device and connection manager initialized
[ 78.107717] Bluetooth: HCI socket layer initialized
[ 78.112897] Bluetooth: L2CAP socket layer initialized
[ 78.118211] Bluetooth: SCO socket layer initialized
[ 78.162991] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 78.168563] Bluetooth: BNEP filters: protocol multicast
[ 78.174016] Bluetooth: BNEP socket layer initialized
[ 78.215387] Bluetooth: RFCOMM TTY layer initialized
[ 78.220523] Bluetooth: RFCOMM socket layer initialized
[ 78.225934] Bluetooth: RFCOMM ver 1.11
[ 78.272129] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 78.278642] Bluetooth: HIDP socket layer initialized
[ 78.400047] Bluetooth: HCI UART driver ver 2.3
[ 78.404693] Bluetooth: HCI UART protocol H4 registered
[ 78.410035] Bluetooth: HCI UART protocol BCSP registered
[ 78.415562] Bluetooth: HCI UART protocol LL registered
[ 78.420953] Bluetooth: HCI UART protocol ATH3K registered
[ 78.426569] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 78.433122] Bluetooth: HCI UART protocol Intel registered
[ 78.438770] Bluetooth: HCI UART protocol BCM registered
[ 78.444161] Bluetooth: HCI UART protocol QCA registered
[ 78.534606] usbcore: registered new interface driver btusb
[ 79.169031] Bluetooth: Unable to create CMAC crypto context
[ 87.113718] usbcore: registered new interface driver snd-usb-audio
>[ 170.260647] udevd[5766]: starting version 3.2
>[ 170.288363] udevd[5775]: starting eudev-3.2
root@NAS-SERVER:/volume1/.@root #
Last edited by iobi on Mon Jan 28, 2019 5:28 am, edited 1 time in total.
-
orion
- Posts: 3485
- Joined: Wed May 29, 2013 11:09 am
Re: AS6104T MyArchive random unmount
I don't understand your procedure-1. I suppose that you restarted the NAS, then you saw MyArchive drives mounted. You got the first "dmesg". After a short period, you found those MyArchive drives dismounted unexpectedly. You got the second "dmesg". Is that right?
Based on the messages above, it seems that you own 3 MyArchive drives (NTFS). Is it correct?
However there are no hardware events during the time from the first dmesg to the second dmesg. It means that there are no hardware events (hardware signal bad, or user un-plug cable, ...) to generate the dismounted actions. If you did the procedure as I mentioned exactly, that should mean the dismounted actions are caused by software: user did the actions from UI or some bugs in software. "dmesg" cannot record those 2 actions. I believe you can only get supports from asustor.
By the way, you can use "Code" block to enclose your message. That should be a correct way for a long text.
Code: Select all
[ 23.377637] ufsd: "mount" (sdc1): is mounted as NTFS at 2019-01-21 12:10:56
[ 28.584751] ufsd: "mount" (sde1): is mounted as NTFS at 2019-01-21 12:11:01
[ 28.929781] ufsd: "mount" (sdb1): is mounted as NTFS at 2019-01-21 12:11:01
However there are no hardware events during the time from the first dmesg to the second dmesg. It means that there are no hardware events (hardware signal bad, or user un-plug cable, ...) to generate the dismounted actions. If you did the procedure as I mentioned exactly, that should mean the dismounted actions are caused by software: user did the actions from UI or some bugs in software. "dmesg" cannot record those 2 actions. I believe you can only get supports from asustor.
By the way, you can use "Code" block to enclose your message. That should be a correct way for a long text.
-
iobi
- Posts: 19
- Joined: Mon Feb 13, 2017 6:00 pm
Re: AS6104T MyArchive random unmount
Dear Orion, I apologize, maybe I was a bit chaotic in the description.
I try to rearrange the story.
I have four disks on the nas:
Disk1 - System
Disk2 - MyArchive (NTFS)
Disk3 - MyArchive (EXT4) (I want to migrate it to NTFS)
Disk4 - MyArchive (NTFS)
Note: the problem has always happened on NTFS.
The procedure was this:
1) restart of the nas
2) I find Disk2 (MyArchive3) NOT mounted
3) launch 1st dmesg
4) mounted the disk2
5) launch 2nd dmesg
STOP - no problem before the next restart
So from the code it does not appear that I have mounted the volume (point 4 of the procedure)? Did I get it right? I apologize but to understand some terms I use google translate and I'm afraid that something will be distorted.
I want to add a detail.
It happened during my tests, and again this weekend because I turned off my whole ecosystem.
IF I start the nas WITHOUT the E-SATA2 disk (WD500KS-00MNB0 on Sharkoon QuickPortHome), the problem does not happen.
(I can not try any more discs on the Sharkoon box because I do not have any more).
Is a connection possible?
PS: sorry for the text too long, now I correct with your suggestion
I try to rearrange the story.
I have four disks on the nas:
Disk1 - System
Disk2 - MyArchive (NTFS)
Disk3 - MyArchive (EXT4) (I want to migrate it to NTFS)
Disk4 - MyArchive (NTFS)
Note: the problem has always happened on NTFS.
The procedure was this:
1) restart of the nas
2) I find Disk2 (MyArchive3) NOT mounted
3) launch 1st dmesg
4) mounted the disk2
5) launch 2nd dmesg
STOP - no problem before the next restart
So from the code it does not appear that I have mounted the volume (point 4 of the procedure)? Did I get it right? I apologize but to understand some terms I use google translate and I'm afraid that something will be distorted.
I want to add a detail.
It happened during my tests, and again this weekend because I turned off my whole ecosystem.
IF I start the nas WITHOUT the E-SATA2 disk (WD500KS-00MNB0 on Sharkoon QuickPortHome), the problem does not happen.
(I can not try any more discs on the Sharkoon box because I do not have any more).
Is a connection possible?
PS: sorry for the text too long, now I correct with your suggestion
-
orion
- Posts: 3485
- Joined: Wed May 29, 2013 11:09 am
Re: AS6104T MyArchive random unmount
Ok, your information is pretty clear now. Your "sde1" should be e-SATA disk (NTFS). NAS detected this e-SATA file system after 28.5 seconds. However NAS detected the previous NTFS drive (sdc1) after 23.3 seconds. It means NAS takes 5 seconds to bring the e-SATA drive in (slow, but it should be all right).
Nothing wrong with those hardware devices. I guess it's caused by software booting up processes.
The booting processes might not put records in "dmesg" messages. So the message shows no more details about it. I believe you can only get helps from asustor directly to find out what's the real problem.
Code: Select all
[ 23.377637] ufsd: "mount" (sdc1): is mounted as NTFS at 2019-01-21 12:10:56
[ 28.584751] ufsd: "mount" (sde1): is mounted as NTFS at 2019-01-21 12:11:01
The booting processes might not put records in "dmesg" messages. So the message shows no more details about it. I believe you can only get helps from asustor directly to find out what's the real problem.