U4 lagging/running slow

[bpratt]

Over the last week I've noticed my U4 appears to be somewhat laggy.

It takes seemingly forever to reboot.
regulary the busy wait 'pointer' is spinning around, when it never used to.

I've had it suddenly reboot by itself, twice today actually... not gui restarts, but right back to the start.

I've just upgraded to 19.3 tonight, but It still seems to be lagging.

[MrQuade]

Long reboot times can be the result of network mount points that point to unavailable locations, like if a NAS has been switched off etc.

Random occurrences of the spinner are often the result of rogue autotimers that are taking too n long to process. This is probably the cause if you notice they pop up every 20 minutes.

This could also be the result of a hard disk fault or connection fault. It's possible the wiz is running out waiting for io.

You can try posting the crash logs of any exist (you should have a log if the crash resulted in a screen full of text).

[bpratt]

no screen of text when it has rebooted itself.

did a HD check, and didn't come up with any issues though.

[MrQuade]

no screen of text when it has rebooted itself.

did a HD check, and didn't come up with any issues though.

If there was no text, and it just spontaneously record, C then this points to a hardware problem, not a firmware issue.

The hard-disk check just does a filesystem check, it doesn't check the hardware necessarily.

You might try checking the /var/log/messages log or dmesg to see if there are any errors reported there. You'll likely need SSH or FTP access for that.

[Grumpy_Geoff]

You might try checking the /var/log/messages log or dmesg to see if there are any errors reported there. You'll likely need SSH or FTP access for that.

Both 'dmesg' and 'messages' files can be viewed from /var/log using File Commander (press TEXT on the file name) or copied to USB (or network share).

[bpratt]

/var/log/messages

May 6 22:04:36 beyonwizu4 user.err kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
May 6 22:04:36 beyonwizu4 user.err kernel: ata1.00: failed command: WRITE DMA EXT
May 6 22:04:36 beyonwizu4 user.err kernel: ata1.00: cmd 35/00:40:d0:0b:0d/00:05:48:00:00/e0 tag 30 dma 688128 out
May 6 22:04:36 beyonwizu4 user.err kernel: res 40/00:00:60:ba:7a/00:02:5a:00:00/e0 Emask 0x4 (timeout)
May 6 22:04:36 beyonwizu4 user.err kernel: ata1.00: status: { DRDY }
May 6 22:04:36 beyonwizu4 user.info kernel: ata1: hard resetting link
May 6 22:04:36 beyonwizu4 user.info kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May 6 22:04:36 beyonwizu4 user.info kernel: ata1.00: configured for UDMA/33
May 6 22:04:36 beyonwizu4 user.info kernel: ata1: EH complete


I'm thinking HD might be on it's way out, as this is the main error, the other log entries are login failure issues.

[prl]

If there are a lot of them, that will affect performance, but occasional ones won't do much as far as performance goes.

[bpratt]

not shedloads of them, but still a number of them.

[peteru]

Check the power and SATA cable connectors first.