Skip to content
View in the app

A better way to browse. Learn more.
Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Unraid Summer Sale in live: 20% off Starter and Unleashed + buy one, get one 50% off

New Motherboard & CPU = Errors

Interstellar
in User Customizations

Featured Replies

Hi Guys, take a look at my syslog and see what you think?

 

Oct 22 22:07:33 Tower kernel: end_request: I/O error, dev sda, sector 3 (Errors)
Oct 22 22:07:33 Tower kernel: Buffer I/O error on device sda1, logical block 1 (Errors)
Oct 22 22:07:33 Tower kernel: lost page write due to I/O error on sda1 (Errors)
Oct 22 22:07:47 Tower kernel: Buffer I/O error on device sda1, logical block 284313 (Errors)
Oct 22 22:07:47 Tower kernel: lost page write due to I/O error on sda1 (Errors)
Oct 22 22:07:47 Tower kernel: Buffer I/O error on device sda1, logical block 284314 (Errors)
Oct 22 22:07:47 Tower kernel: lost page write due to I/O error on sda1 (Errors)
Oct 22 22:07:47 Tower kernel: Buffer I/O error on device sda1, logical block 284315 (Errors)
Oct 22 22:07:47 Tower kernel: lost page write due to I/O error on sda1 (Errors)
Oct 22 22:07:47 Tower kernel: Buffer I/O error on device sda1, logical block 284316 (Errors)
Oct 22 22:07:47 Tower kernel: lost page write due to I/O error on sda1 (Errors)
Oct 22 22:07:47 Tower kernel: Buffer I/O error on device sda1, logical block 284317 (Errors)
Oct 22 22:07:47 Tower kernel: lost page write due to I/O error on sda1 (Errors)
Oct 22 22:07:52 Tower kernel: Buffer I/O error on device sda1, logical block 284122 (Errors)
Oct 22 22:07:52 Tower kernel: lost page write due to I/O error on sda1 (Errors)
Oct 22 22:07:52 Tower kernel: Buffer I/O error on device sda1, logical block 284123 (Errors)
Oct 22 22:07:52 Tower kernel: lost page write due to I/O error on sda1 (Errors)
Oct 22 22:07:52 Tower kernel: Buffer I/O error on device sda1, logical block 284124 (Errors)
Oct 22 22:07:52 Tower kernel: lost page write due to I/O error on sda1 (Errors)
Oct 22 22:07:52 Tower kernel: Buffer I/O error on device sda1, logical block 284125 (Errors)
Oct 22 22:07:52 Tower kernel: lost page write due to I/O error on sda1 (Errors)

syslog-2012-10-22.txt

  • Quote

    looks like /dev/sda has either stopped working, or a power or data connection to it is loose. 

     

    However, since it was just after waking from being put to sleep, it might be your motherboard/disk controller does not wake from a sleep too well.

     

    Since unRAID has never supported "sleep", this should be in the customizations forum.

  • Quote
    • Author

    looks like /dev/sda has either stopped working, or a power or data connection to it is loose. 

     

    However, since it was just after waking from being put to sleep, it might be your motherboard/disk controller does not wake from a sleep too well.

     

    Since unRAID has never supported "sleep", this should be in the customizations forum.

     

     

    Fine, but the errors before that are an UnRAID thing:

     

    Oct 22 22:03:22 Tower kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359)
Oct 22 22:03:22 Tower kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT4._GTF] (Node f304ef48), AE_NOT_FOUND (20120320/psparse-536)
Oct 22 22:03:22 Tower kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Oct 22 22:03:22 Tower kernel: ata7.00: ATA-8: WDC WD20EARS-00MVWB0, 51.0AB51, max UDMA/133
Oct 22 22:03:22 Tower kernel: ata7.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Oct 22 22:03:22 Tower kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359)
Oct 22 22:03:22 Tower kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT5._GTF] (Node f304ef90), AE_NOT_FOUND (20120320/psparse-536)
Oct 22 22:03:22 Tower kernel: ata8.00: ATA-8: WDC WD20EARS-00MVWB0, 51.0AB51, max UDMA/133
Oct 22 22:03:22 Tower kernel: ata8.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Oct 22 22:03:22 Tower kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359)
Oct 22 22:03:22 Tower kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT3._GTF] (Node f304ef00), AE_NOT_FOUND (20120320/psparse-536)
Oct 22 22:03:22 Tower kernel: ata6.00: ATA-7: SAMSUNG HD154UI, 1AG01118, max UDMA7
Oct 22 22:03:22 Tower kernel: ata6.00: 2930277168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Oct 22 22:03:22 Tower kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359)
Oct 22 22:03:22 Tower kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT2._GTF] (Node f304eeb8), AE_NOT_FOUND (20120320/psparse-536)
Oct 22 22:03:22 Tower kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359)
Oct 22 22:03:22 Tower kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT4._GTF] (Node f304ef48), AE_NOT_FOUND (20120320/psparse-536)
Oct 22 22:03:22 Tower kernel: ata5.00: ATA-8: WDC WD20EARS-00MVWB0, 51.0AB51, max UDMA/133
Oct 22 22:03:22 Tower kernel: ata5.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Oct 22 22:03:22 Tower kernel: ata7.00: configured for UDMA/133
Oct 22 22:03:22 Tower kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359)
Oct 22 22:03:22 Tower kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT5._GTF] (Node f304ef90), AE_NOT_FOUND (20120320/psparse-536)
Oct 22 22:03:22 Tower kernel: ata8.00: configured for UDMA/133
Oct 22 22:03:22 Tower kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359)
Oct 22 22:03:22 Tower kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT2._GTF] (Node f304eeb8), AE_NOT_FOUND (20120320/psparse-536)
Oct 22 22:03:22 Tower kernel: ata5.00: configured for UDMA/133
Oct 22 22:03:22 Tower kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359)
Oct 22 22:03:22 Tower kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT3._GTF] (Node f304ef00), AE_NOT_FOUND (20120320/psparse-536)
Oct 22 22:03:22 Tower kernel: ata6.00: configured for UDMA/133
Oct 22 22:03:22 Tower kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Oct 22 22:03:22 Tower kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Oct 22 22:03:22 Tower kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359)
Oct 22 22:03:22 Tower kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node f304ee70), AE_NOT_FOUND (20120320/psparse-536)
Oct 22 22:03:22 Tower kernel: ata4.00: ATA-8: WDC WD2002FAEX-007BA0, 05.01D05, max UDMA/133
Oct 22 22:03:22 Tower kernel: ata4.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Oct 22 22:03:22 Tower kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359)
Oct 22 22:03:22 Tower kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node f304ee28), AE_NOT_FOUND (20120320/psparse-536)
Oct 22 22:03:22 Tower kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359)
Oct 22 22:03:22 Tower kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node f304ee70), AE_NOT_FOUND (20120320/psparse-536)

     

     

    So if you wouldn't mind moving it back :P

  • Quote
    • Author

    I know it isn't a clean install, I ran out of time past night/this morning. I was more hoping for a 'I know what this is, do this and it will fix itself :P'

     

    Ill post a clean one tonight.

     

    Cheers.

  • Quote

    • Archived

    This topic is now archived and is closed to further replies.

    Go to topic listing

    Account

    Navigation

    Search

    Search

    Configure browser push notifications
    Chrome (Android)
    1. Tap the lock icon next to the address bar.
    2. Tap Permissions → Notifications.
    3. Adjust your preference.
    Chrome (Desktop)
    1. Click the padlock icon in the address bar.
    2. Select Site settings.
    3. Find Notifications and adjust your preference.