9 hours ago, Videodr0me said:

Strangely (or not) I was on 6.7.1-RC2 and got no notification of 6.7.2. stable. Only if i manualy change the branch from next to stable unraid displays the update. Is this normal? If its normal, maybe it should be changed so that people on RCs still get info if newer stable versions get released.

Yes, sorry my mistake.  Those on 'next' should now see the update.

3 hours ago, itimpi said:

If your problem is caused by a Marvell based controller there is a solution involving adding extra options to the boot parameters that seems to have worked for most people.    You might want to try it as there is no guarantee that any future UnRaid release will have any other way of handling this,

 

There may be some movement on finding a solution:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832383/comments/16

 

The way bug fixes work in Linux is that they always 'patch' the latest/current development release.  Then if fix is verified to work, the various Linux maintainers back-port the patch to earlier supported kernels.  We'll keep an eye on this.

Just updated main server from 6.7.0. Everything seems to work great. Nothing alarming in logs.

Thanks Limetech and all volunteers for another great update.

Upgraded from 6.7.1 to 6.7.2 with no issues.  Thanks again for supporting your product.

Upgraded from 6.7.0 to 6.7.2 - looks good so far...

Updated from 6.7 to 6.7.2

Now the server isnt booting!

no default or ui configuration directive found

sounds like a broken usb flash drive? 

Upgrade this morning.  No problem so far.  Thank unraid.

6 hours ago, jne1979 said:

Updated from 6.7 to 6.7.2

Now the server isnt booting!

no default or ui configuration directive found

sounds like a broken usb flash drive? 

Make a Backup copy of your Flash Boot drive.  Hopefully, you can make a copy of the config folder.  You might need it if worst comes to worst.  

 

Then run chkdsk on the drive and see what that finds.  If it boots after that, stop and be thankful for your good fortune! 

 

At this juncture, you have three options.  

 

(1)-- try and fix the problem on the flash drive.  

(2)-- format the flash and install the latest software from skratch.  Copy back the config folder from that backup.  See if the system will boot.

(3)-- get new flash drive and install the latest software.  Copy back that config folder. boot system and replace the .key file. 

Updated to 6.7.2 and got the missing drive issue, was running 6.7 before this perfectly fine, tried reverting with nothing. Looking over boot the Adaptec HBA is loading fine during boot sequence but UnRaid is not seeing any drives. Can anyone help?  Checked BIOS, drives are shown.

 

unwejaton-diagnostics-20190701-0459.zip

2 hours ago, kaine1688 said:

Updated to 6.7.2 and got the missing drive issue, was running 6.7 before this perfectly fine, tried reverting with nothing. Looking over boot the Adaptec HBA is loading fine during boot sequence but UnRaid is not seeing any drives. Can anyone help?  Checked BIOS, drives are shown.

 

unwejaton-diagnostics-20190701-0459.zip 82.73 kB · 0 downloads

Kernel oops during device discovery, possibly a kernel issue:

 

