1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
Dismiss Notice

Welcome To SNBForums

SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.

If you'd like to post a question, simply register and have at it!

While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!

Asus RT-AC86U signature updates and reboots

Discussion in 'ASUS AC Routers & Adapters' started by lalala2, Sep 4, 2018.

  1. lalala2

    lalala2 New Around Here

    Joined:
    Jan 6, 2018
    Messages:
    8
    It appears that the RT-AC86U reboots every time there is a signature version upgrade, which happens every several days.

    This is info from the firmware upgrade tab of firmware 3.0.0.4.384_21140:
    Signature Version
    2.086 Updated : 2018/09/02 01:37

    I need a stable router that doesn't reboot. Is there a way to turn off these signature updates?
     
  2. OzarkEdge

    OzarkEdge Very Senior Member

    Joined:
    Feb 14, 2018
    Messages:
    1,051
    Location:
    USA
    Where does this appear? I haven't noticed this on the four 86Us I've worked on.

    OE
     
  3. RMerlin

    RMerlin Super Moderator

    Joined:
    Apr 14, 2012
    Messages:
    29,069
    Location:
    Canada
    It only appears if you use any of the Trend Micro-powered features that requires it (for instance Adaptive QoS).
     
  4. OzarkEdge

    OzarkEdge Very Senior Member

    Joined:
    Feb 14, 2018
    Messages:
    1,051
    Location:
    USA
    Thanks... that explains that! I hope ASUS doesn't think of anything else to cram into their routers! :rolleyes:

    OE
     
  5. GuruGuy

    GuruGuy Guest

    Why does the router need to reboot for a signature update? If a computer needed a reboot for every antivirus signature update, it would be rebooting constantly all day long every day
     
  6. RMerlin

    RMerlin Super Moderator

    Joined:
    Apr 14, 2012
    Messages:
    29,069
    Location:
    Canada
    It doesn't. What indicates the router actually rebooted?
     
  7. GuruGuy

    GuruGuy Guest

    That's a question for the OP
     
  8. CriticJay

    CriticJay Occasional Visitor

    Joined:
    May 30, 2018
    Messages:
    33
    Exactly. Mine does not reboot for signature updates, so not sure what is up with the OP's router.
     
  9. RMerlin

    RMerlin Super Moderator

    Joined:
    Apr 14, 2012
    Messages:
    29,069
    Location:
    Canada
    Some people confuse a reboot with a restart of the wireless stack, that's why I was asking.
     
  10. lalala2

    lalala2 New Around Here

    Joined:
    Jan 6, 2018
    Messages:
    8
    The uptime counter resets and the system log shows the time resetting to a prior period and then finally coming back to the present day.

    However, I just looked at it again and it seems the router resets every 4-5 days independently of the signature version update. There seems to be some other issue with my router.
     
  11. indark

    indark Senior Member

    Joined:
    Jan 17, 2014
    Messages:
    202
    maybe you have enabled the scheduler for reboot?
    to check,
    it's under admin -> system -> Enable Reboot Scheduler

    if it's not the case,
    I will try to do a power cycle + nvram clear and reconfigure the router from there

    power of the router for 30+ sec, hold wps button while powering on
    wait till power led start blinking/flashing then release the wps button
    wait till it's reboot and reconfigure from there.
     
  12. Gingernut

    Gingernut Senior Member

    Joined:
    Sep 18, 2009
    Messages:
    258
    Reviving this thread with hopes to find out the reason behind these reboots.

    The longest uptime I've been able to achieve with the 86U is around 10 days, normally when I check it's uptime it's either a few days or just hours, and for some unknown reason it has rebooted.

    This happens on every release that I'm aware of, I've done a full factory reset and auto reboot scheduler is and alwasys has been disabled.

    Possible causes:

    FreshTJ's QOS script?

    Skynet firewall script?

    USB connected hard drive?

    Is there a method to debug this and gather more information without cracking it open and connecting a serial cable?

    Here's a snippet from the router's log just before a reboot.

    Code:
    Nov 16 23:09:11 dnsmasq-dhcp[800]: DHCPREQUEST(br0) 192.168.1.181 00:bb:3a:8f:16:d0
    Nov 16 23:09:11 dnsmasq-dhcp[800]: DHCPACK(br0) 192.168.1.181 00:bb:3a:8f:16:d0
    Nov 16 23:09:17 dnsmasq-dhcp[800]: DHCPREQUEST(br0) 192.168.1.186 b0:65:bd:9b:08:59
    Nov 16 23:09:17 dnsmasq-dhcp[800]: DHCPACK(br0) 192.168.1.186 b0:65:bd:9b:08:59 iPad-41
    May  5 07:05:05 syslogd started: BusyBox v1.25.1
    May  5 07:05:05 kernel: klogd started: BusyBox v1.25.1 (2018-11-10 00:23:56 CET)
    May  5 07:05:05 kernel: Booting Linux on physical CPU 0x0
    May  5 07:05:05 kernel: Linux version 4.1.27 ([email protected]) (gcc version 5.3.0 (Buildroot 2016.02) ) #2 SMP PREEMPT Sat Nov 10 01:28:06 CET 2018
    May  5 07:05:05 kernel: CPU: AArch64 Processor [420f1000] revision 0
    May  5 07:05:05 kernel: Detected VIPT I-cache on CPU0
    May  5 07:05:05 kernel: alternatives: enabling workaround for ARM erratum 845719
    May  5 07:05:05 kernel: PERCPU: Embedded 15 pages/cpu @ffffffc01ffd6000 s21376 r8192 d31872 u61440
    May  5 07:05:05 kernel: Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 122112
    May  5 07:05:05 kernel: Kernel command line: coherent_pool=1M cpuidle_sysfs_switch
    May  5 07:05:05 kernel: PID hash table entries: 2048 (order: 2, 16384 bytes)
    May  5 07:05:05 kernel: Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
    May  5 07:05:05 kernel: Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
    May  5 07:05:05 kernel: Memory: 440208K/495616K available (4678K kernel code, 301K rwdata, 1568K rodata, 228K init, 471K bss, 55408K reserved, 0K cma-reserved)
    May  5 07:05:05 kernel: Virtual kernel memory layout:
    May  5 07:05:05 kernel:     vmalloc : 0xffffff8000000000 - 0xffffffbdffff0000   (   247 GB)
    May  5 07:05:05 kernel:     vmemmap : 0xffffffbe00000000 - 0xffffffbfc0000000   (     7 GB maximum)
    May  5 07:05:05 kernel:               0xffffffbe00000000 - 0xffffffbe00700000   (     7 MB actual)
    May  5 07:05:05 kernel:     fixed   : 0xffffffbffabfd000 - 0xffffffbffac00000   (    12 KB)
    May  5 07:05:05 kernel:     PCI I/O : 0xffffffbffae00000 - 0xffffffbffbe00000   (    16 MB)
    May  5 07:05:05 kernel:     modules : 0xffffffbffc000000 - 0xffffffc000000000   (    64 MB)
    May  5 07:05:05 kernel:     memory  : 0xffffffc000000000 - 0xffffffc020000000   (   512 MB)
    May  5 07:05:05 kernel:       .init : 0xffffffc00069b000 - 0xffffffc0006d4000   (   228 KB)
    May  5 07:05:05 kernel:       .text : 0xffffffc000080000 - 0xffffffc00069a274   (  6249 KB)
    May  5 07:05:05 kernel:       .data : 0xffffffc0006d5000 - 0xffffffc000720680   (   302 KB)
    May  5 07:05:05 kernel: Preemptible hierarchical RCU implementation.
    May  5 07:05:05 kernel:     RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
    May  5 07:05:05 kernel: RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
    May  5 07:05:05 kernel: NR_IRQS:64 nr_irqs:64 0
    May  5 07:05:05 kernel: Architected cp15 timer(s) running at 50.00MHz (phys).
    May  5 07:05:05 kernel: clocksource arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0xb8812736b, max_idle_ns: 440795202655 ns
    May  5 07:05:05 kernel: sched_clock: 56 bits at 50MHz, resolution 20ns, wraps every 4398046511100ns
    May  5 07:05:05 kernel: BRCM Legacy Drivers' Helper, all legacy drivers' IO memories/interrupts should be remapped here
    May  5 07:05:05 kernel:      Remapping interrupts...
    May  5 07:05:05 kernel:              hwirq      virq
    May  5 07:05:05 kernel:                61         5
    May  5 07:05:05 kernel:                64         6
    May  5 07:05:05 kernel:                66         7
    May  5 07:05:05 kernel:                91         8
    May  5 07:05:05 kernel:                92         9
    May  5 07:05:05 kernel:                93        10
    May  5 07:05:05 kernel:                77        11
    May  5 07:05:05 kernel:                78        12
    May  5 07:05:05 kernel:                79        13
    May  5 07:05:05 kernel:                80        14
    May  5 07:05:05 kernel:                81        15
    May  5 07:05:05 kernel:                82        16
    May  5 07:05:05 kernel:                83        17
    May  5 07:05:05 kernel:                84        18
    May  5 07:05:05 kernel:                85        19
    May  5 07:05:05 kernel:                86        20
    May  5 07:05:05 kernel:                88        21
    May  5 07:05:05 kernel:                96        22
    May  5 07:05:05 kernel:                97        23
    May  5 07:05:05 kernel:                98        24
    May  5 07:05:05 kernel:                99        25
    May  5 07:05:05 kernel:               118        26
    May  5 07:05:05 kernel:               119        27
    May  5 07:05:05 kernel:               106        28
    May  5 07:05:05 kernel:               104        29
    May  5 07:05:05 kernel:               105        30
    May  5 07:05:05 kernel:                76        31
    May  5 07:05:05 kernel:               120        32
    May  5 07:05:05 kernel:               110        33
    May  5 07:05:05 kernel:               148        34
    May  5 07:05:05 kernel:               154        35
    May  5 07:05:05 kernel:               155        36
    May  5 07:05:05 kernel:               156        37
    May  5 07:05:05 kernel:               157        38
    May  5 07:05:05 kernel:               158        39
    May  5 07:05:05 kernel:               159        40
    May  5 07:05:05 kernel:                69        41
    May  5 07:05:05 kernel:      Remapping IO memories...
    May  5 07:05:05 kernel:              phys              virt          size
    May  5 07:05:05 kernel:        00000000ff800000  ffffff8000008000  00003000
    May  5 07:05:05 kernel:        00000000ff858000  ffffff8000002000  00001000
    May  5 07:05:05 kernel:        00000000ff85a000  ffffff800000c000  00001000
    May  5 07:05:05 kernel:        00000000ffe00000  ffffff8000040000  00020000
    May  5 07:05:05 kernel:        0000000080002000  ffffff800000e000  00001000
    May  5 07:05:05 kernel:        0000000080018000  ffffff8000010000  00004000
    May  5 07:05:05 kernel:        0000000080200000  ffffff8000018000  00005000
    May  5 07:05:05 kernel:        0000000080280000  ffffff8000016000  00001000
    May  5 07:05:05 kernel:        0000000082200000  ffffff8000080000  00100000
    May  5 07:05:05 kernel:        0000000080080000  ffffff8000200000  00050000
    May  5 07:05:05 kernel:        0000000080008000  ffffff8000020000  00003fff
    May  5 07:05:05 kernel:        000000008000c000  ffffff8000028000  00003fff
    May  5 07:05:05 kernel:        0000000081060000  ffffff8000030000  00004000
    May  5 07:05:05 kernel:        0000000080100000  ffffff8000038000  00002000
    May  5 07:05:05 kernel:        0000000080010000  ffffff800001e000  00001000
    May  5 07:05:05 kernel:        000000008001d000  ffffff800003c000  00001010
    May  5 07:05:05 kernel:        000000008001c000  ffffff8000026000  00000448
    May  5 07:05:05 kernel: console [ttyS0] enabled
    May  5 07:05:05 kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 100.00 BogoMIPS (lpj=500000)
    May  5 07:05:05 kernel: pid_max: default: 32768 minimum: 301
    May  5 07:05:05 kernel: Mount-cache hash table entries: 1024 (order: 1, 8192 bytes)
    May  5 07:05:05 kernel: Mountpoint-cache hash table entries: 1024 (order: 1, 8192 bytes)
    May  5 07:05:05 kernel: --Kernel Config--
    May  5 07:05:05 kernel:   SMP=1
    May  5 07:05:05 kernel:   PREEMPT=1
    May  5 07:05:05 kernel:   DEBUG_SPINLOCK=0
    May  5 07:05:05 kernel:   DEBUG_MUTEXES=0
    May  5 07:05:05 kernel: Broadcom Logger v0.1
    May  5 07:05:05 kernel: creating mapping for reserved memory phys 0x0c400000 virt 0xffffffc00c400000 size 0x00e00000 for dhd1
    May  5 07:05:05 kernel: Do not need to create mapping for reserved memory phys 0x0e000000 size 0x02000000 for buffer
    May  5 07:05:05 kernel: creating mapping for reserved memory phys 0x0d200000 virt 0xffffffc00d200000 size 0x00e00000 for flow
    May  5 07:05:05 kernel: pmc_init:PMC using DQM mode
    May  5 07:05:05 kernel: CPU1: Booted secondary processor
    May  5 07:05:05 kernel: Detected VIPT I-cache on CPU1
    May  5 07:05:05 kernel: Brought up 2 CPUs
    May  5 07:05:05 kernel: SMP: Total of 2 processors activated.
    May  5 07:05:05 kernel: CPU: All CPU(s) started at EL2
    May  5 07:05:05 kernel: alternatives: patching kernel code
    May  5 07:05:05 kernel: devtmpfs: initialized
    May  5 07:05:05 kernel: clocksource jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
    May  5 07:05:05 kernel: NET: Registered protocol family 16
    May  5 07:05:05 kernel: cpuidle: using governor ladder
    May  5 07:05:05 kernel: cpuidle: using governor menu
    May  5 07:05:05 kernel: vdso: 2 pages (1 code @ ffffffc0006dd000, 1 data @ ffffffc0006dc000)
    May  5 07:05:05 kernel: DMA: preallocated 1024 KiB pool for atomic allocations
    May  5 07:05:05 kernel: ACPI: Interpreter disabled.
    May  5 07:05:05 kernel: bcmhs_spi bcmhs_spi.1: master is unqueued, this is deprecated
    May  5 07:05:05 kernel: skbFreeTask created successfully
    May  5 07:05:05 kernel: gbpm_do_work scheduled
    May  5 07:05:05 kernel: ^[[0;34mBLOG v3.0 Initialized^[[0m
    May  5 07:05:05 kernel: BLOG Rule v1.0 Initialized
    May  5 07:05:05 kernel: Broadcom IQoS v0.1 initialized
    May  5 07:05:05 kernel: Broadcom GBPM v0.1 initialized
    May  5 07:05:05 kernel: Switched to clocksource arch_sys_counter

    Any help is welcome.
     
  13. lalala2

    lalala2 New Around Here

    Joined:
    Jan 6, 2018
    Messages:
    8
    I have none of those addons or scripts and the reboots still happen.
     
    Gingernut likes this.
  14. Gingernut

    Gingernut Senior Member

    Joined:
    Sep 18, 2009
    Messages:
    258
    Do you have any drives attached?
     
  15. lalala2

    lalala2 New Around Here

    Joined:
    Jan 6, 2018
    Messages:
    8
    Nope. It looks like there's a memory leak


    Nov 26 12:57:58 kernel: Mem-Info:
    Nov 26 12:57:58 kernel: active_anon:6941 inactive_anon:0 isolated_anon:0
    Nov 26 12:57:58 kernel: active_file:15 inactive_file:17 isolated_file:0
    Nov 26 12:57:58 kernel: unevictable:813 dirty:0 writeback:0 unstable:0
    Nov 26 12:57:58 kernel: slab_reclaimable:438 slab_unreclaimable:74980
    Nov 26 12:57:58 kernel: mapped:93 shmem:0 pagetables:323 bounce:0
    Nov 26 12:57:58 kernel: free:5708 free_pcp:326 free_cma:0
    Nov 26 12:57:58 kernel: DMA free:22936kB min:20480kB low:25600kB high:30720kB active_anon:27764kB inactive_anon:0kB active_file:8kB inactive_file:4kB unevictable:3252kB isolated(anon):0kB isolated(file):0kB present:495616kB managed:440520kB mlocked:0kB dirty:0kB writeback:0kB mapped:220kB shmem:0kB slab_reclaimable:1752kB slab_unreclaimable:299920kB kernel_stack:2144kB pagetables:1292kB unstable:0kB bounce:0kB free_pcp:1304kB local_pcp:732kB free_cma:0kB writeback_tmp:0kB pages_scanned:252 all_unreclai
    Nov 26 12:57:58 kernel: lowmem_reserve[]: 0 0 0
    Nov 26 12:57:58 kernel: DMA: 489*4kB (UEM) 237*8kB (UEM) 230*16kB (UEM) 104*32kB (UEM) 51*64kB (UEM) 5*128kB (EM) 0*256kB 0*512kB 0*1024kB 0*2048kB 2*4096kB (R) = 22956kB
    Nov 26 12:57:58 kernel: 845 total pagecache pages
    Nov 26 12:57:58 kernel: 0 pages in swap cache
    Nov 26 12:57:58 kernel: Swap cache stats: add 0, delete 0, find 0/0
    Nov 26 12:57:58 kernel: Free swap = 0kB
    Nov 26 12:57:58 kernel: Total swap = 0kB
    Nov 26 12:57:58 kernel: 123904 pages RAM
    Nov 26 12:57:58 kernel: 0 pages HighMem/MovableOnly
    Nov 26 12:57:58 kernel: 13774 pages reserved
    Nov 26 12:57:58 kernel: [ pid ] uid tgid total_vm rss nr_ptes nr_pmds swapents oom_score_adj name
    Nov 26 12:57:58 kernel: [ 286] 0 286 4626 22 5 2 0 0 swmdk
    Nov 26 12:57:58 kernel: [ 299] 0 299 392 12 4 2 0 0 wdtctl
    Nov 26 12:57:58 kernel: [ 331] 0 331 428 14 5 2 0 0 hotplug2
    Nov 26 12:57:58 kernel: [ 615] 0 615 2102 81 6 2 0 0 console
    Nov 26 12:57:58 kernel: [ 617] 0 617 769 13 6 2 0 0 sh
    Nov 26 12:57:58 kernel: [ 685] 0 685 768 21 4 2 0 0 syslogd
    Nov 26 12:57:58 kernel: [ 687] 0 687 768 23 5 2 0 0 klogd
    Nov 26 12:57:58 kernel: [ 725] 0 725 2102 93 7 2 0 0 wanduck
    Nov 26 12:57:58 kernel: [ 730] 0 730 2780 73 10 2 0 0 nt_monitor
    Nov 26 12:57:58 kernel: [ 731] 0 731 1290 41 5 2 0 0 protect_srv
    Nov 26 12:57:58 kernel: [ 732] 0 732 2614 84 7 2 0 0 netool
    Nov 26 12:57:58 kernel: [ 742] 0 742 2292 97 8 2 0 0 nt_center
    Nov 26 12:57:58 kernel: [ 748] 0 748 1938 206 8 2 0 0 nt_actMail
    Nov 26 12:57:58 kernel: [ 751] 0 751 581 24 5 2 0 0 dropbear
    Nov 26 12:57:58 kernel: [ 753] 0 753 696 41 5 2 0 0 eapd
    Nov 26 12:57:58 kernel: [ 755] 0 755 846 147 5 2 0 0 nas
    Nov 26 12:57:58 kernel: [ 756] 0 756 2102 81 8 2 0 0 wpsaide
    Nov 26 12:57:58 kernel: [ 757] 0 757 1008 45 6 2 0 0 wlc_nt
    Nov 26 12:57:58 kernel: [ 760] 0 760 728 50 5 2 0 0 bsd
    Nov 26 12:57:58 kernel: [ 766] 0 766 1099 48 5 2 0 0 wlceventd
    Nov 26 12:57:58 kernel: [ 769] 0 769 743 46 5 2 0 0 acsd
    Nov 26 12:57:58 kernel: [ 771] 0 771 687 31 5 2 0 0 dhd_monitor
    Nov 26 12:57:58 kernel: [ 774] 65534 774 588 58 5 2 0 0 dnsmasq
    Nov 26 12:57:58 kernel: [ 781] 0 781 768 27 5 2 0 0 crond
    Nov 26 12:57:58 kernel: [ 794] 0 794 772 56 5 2 0 0 avahi-daemon
    Nov 26 12:57:58 kernel: [ 799] 0 799 685 33 4 2 0 0 infosvr
    Nov 26 12:57:58 kernel: [ 801] 0 801 1086 499 6 2 0 0 sysstate
    Nov 26 12:57:58 kernel: [ 802] 0 802 2159 104 7 2 0 0 watchdog
    Nov 26 12:57:58 kernel: [ 804] 0 804 1033 428 5 2 0 0 rstats
    Nov 26 12:57:58 kernel: [ 830] 0 830 767 47 5 2 0 0 lld2d
    Nov 26 12:57:58 kernel: [ 847] 0 847 1329 200 6 2 0 0 networkmap
    Nov 26 12:57:58 kernel: [ 850] 0 850 1945 88 8 2 0 0 mastiff
    Nov 26 12:57:58 kernel: [ 851] 0 851 2102 81 7 2 0 0 bwdpi_check
    Nov 26 12:57:58 kernel: [ 852] 0 852 2102 86 8 2 0 0 hour_monitor
    Nov 26 12:57:58 kernel: [ 856] 0 856 2874 101 9 2 0 0 roamast
    Nov 26 12:57:58 kernel: [ 869] 0 869 888 49 6 2 0 0 lldpd
    Nov 26 12:57:58 kernel: [ 873] 65534 873 831 38 6 2 0 0 lldpd
    Nov 26 12:57:58 kernel: [ 903] 0 903 2720 123 9 2 0 0 cfg_server
    Nov 26 12:57:58 kernel: [ 1041] 0 1041 2102 88 7 2 0 0 ntp
    Nov 26 12:57:58 kernel: [ 1130] 0 1130 5622 689 16 2 0 0 dcd
    Nov 26 12:57:58 kernel: [ 1144] 0 1144 2343 243 8 2 0 0 wred
    Nov 26 12:57:58 kernel: [ 1192] 0 1192 2102 83 7 2 0 0 bwdpi_wred_aliv
    Nov 26 12:57:58 kernel: [ 2035] 0 2035 479 17 4 2 0 0 mcpd
    Nov 26 12:57:58 kernel: [ 2296] 0 2296 2102 82 7 2 0 0 usbled
    Nov 26 12:57:58 kernel: [ 2297] 0 2297 1875 52 7 2 0 0 u2ec
    Nov 26 12:57:58 kernel: [ 2298] 0 2298 698 29 6 2 0 0 lpd
    Nov 26 12:57:58 kernel: [ 2300] 0 2300 2102 87 7 2 0 0 disk_monitor
    Nov 26 12:57:58 kernel: [ 4377] 0 4377 2027 103 6 2 0 0 httpds
    Nov 26 12:57:58 kernel: [ 4379] 0 4379 3619 1710 11 2 0 0 httpd
    Nov 26 12:57:58 kernel: [ 8445] 0 8445 579 56 5 2 0 0 miniupnpd
    Nov 26 12:57:58 kernel: [31031] 0 31031 427 14 5 2 0 0 tcd
    Nov 26 12:57:58 kernel: [ 886] 0 886 146 1 1 1 0 0 sh
    Nov 26 12:59:26 roamast: eth5: add client [2c:1f:23:27:dd:5c] to monitor list
    Nov 26 13:14:20 roamast: eth6: add client [2c:1f:23:27:dd:5c] to monitor list
    Nov 26 15:29:32 kernel: dcd triggered out of memory codition (oom killer not called): gfp_mask=0x2d2, order=0, oom_score_adj=0
     
  16. Gingernut

    Gingernut Senior Member

    Joined:
    Sep 18, 2009
    Messages:
    258
    At least in my case looks like I had a failing drive attached, NTFS drive removed from router and tested in Windows, was absolutely full of bad sectors.

    Since I've swithced it for a healthy drive I've been stable with an uptime of 12 days so far.