Jun 30 23:54:59 unWejaton kernel: sas: phy-14:0 added to port-14:0, phy_mask:0x1 (5003048001dfecff)
Jun 30 23:54:59 unWejaton kernel: sas: DOING DISCOVERY on port 0, pid:2363
Jun 30 23:54:59 unWejaton kernel: BUG: unable to handle kernel paging request at ffff8880ffa7b360
Jun 30 23:54:59 unWejaton kernel: PGD 2401067 P4D 2401067 PUD 0
Jun 30 23:54:59 unWejaton kernel: Oops: 0000 [#1] SMP PTI
Jun 30 23:54:59 unWejaton kernel: CPU: 11 PID: 2363 Comm: kworker/u112:1 Not tainted 4.19.56-Unraid #1
Jun 30 23:54:59 unWejaton kernel: Hardware name: ASUSTeK COMPUTER INC. Z10PE-D16 WS/Z10PE-D16 WS, BIOS 3305 06/22/2016
Jun 30 23:54:59 unWejaton kernel: Workqueue: 0000:82:00.0_disco_q sas_discover_domain [libsas]
Jun 30 23:54:59 unWejaton kernel: RIP: 0010:pm80xx_chip_smp_req+0x22d/0x36c [pm80xx]
Jun 30 23:54:59 unWejaton kernel: Code: c7 c6 10 1e 13 a0 48 c7 c7 8f 5b 13 a0 e8 3f 25 f6 e0 49 8d 44 24 1c 45 31 ff 48 89 44 24 08 41 39 ef 73 87 8b 83 48 44 00 00 <47> 0f b6 44 3d 00 83 e0 08 41 83 ff 0f 77 18 85 c0 47 88 44 3c 0c
Jun 30 23:54:59 unWejaton kernel: RSP: 0018:ffffc9000812bbf8 EFLAGS: 00010093
Jun 30 23:54:59 unWejaton kernel: RAX: 0000000000000001 RBX: ffff88905a6f0000 RCX: 0000000000000080
Jun 30 23:54:59 unWejaton kernel: RDX: 00000000ffa7b360 RSI: 0000000000000001 RDI: ffff88885f027200
Jun 30 23:54:59 unWejaton kernel: RBP: 0000000000000008 R08: 0000000000000040 R09: 0000000000000002
Jun 30 23:54:59 unWejaton kernel: R10: ffff889059bff4e0 R11: ffff88885a4d0e00 R12: ffffc9000812bc0c
Jun 30 23:54:59 unWejaton kernel: R13: ffff8880ffa7b360 R14: ffff889044801080 R15: 0000000000000000
Jun 30 23:54:59 unWejaton kernel: FS:  0000000000000000(0000) GS:ffff88885f6c0000(0000) knlGS:0000000000000000
Jun 30 23:54:59 unWejaton kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jun 30 23:54:59 unWejaton kernel: CR2: ffff8880ffa7b360 CR3: 0000000001e0a001 CR4: 00000000003606e0
Jun 30 23:54:59 unWejaton kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Jun 30 23:54:59 unWejaton kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Jun 30 23:54:59 unWejaton kernel: Call Trace:
Jun 30 23:54:59 unWejaton kernel: pm8001_task_exec.isra.2+0x2ba/0x3c1 [pm80xx]
Jun 30 23:54:59 unWejaton kernel: ? smp_task_timedout+0x44/0x44 [libsas]
Jun 30 23:54:59 unWejaton kernel: smp_execute_task_sg+0xf8/0x224 [libsas]
Jun 30 23:54:59 unWejaton kernel: smp_execute_task+0x52/0x6e [libsas]
Jun 30 23:54:59 unWejaton kernel: sas_discover_expander.part.6+0x7d/0x542 [libsas]
Jun 30 23:54:59 unWejaton kernel: sas_discover_root_expander+0x46/0xd2 [libsas]
Jun 30 23:54:59 unWejaton kernel: sas_discover_domain+0x4a5/0x59b [libsas]
Jun 30 23:54:59 unWejaton kernel: process_one_work+0x16e/0x24f
Jun 30 23:54:59 unWejaton kernel: ? pwq_unbound_release_workfn+0xb7/0xb7
Jun 30 23:54:59 unWejaton kernel: worker_thread+0x1dc/0x2ac
Jun 30 23:54:59 unWejaton kernel: kthread+0x10b/0x113
Jun 30 23:54:59 unWejaton kernel: ? kthread_park+0x71/0x71
Jun 30 23:54:59 unWejaton kernel: ret_from_fork+0x35/0x40
Jun 30 23:54:59 unWejaton kernel: Modules linked in: acpi_cpufreq(-) sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd cryptd glue_helper intel_cstate ipmi_ssif intel_uncore pm80xx(+) mxm_wmi wmi_bmof igb libsas intel_rapl_perf mlx4_core(+) sr_mod ahci i2c_i801 scsi_transport_sas i2c_algo_bit i2c_core libahci cdrom wmi ipmi_si pcc_cpufreq acpi_power_meter acpi_pad button
Jun 30 23:54:59 unWejaton kernel: CR2: ffff8880ffa7b360
Jun 30 23:54:59 unWejaton kernel: ---[ end trace 30c9b447b115a633 ]---

 

I seem to be having out of memory issues that I've never had before. Everything appears to be working ok, first time I had the out of memory error it seemed to kill my VM that I had running.

downloadbox-syslog-20190701-0831.zip

Edited July 1, 20197 yr by allanp81

3 hours ago, johnnie.black said:

Kernel oops during device discovery, possibly a kernel issue:

What does that mean exactly, possible causes?

1 minute ago, kaine1688 said:

What does that mean exactly, possible causes?

You might need to wait for a newer kernel, a board bios and/or HBA firmware upgrades might also help.

7 minutes ago, johnnie.black said:

You might need to wait for a newer kernel, a board bios and/or HBA firmware upgrades might also help.

Anything I can do to get the array up and running? I tried reverting back to 6.7 but the same thing happens. It was running perfectly fine before the update.

16 minutes ago, kaine1688 said:

I tried reverting back to 6.7 but the same thing happens. It was running perfectly fine before the update.

If the same thing happens it wasn't because of the update.

2 minutes ago, johnnie.black said:

If the same thing happens it wasn't because of the update.

Now that I might think about it I might have been on 6.6.6 i think and had a update pending and hit update again to 6.7.2 since the notification was up. Could that have done anything?

Just now, kaine1688 said:

Could that have done anything?

Not done anything, but if it's kernel related going to the previous release you were using will solve the problem.

3 hours ago, allanp81 said:

I seem to be having out of memory issues that I've never had before. Everything appears to be working ok, first time I had the out of memory error it seemed to kill my VM that I had running.

downloadbox-syslog-20190701-0831.zip 50.05 kB · 1 download

 

Post your entire Diagnostics zip file, not just a syslog. Read the FAQs if you're unaware of what Diagnostics is.

3 minutes ago, johnnie.black said:

Not done anything, but if it's kernel related going to the previous release you were using will solve the problem.

The rollback under Update OS only gives me option to 6.7, is there another way to revert back to a previous release?

Just now, kaine1688 said:

is there another way to revert back to a previous release?

Copy all the bz* files from the older release to the flashdrive overwriting the existing ones and reboot.

5 minutes ago, johnnie.black said:

Copy all the bz* files from the older release to the flashdrive overwriting the existing ones and reboot.

I do not want to mess anything up so could you be more specific, there is a folder called previous on the USB but its probably the 6.7 update, is there anywhere else I can get these files? 

Download v6.6.7 and

25 minutes ago, johnnie.black said:

Copy all the bz* files from the older release to the flashdrive overwriting the existing ones and reboot. 

 

1 hour ago, BRiT said:

 

Post your entire Diagnostics zip file, not just a syslog. Read the FAQs if you're unaware of what Diagnostics is.

Thanks, sorry forgot to post the whole thing.

downloadbox-diagnostics-20190701-1246.zip

12 minutes ago, allanp81 said:

Thanks, sorry forgot to post the whole thing.

downloadbox-diagnostics-20190701-1246.zip 176.6 kB · 0 downloads

Your external Buffalo has file system corruption, and you need to Check Disk Filesystem on it (probably need to do it via command line)

Jun 30 03:10:40 downloadbox kernel: XFS (sdc1): Corruption detected! Free inode 0xc36fd4cf not marked free! (mode 0x81ff)

Your cache pool is nearly fully allocated, and you need to fix that up (Probably a FAQ about that one)

    Device size:		 476.97GiB
    Device allocated:		 462.97GiB
    Device unallocated:		  14.00GiB

I would also consider limiting the memory resources of the various docker apps to see if your out of memory situation improves  

Hmm, I wonder if it's related to my cache pool running out of space that I corrected much earlier that day. My cache pool at the moment has well over 100Gb of free space on it. I'll have a look at the external drive, it's probably failing as it was a cheap piece of kit that's not exactly new!

 

Thanks