Ron Posted June 23, 2018 Share Posted June 23, 2018 I awoke today to my subwoofer powering on and realized we had a power outage, and when I got everything up and running again, I found 2 HDDs that are now unmountable' I have attached the diagnostics file. Please let me know what to do next. tower-diagnostics-20180622-1933.zip Quote Link to comment
JorgeB Posted June 23, 2018 Share Posted June 23, 2018 Disks 6 and 7 are not mounting because of an unsupported partition error, it doesn't make sense this being caused by an unclean shutdown, are you sure they were mounting before? 1 Quote Link to comment
Ron Posted June 23, 2018 Author Share Posted June 23, 2018 (edited) Yes, they were being used, and have a lot of my data on them. Should I format them, and hope the parity can rebuild them? Edited June 23, 2018 by Ron Quote Link to comment
JorgeB Posted June 23, 2018 Share Posted June 23, 2018 Don't format, and parity likely can't help with this, post the output of :sfdisk -l /dev/sdbAnd the same for sdc 1 Quote Link to comment
Ron Posted June 23, 2018 Author Share Posted June 23, 2018 Is there a way to do it from the web interface...after the power outage I have lost the video output too on my NAS. Quote Link to comment
JorgeB Posted June 23, 2018 Share Posted June 23, 2018 You can use Putty or the built in terminal. 1 Quote Link to comment
Ron Posted June 23, 2018 Author Share Posted June 23, 2018 (edited) is that under plugins, or are you talking about windows terminal? Edited June 23, 2018 by Ron Quote Link to comment
Ron Posted June 23, 2018 Author Share Posted June 23, 2018 (edited) Ok.. I have putty up, and running with their terminal window. am i typing this correctly sfdisk-l/dev/sdb I am doing this from the root of Unraid root@Tower which is the name of the NAS Edited June 23, 2018 by Ron Quote Link to comment
Ron Posted June 23, 2018 Author Share Posted June 23, 2018 (edited) When i type sfdisk -| /dev/sdb i get the error bash: /dev/sdb: permission denied sfdisk: cannot open -: No such file or directory When I type sfdisk-|/dev/sdb I get the error bash: sfdisk-: command not found bash /dev/sdb: Permission denied Edited June 23, 2018 by Ron Quote Link to comment
JorgeB Posted June 23, 2018 Share Posted June 23, 2018 Command you're running is wrong, use copy/paste Quote Link to comment
Ron Posted June 23, 2018 Author Share Posted June 23, 2018 (edited) got it.. is there a way to copy from the window in Putty? My keyboard does not give a screen print option Edited June 23, 2018 by Ron Quote Link to comment
Ron Posted June 23, 2018 Author Share Posted June 23, 2018 SDC gives me an error Partition 1 does not start on physical sector boundary Quote Link to comment
JorgeB Posted June 23, 2018 Share Posted June 23, 2018 4 minutes ago, Ron said: is there a way to copy from the window in Putty? Putty allows copy/paste 1 Quote Link to comment
JorgeB Posted June 23, 2018 Share Posted June 23, 2018 I'm going to leave now and most likely won't be on the forum until tomorrow, probably someone else can help you before that, but if not I'll pick it up tomorrow morning. 1 Quote Link to comment
Squid Posted June 23, 2018 Share Posted June 23, 2018 11 minutes ago, Ron said: is there a way to copy from the window in Putty? Highlighting (dragging mouse) the text is the "copy" in Putty To paste, simply right click in the window 1 Quote Link to comment
Ron Posted June 23, 2018 Author Share Posted June 23, 2018 login as: root Last login: Sat Jun 23 11:06:54 2018 from 192.168.200.222 Linux 4.14.16-unRAID. root@Tower:~# fdisk -l /dev/sdb Disk /dev/sdb: 5.5 TiB, 6001175126016 bytes, 11721045168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 056432DB-69C0-11E3-88C3-000743150B50 Device Start End Sectors Size Type /dev/sdb1 2048 11721043967 11721041920 5.5T Microsoft basic data root@Tower:~# fdisk -l /dev/sdc Disk /dev/sdc: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0xb4cd68a4 Device Boot Start End Sectors Size Id Type /dev/sdc1 63 976751999 976751937 465.8G 7 HPFS/NTFS/exFAT Partition 1 does not start on physical sector boundary. root@Tower:~# Quote Link to comment
Squid Posted June 23, 2018 Share Posted June 23, 2018 You're going to have to wait til tomorrow for @johnnie.black He is the guru on this type of thing. 1 Quote Link to comment
JorgeB Posted June 23, 2018 Share Posted June 23, 2018 Had time for one more reply, and like I asked before: 10 hours ago, johnnie.black said: are you sure they were mounting before? There's no way those disks were formatted by unRAID before, one still has a Windows GPT partition, and the other has a smaller windows MBR partition, though if they were normally added to the array they would be cleared, and they clearly aren't, unless you did a new config, re-synced parity and never got around to format them. 1 Quote Link to comment
Ron Posted June 23, 2018 Author Share Posted June 23, 2018 (edited) 11 minutes ago, johnnie.black said: Had time for one more reply, and like I asked before: There's no way those disks were formatted by unRAID before, one still has a Windows GPT partition, and the other has a smaller windows MBR partition, though if they were normally added to the array they would be cleared, and they clearly aren't, unless you did a new config, re-synced parity and never got around to format them. I went through he process of adding them as the wiki said. It had them listed as mounted too. What do I do then now? Do I format them? Will I lose all my data, Or does this mean nothing went on them from unraid? Edited June 23, 2018 by Ron Quote Link to comment
pwm Posted June 23, 2018 Share Posted June 23, 2018 44 minutes ago, Ron said: Or does this mean nothing went on them from unraid? Both of the disks have Windows parititions - not unix paritions. /dev/sdb1 2048 11721043967 11721041920 5.5T Microsoft basic data /dev/sdc1 63 976751999 976751937 465.8G 7 HPFS/NTFS/exFAT So if there are contents on them, it's contents that Windows put there. And Windows should then be able to mount and extract the information. Quote Link to comment
Ron Posted June 23, 2018 Author Share Posted June 23, 2018 So since I only use these hdds on Unraid, and am only concerned with unraid...i can format them in Unraid and not lose any data from Unraid correct? Meaning unraid could not have wrote to the hdds, correct? Quote Link to comment
pwm Posted June 23, 2018 Share Posted June 23, 2018 16 minutes ago, Ron said: So since I only use these hdds on Unraid, and am only concerned with unraid...i can format them in Unraid and not lose any data from Unraid correct? Meaning unraid could not have wrote to the hdds, correct? unRAID has most definitely not created the above partitions. And unRAID doesn't support Windows partitions in the array. If you will lose data by formatting them is something you must decide on yourself based on your personal knowledge of their earlier life. If you have possibly mapped them to a Windows VM or something. At least one of the partitions are created by a partitioning software that used the older cylinder/head/sector (CHS) address format instead of the Logical Block Addressing (LBA) . That's why it created the partition with a start address of 63 (it thought it placed the partition on the start of a track). Partition programs new enough to use LBA would have aligned the partition on a n * 4 kB address. Quote Link to comment
SSD Posted June 23, 2018 Share Posted June 23, 2018 @Ron (I had created most of this post before @pwm's post, but have included more detail) ** DO NOT TRY TO DO ANYTHING IN YOUR ARRAY RIGHT NOW. READ THIS POST TO THE VERY BOTTOM AND RESPOND WITH ANY QUESTIONS ** The output from your above the fdisk commands are not as I would expect them to be. For comparison, here is the output I receive for an 8T data disk in my own array. fdisk -l /dev/sdp Disk /dev/sdp: 7.3 TiB, 8001563222016 bytes, 15628053168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 84077B29-0642-46AC-A625-5146AC747B9D Device Start End Sectors Size Type /dev/sdp1 64 15628053134 15628053071 7.3T Linux filesystem When unRAID prepares a disk it will always have a starting sector of 64. Earlier versions of unRAID might have a starting sector of 63 and would still be properly recognized. But this is only for drives 2.2T or smaller. Any disk over that size would have a starting partition of 64 to work as an array disk. Here is an example of an older 2T disk formatted as XFS starting on sector 63. fdisk -l /dev/sdm Disk /dev/sdm: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x9c4adde7 Device Boot Start End Sectors Size Id Type /dev/sdm1 63 3907029167 3907029105 1.8T 83 Linux But if you look at your two outputs ... /dev/sdb1 2048 11721043967 11721041920 5.5T Microsoft basic data /dev/sdc1 63 976751999 976751937 465.8G 7 HPFS/NTFS/exFAT sdb1 is showing a starting sector of 2048. unRAID is not going to recognize that for an array disk. It is not partitioned properly. sdc1 is showing a starting sector of 63 which is possible for an array disk, but only for a disk under 2.2T. This disk is 4T. If you look carefully you'll see the partition size it is showing as 465.8G. UnRAID would always use the full disk size. (If you look at the output from my two disks, you'll see that the disk size and partition size are the same. This looks like a badly partitioned disk for unRAID. The partition types are also showing Microsoft basic data and HPFS/NTFS/exFAT. If you look at my disks it is showing Linux. This is another sign that the disks are badly partitioned / formatted for unRAID. Here is an excerpt from your syslog indicating that unRAID cannot make sense of these two disks, showing unsupported partition layout. Jun 22 19:31:53 Tower emhttpd: shcmd (67): mount -t reiserfs -o remount,user_xattr,acl,noatime,nodiratime /dev/md5 /mnt/disk5 Jun 22 19:31:53 Tower emhttpd: reiserfs: resizing /mnt/disk5 Jun 22 19:31:54 Tower emhttpd: shcmd (68): mkdir -p /mnt/disk6 Jun 22 19:31:54 Tower emhttpd: /mnt/disk6 mount error: Unsupported partition layout Jun 22 19:31:54 Tower emhttpd: shcmd (69): umount /mnt/disk6 Jun 22 19:31:54 Tower root: umount: /mnt/disk6: not mounted. Jun 22 19:31:54 Tower emhttpd: shcmd (69): exit status: 32 Jun 22 19:31:54 Tower emhttpd: shcmd (70): rmdir /mnt/disk6 Jun 22 19:31:54 Tower emhttpd: shcmd (71): mkdir -p /mnt/disk7 Jun 22 19:31:54 Tower emhttpd: /mnt/disk7 mount error: Unsupported partition layout Jun 22 19:31:54 Tower emhttpd: shcmd (72): umount /mnt/disk7 Jun 22 19:31:54 Tower root: umount: /mnt/disk7: not mounted. Jun 22 19:31:54 Tower emhttpd: shcmd (72): exit status: 32 Jun 22 19:31:54 Tower emhttpd: shcmd (73): rmdir /mnt/disk7 I can't speak to what happened. Looks like the disks were never part of your array. But if they were, and you had data on them, appears the partition table was corrupted. This is not a typical thing to have happen randomly - normally implies that the user did something to alter the partition table through a partitioning tool, or by booting in a non-Linux OS and performing partitioning. Suggest waiting for @johnnie.black to give his suggestion, but if this was a corruption that occurred outside of normal array I/O, then the parities (looks like you have dual parity) could simulate those two disks if you do things exactly correctly. And that simulation might be intact while the physical disks are corrupted. To confirm you could backup your config folder on your flash disk (do on Windows machine while server is powered down), disconnect (or just unassign disk6 and disk7), and start the array. Those disks would then be simulated and you could look to see if your data is showing accurately. DO NOT DO ANY WRITES TO THE ARRAY. In fact you might want to do this in safe mode to prevent docker/plugin/VMs to do writes to your array. It will also prevent the array from autostarting (but missing disks will also stop the autostart which is a good reason to physically disconnect them prior to booting). But looks like array has already started. In fact a parity check may have kicked off (although I see no sign of that in the syslog, but do see Plex started meaning the array started). Depending on the unRAID version, the parity check, if it kicked off, would have been in correcting mode or non-correction mode. You can't to back, and best you could do is try removing those 2 disks and see what you get. But I suggest waiting for johnnie and others who may have other ideas to pick the one you want to do first. My approach (if you can stop writes to the array) is reversible with the backup of the config folder I suggested. You'd just have to rename the config folder to "config.bad" or something, and rename your config folder backup to "config" (do this in Windows workstation while server is powered down). I don't think I have to say this - but your array is in a very sensitive state. Your ability to recover may be impacted by doing the wrong thing. Even a very small mistake may make recovery impossible. Therefore, I urge you not to rush into any action without posting EXACTLY what you plan to do in as much detail as possible, and getting some before doing it! Some things are "destructive", and once you do it you can't undo it. But a simple change can make them "non-destructive", enabling to to undo the changes and get things back into the original state to try something else if the action doesn't work. (For example, my step to backup the config folder before removing disk6/disk7 is what makes my suggestion non-destructive. Otherwise getting back to the starting state would be much more difficult or potentially impossible without it.) A little knowledge can be a dangerous thing, so you really want others looking over your shoulder before each action is attempted. 1 Quote Link to comment
Ron Posted June 23, 2018 Author Share Posted June 23, 2018 1 hour ago, SSD said: @Ron (I had created most of this post before @pwm's post, but have included more detail) ** DO NOT TRY TO DO ANYTHING IN YOUR ARRAY RIGHT NOW. READ THIS POST TO THE VERY BOTTOM AND RESPOND WITH ANY QUESTIONS ** The output from your above the fdisk commands are not as I would expect them to be. For comparison, here is the output I receive for an 8T data disk in my own array. fdisk -l /dev/sdp Disk /dev/sdp: 7.3 TiB, 8001563222016 bytes, 15628053168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 84077B29-0642-46AC-A625-5146AC747B9D Device Start End Sectors Size Type /dev/sdp1 64 15628053134 15628053071 7.3T Linux filesystem When unRAID prepares a disk it will always have a starting sector of 64. Earlier versions of unRAID might have a starting sector of 63 and would still be properly recognized. But this is only for drives 2.2T or smaller. Any disk over that size would have a starting partition of 64 to work as an array disk. Here is an example of an older 2T disk formatted as XFS starting on sector 63. fdisk -l /dev/sdm Disk /dev/sdm: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x9c4adde7 Device Boot Start End Sectors Size Id Type /dev/sdm1 63 3907029167 3907029105 1.8T 83 Linux But if you look at your two outputs ... /dev/sdb1 2048 11721043967 11721041920 5.5T Microsoft basic data /dev/sdc1 63 976751999 976751937 465.8G 7 HPFS/NTFS/exFAT sdb1 is showing a starting sector of 2048. unRAID is not going to recognize that for an array disk. It is not partitioned properly. sdc1 is showing a starting sector of 63 which is possible for an array disk, but only for a disk under 2.2T. This disk is 4T. If you look carefully you'll see the partition size it is showing as 465.8G. UnRAID would always use the full disk size. (If you look at the output from my two disks, you'll see that the disk size and partition size are the same. This looks like a badly partitioned disk for unRAID. The partition types are also showing Microsoft basic data and HPFS/NTFS/exFAT. If you look at my disks it is showing Linux. This is another sign that the disks are badly partitioned / formatted for unRAID. Here is an excerpt from your syslog indicating that unRAID cannot make sense of these two disks, showing unsupported partition layout. Jun 22 19:31:53 Tower emhttpd: shcmd (67): mount -t reiserfs -o remount,user_xattr,acl,noatime,nodiratime /dev/md5 /mnt/disk5 Jun 22 19:31:53 Tower emhttpd: reiserfs: resizing /mnt/disk5 Jun 22 19:31:54 Tower emhttpd: shcmd (68): mkdir -p /mnt/disk6 Jun 22 19:31:54 Tower emhttpd: /mnt/disk6 mount error: Unsupported partition layout Jun 22 19:31:54 Tower emhttpd: shcmd (69): umount /mnt/disk6 Jun 22 19:31:54 Tower root: umount: /mnt/disk6: not mounted. Jun 22 19:31:54 Tower emhttpd: shcmd (69): exit status: 32 Jun 22 19:31:54 Tower emhttpd: shcmd (70): rmdir /mnt/disk6 Jun 22 19:31:54 Tower emhttpd: shcmd (71): mkdir -p /mnt/disk7 Jun 22 19:31:54 Tower emhttpd: /mnt/disk7 mount error: Unsupported partition layout Jun 22 19:31:54 Tower emhttpd: shcmd (72): umount /mnt/disk7 Jun 22 19:31:54 Tower root: umount: /mnt/disk7: not mounted. Jun 22 19:31:54 Tower emhttpd: shcmd (72): exit status: 32 Jun 22 19:31:54 Tower emhttpd: shcmd (73): rmdir /mnt/disk7 I can't speak to what happened. Looks like the disks were never part of your array. But if they were, and you had data on them, appears the partition table was corrupted. This is not a typical thing to have happen randomly - normally implies that the user did something to alter the partition table through a partitioning tool, or by booting in a non-Linux OS and performing partitioning. Suggest waiting for @johnnie.black to give his suggestion, but if this was a corruption that occurred outside of normal array I/O, then the parities (looks like you have dual parity) could simulate those two disks if you do things exactly correctly. And that simulation might be intact while the physical disks are corrupted. To confirm you could backup your config folder on your flash disk (do on Windows machine while server is powered down), disconnect (or just unassign disk6 and disk7), and start the array. Those disks would then be simulated and you could look to see if your data is showing accurately. DO NOT DO ANY WRITES TO THE ARRAY. In fact you might want to do this in safe mode to prevent docker/plugin/VMs to do writes to your array. It will also prevent the array from autostarting (but missing disks will also stop the autostart which is a good reason to physically disconnect them prior to booting). But looks like array has already started. In fact a parity check may have kicked off (although I see no sign of that in the syslog, but do see Plex started meaning the array started). Depending on the unRAID version, the parity check, if it kicked off, would have been in correcting mode or non-correction mode. You can't to back, and best you could do is try removing those 2 disks and see what you get. But I suggest waiting for johnnie and others who may have other ideas to pick the one you want to do first. My approach (if you can stop writes to the array) is reversible with the backup of the config folder I suggested. You'd just have to rename the config folder to "config.bad" or something, and rename your config folder backup to "config" (do this in Windows workstation while server is powered down). I don't think I have to say this - but your array is in a very sensitive state. Your ability to recover may be impacted by doing the wrong thing. Even a very small mistake may make recovery impossible. Therefore, I urge you not to rush into any action without posting EXACTLY what you plan to do in as much detail as possible, and getting some before doing it! Some things are "destructive", and once you do it you can't undo it. But a simple change can make them "non-destructive", enabling to to undo the changes and get things back into the original state to try something else if the action doesn't work. (For example, my step to backup the config folder before removing disk6/disk7 is what makes my suggestion non-destructive. Otherwise getting back to the starting state would be much more difficult or potentially impossible without it.) A little knowledge can be a dangerous thing, so you really want others looking over your shoulder before each action is attempted. Is it even safe to use Unraid now? I am on 6.41. The parity check showed 9 errors. Jun 22 19:31:32 Tower kernel: microcode: microcode updated early to revision 0x22, date = 2017-01-27 Jun 22 19:31:32 Tower kernel: Linux version 4.14.16-unRAID (root@develop64) (gcc version 7.3.0 (GCC)) #1 SMP PREEMPT Wed Jan 31 08:51:39 PST 2018 Jun 22 19:31:32 Tower kernel: Command line: BOOT_IMAGE=/bzimage initrd=/bzroot Jun 22 19:31:32 Tower kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' Jun 22 19:31:32 Tower kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' Jun 22 19:31:32 Tower kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' Jun 22 19:31:32 Tower kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 Jun 22 19:31:32 Tower kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format. Jun 22 19:31:32 Tower kernel: e820: BIOS-provided physical RAM map: Jun 22 19:31:32 Tower kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009c3ff] usable Jun 22 19:31:32 Tower kernel: BIOS-e820: [mem 0x000000000009c400-0x000000000009ffff] reserved Jun 22 19:31:32 Tower kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved Jun 22 19:31:32 Tower kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000b3ad3fff] usable Jun 22 19:31:32 Tower kernel: BIOS-e820: [mem 0x00000000b3ad4000-0x00000000b3adafff] ACPI NVS Jun 22 19:31:32 Tower kernel: BIOS-e820: [mem 0x00000000b3adb000-0x00000000b3f34fff] usable Jun 22 19:31:32 Tower kernel: BIOS-e820: [mem 0x00000000b3f35000-0x00000000b439ffff] reserved Jun 22 19:31:32 Tower kernel: BIOS-e820: [mem 0x00000000b43a0000-0x00000000c870ffff] usable Jun 22 19:31:32 Tower kernel: BIOS-e820: [mem 0x00000000c8710000-0x00000000c8918fff] reserved Jun 22 19:31:32 Tower kernel: BIOS-e820: [mem 0x00000000c8919000-0x00000000c8931fff] ACPI data Jun 22 19:31:32 Tower kernel: BIOS-e820: [mem 0x00000000c8932000-0x00000000c8e72fff] ACPI NVS Jun 22 19:31:32 Tower kernel: BIOS-e820: [mem 0x00000000c8e73000-0x00000000c9ffefff] reserved Jun 22 19:31:32 Tower kernel: BIOS-e820: [mem 0x00000000c9fff000-0x00000000c9ffffff] usable Jun 22 19:31:32 Tower kernel: BIOS-e820: [mem 0x00000000cb000000-0x00000000cf1fffff] reserved Jun 22 19:31:32 Tower kernel: BIOS-e820: [mem 0x00000000f0000000-0x00000000f7ffffff] reserved Jun 22 19:31:32 Tower kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved Jun 22 19:31:32 Tower kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved Jun 22 19:31:32 Tower kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved Jun 22 19:31:32 Tower kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved Jun 22 19:31:32 Tower kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved Jun 22 19:31:32 Tower kernel: BIOS-e820: [mem 0x0000000100000000-0x000000042fdfffff] usable Jun 22 19:31:32 Tower kernel: NX (Execute Disable) protection: active Jun 22 19:31:32 Tower kernel: random: fast init done Jun 22 19:31:32 Tower kernel: SMBIOS 2.7 present. Jun 22 19:31:32 Tower kernel: DMI: ASUS All Series/Z87-PRO, BIOS 2103 08/18/2014 Jun 22 19:31:32 Tower kernel: tsc: Fast TSC calibration using PIT Jun 22 19:31:32 Tower kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved Jun 22 19:31:32 Tower kernel: e820: remove [mem 0x000a0000-0x000fffff] usable Jun 22 19:31:32 Tower kernel: e820: last_pfn = 0x42fe00 max_arch_pfn = 0x400000000 Jun 22 19:31:32 Tower kernel: MTRR default type: uncachable Jun 22 19:31:32 Tower kernel: MTRR fixed ranges enabled: Jun 22 19:31:32 Tower kernel: 00000-9FFFF write-back Jun 22 19:31:32 Tower kernel: A0000-BFFFF uncachable Jun 22 19:31:32 Tower kernel: C0000-D7FFF write-protect Jun 22 19:31:32 Tower kernel: D8000-E7FFF uncachable Jun 22 19:31:32 Tower kernel: E8000-FFFFF write-protect Jun 22 19:31:32 Tower kernel: MTRR variable ranges enabled: Jun 22 19:31:32 Tower kernel: 0 base 0000000000 mask 7C00000000 write-back Jun 22 19:31:32 Tower kernel: 1 base 0400000000 mask 7FE0000000 write-back Jun 22 19:31:32 Tower kernel: 2 base 0420000000 mask 7FF0000000 write-back Jun 22 19:31:32 Tower kernel: 3 base 00E0000000 mask 7FE0000000 uncachable Jun 22 19:31:32 Tower kernel: 4 base 00D0000000 mask 7FF0000000 uncachable Jun 22 19:31:32 Tower kernel: 5 base 00CC000000 mask 7FFC000000 uncachable Jun 22 19:31:32 Tower kernel: 6 base 00CB000000 mask 7FFF000000 uncachable Jun 22 19:31:32 Tower kernel: 7 base 042FE00000 mask 7FFFE00000 uncachable Jun 22 19:31:32 Tower kernel: 8 disabled Jun 22 19:31:32 Tower kernel: 9 disabled Jun 22 19:31:32 Tower kernel: x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT Jun 22 19:31:32 Tower kernel: e820: update [mem 0xcb000000-0xffffffff] usable ==> reserved Jun 22 19:31:32 Tower kernel: e820: last_pfn = 0xca000 max_arch_pfn = 0x400000000 Jun 22 19:31:32 Tower kernel: found SMP MP-table at [mem 0x000fd770-0x000fd77f] mapped at [ffffffffff200770] Jun 22 19:31:32 Tower kernel: Base memory trampoline at [ffff880000096000] 96000 size 24576 Jun 22 19:31:32 Tower kernel: Using GB pages for direct mapping Jun 22 19:31:32 Tower kernel: BRK [0x0202e000, 0x0202efff] PGTABLE Jun 22 19:31:32 Tower kernel: BRK [0x0202f000, 0x0202ffff] PGTABLE Jun 22 19:31:32 Tower kernel: BRK [0x02030000, 0x02030fff] PGTABLE Jun 22 19:31:32 Tower kernel: BRK [0x02031000, 0x02031fff] PGTABLE Jun 22 19:31:32 Tower kernel: BRK [0x02032000, 0x02032fff] PGTABLE Jun 22 19:31:32 Tower kernel: BRK [0x02033000, 0x02033fff] PGTABLE Jun 22 19:31:32 Tower kernel: RAMDISK: [mem 0x7b170000-0x7fffffff] Jun 22 19:31:32 Tower kernel: ACPI: Early table checksum verification disabled Jun 22 19:31:32 Tower kernel: ACPI: RSDP 0x00000000000F0490 000024 (v02 ALASKA) Jun 22 19:31:32 Tower kernel: ACPI: XSDT 0x00000000C891E080 00007C (v01 ALASKA A M I 01072009 AMI 00010013) Jun 22 19:31:32 Tower kernel: ACPI: FACP 0x00000000C892CA78 00010C (v05 ALASKA A M I 01072009 AMI 00010013) Jun 22 19:31:32 Tower kernel: ACPI: DSDT 0x00000000C891E198 00E8DB (v02 ALASKA A M I 00000031 INTL 20091112) Jun 22 19:31:32 Tower kernel: ACPI: FACS 0x00000000C8E71080 000040 Jun 22 19:31:32 Tower kernel: ACPI: APIC 0x00000000C892CB88 000092 (v03 ALASKA A M I 01072009 AMI 00010013) Jun 22 19:31:32 Tower kernel: ACPI: FPDT 0x00000000C892CC20 000044 (v01 ALASKA A M I 01072009 AMI 00010013) Jun 22 19:31:32 Tower kernel: ACPI: LPIT 0x00000000C892CC68 00005C (v01 ALASKA A M I 00000000 AMI. 00000005) Jun 22 19:31:32 Tower kernel: ACPI: SSDT 0x00000000C892CCC8 000539 (v01 PmRef Cpu0Ist 00003000 INTL 20091112) Jun 22 19:31:32 Tower kernel: ACPI: SSDT 0x00000000C892D208 000AD8 (v01 PmRef CpuPm 00003000 INTL 20091112) Jun 22 19:31:32 Tower kernel: ACPI: MCFG 0x00000000C892DCE0 00003C (v01 ALASKA A M I 01072009 MSFT 00000097) Jun 22 19:31:32 Tower kernel: ACPI: HPET 0x00000000C892DD20 000038 (v01 ALASKA A M I 01072009 AMI. 00000005) Jun 22 19:31:32 Tower kernel: ACPI: SSDT 0x00000000C892DD58 00036D (v01 SataRe SataTabl 00001000 INTL 20091112) Jun 22 19:31:32 Tower kernel: ACPI: SSDT 0x00000000C892E0C8 0034E1 (v01 SaSsdt SaSsdt 00003000 INTL 20091112) Jun 22 19:31:32 Tower kernel: ACPI: BGRT 0x00000000C8931608 000038 (v00 ALASKA A M I 01072009 AMI 00010013) Jun 22 19:31:32 Tower kernel: ACPI: Local APIC address 0xfee00000 Jun 22 19:31:32 Tower kernel: No NUMA configuration found Jun 22 19:31:32 Tower kernel: Faking a node at [mem 0x0000000000000000-0x000000042fdfffff] Jun 22 19:31:32 Tower kernel: NODE_DATA(0) allocated [mem 0x42fdf7000-0x42fdfafff] Jun 22 19:31:32 Tower kernel: Zone ranges: Jun 22 19:31:32 Tower kernel: DMA [mem 0x0000000000001000-0x0000000000ffffff] Jun 22 19:31:32 Tower kernel: DMA32 [mem 0x0000000001000000-0x00000000ffffffff] Jun 22 19:31:32 Tower kernel: Normal [mem 0x0000000100000000-0x000000042fdfffff] Jun 22 19:31:32 Tower kernel: Movable zone start for each node Jun 22 19:31:32 Tower kernel: Early memory node ranges Jun 22 19:31:32 Tower kernel: node 0: [mem 0x0000000000001000-0x000000000009bfff] Jun 22 19:31:32 Tower kernel: node 0: [mem 0x0000000000100000-0x00000000b3ad3fff] Jun 22 19:31:32 Tower kernel: node 0: [mem 0x00000000b3adb000-0x00000000b3f34fff] Jun 22 19:31:32 Tower kernel: node 0: [mem 0x00000000b43a0000-0x00000000c870ffff] Jun 22 19:31:32 Tower kernel: node 0: [mem 0x00000000c9fff000-0x00000000c9ffffff] Jun 22 19:31:32 Tower kernel: node 0: [mem 0x0000000100000000-0x000000042fdfffff] Jun 22 19:31:32 Tower kernel: Initmem setup node 0 [mem 0x0000000000001000-0x000000042fdfffff] Jun 22 19:31:32 Tower kernel: On node 0 totalpages: 4161594 Jun 22 19:31:32 Tower kernel: DMA zone: 64 pages used for memmap Jun 22 19:31:32 Tower kernel: DMA zone: 21 pages reserved Jun 22 19:31:32 Tower kernel: DMA zone: 3995 pages, LIFO batch:0 Jun 22 19:31:32 Tower kernel: DMA32 zone: 12747 pages used for memmap Jun 22 19:31:32 Tower kernel: DMA32 zone: 815775 pages, LIFO batch:31 Jun 22 19:31:32 Tower kernel: Normal zone: 52216 pages used for memmap Jun 22 19:31:32 Tower kernel: Normal zone: 3341824 pages, LIFO batch:31 Jun 22 19:31:32 Tower kernel: Reserving Intel graphics memory at 0x00000000cb200000-0x00000000cf1fffff Jun 22 19:31:32 Tower kernel: ACPI: PM-Timer IO Port: 0x1808 Jun 22 19:31:32 Tower kernel: ACPI: Local APIC address 0xfee00000 Jun 22 19:31:32 Tower kernel: ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1]) Jun 22 19:31:32 Tower kernel: IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 Jun 22 19:31:32 Tower kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) Jun 22 19:31:32 Tower kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) Jun 22 19:31:32 Tower kernel: ACPI: IRQ0 used by override. Jun 22 19:31:32 Tower kernel: ACPI: IRQ9 used by override. Jun 22 19:31:32 Tower kernel: Using ACPI (MADT) for SMP configuration information Jun 22 19:31:32 Tower kernel: ACPI: HPET id: 0x8086a701 base: 0xfed00000 Jun 22 19:31:32 Tower kernel: smpboot: Allowing 8 CPUs, 0 hotplug CPUs Jun 22 19:31:32 Tower kernel: e820: [mem 0xcf200000-0xefffffff] available for PCI devices Jun 22 19:31:32 Tower kernel: Booting paravirtualized kernel on bare hardware Jun 22 19:31:32 Tower kernel: clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1910969940391419 ns Jun 22 19:31:32 Tower kernel: setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:8 nr_node_ids:1 Jun 22 19:31:32 Tower kernel: percpu: Embedded 43 pages/cpu @ffff88042fa00000 s139032 r8192 d28904 u262144 Jun 22 19:31:32 Tower kernel: pcpu-alloc: s139032 r8192 d28904 u262144 alloc=1*2097152 Jun 22 19:31:32 Tower kernel: pcpu-alloc: [0] 0 1 2 3 4 5 6 7 Jun 22 19:31:32 Tower kernel: Built 1 zonelists, mobility grouping on. Total pages: 4096546 Jun 22 19:31:32 Tower kernel: Policy zone: Normal Jun 22 19:31:32 Tower kernel: Kernel command line: BOOT_IMAGE=/bzimage initrd=/bzroot Jun 22 19:31:32 Tower kernel: PID hash table entries: 4096 (order: 3, 32768 bytes) Jun 22 19:31:32 Tower kernel: Memory: 16219648K/16646376K available (8204K kernel code, 702K rwdata, 1952K rodata, 1080K init, 508K bss, 426728K reserved, 0K cma-reserved) Jun 22 19:31:32 Tower kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1 Jun 22 19:31:32 Tower kernel: Kernel/User page tables isolation: enabled Jun 22 19:31:32 Tower kernel: Preemptible hierarchical RCU implementation. Jun 22 19:31:32 Tower kernel: RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=8. Jun 22 19:31:32 Tower kernel: Tasks RCU enabled. Jun 22 19:31:32 Tower kernel: RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8 Jun 22 19:31:32 Tower kernel: NR_IRQS: 16640, nr_irqs: 488, preallocated irqs: 16 Jun 22 19:31:32 Tower kernel: Offload RCU callbacks from CPUs: . Jun 22 19:31:32 Tower kernel: Console: colour VGA+ 80x25 Jun 22 19:31:32 Tower kernel: console [tty0] enabled Jun 22 19:31:32 Tower kernel: clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 133484882848 ns Jun 22 19:31:32 Tower kernel: hpet clockevent registered Jun 22 19:31:32 Tower kernel: tsc: Fast TSC calibration using PIT Jun 22 19:31:32 Tower kernel: tsc: Detected 3606.573 MHz processor Jun 22 19:31:32 Tower kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 7213.14 BogoMIPS (lpj=3606573) Jun 22 19:31:32 Tower kernel: pid_max: default: 32768 minimum: 301 Jun 22 19:31:32 Tower kernel: ACPI: Core revision 20170728 Jun 22 19:31:32 Tower kernel: ACPI: 5 ACPI AML tables successfully acquired and loaded Jun 22 19:31:32 Tower kernel: Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes) Jun 22 19:31:32 Tower kernel: Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes) Jun 22 19:31:32 Tower kernel: Mount-cache hash table entries: 32768 (order: 6, 262144 bytes) Jun 22 19:31:32 Tower kernel: Mountpoint-cache hash table entries: 32768 (order: 6, 262144 bytes) Jun 22 19:31:32 Tower kernel: CPU: Physical Processor ID: 0 Jun 22 19:31:32 Tower kernel: CPU: Processor Core ID: 0 Jun 22 19:31:32 Tower kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance' Jun 22 19:31:32 Tower kernel: ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8) Jun 22 19:31:32 Tower kernel: mce: CPU supports 9 MCE banks Jun 22 19:31:32 Tower kernel: CPU0: Thermal monitoring enabled (TM1) Jun 22 19:31:32 Tower kernel: process: using mwait in idle threads Jun 22 19:31:32 Tower kernel: Last level iTLB entries: 4KB 1024, 2MB 1024, 4MB 1024 Jun 22 19:31:32 Tower kernel: Last level dTLB entries: 4KB 1024, 2MB 1024, 4MB 1024, 1GB 4 Jun 22 19:31:32 Tower kernel: Spectre V2 mitigation: Mitigation: Full generic retpoline Jun 22 19:31:32 Tower kernel: Freeing SMP alternatives memory: 28K Jun 22 19:31:32 Tower kernel: smpboot: Max logical packages: 2 Jun 22 19:31:32 Tower kernel: x2apic: IRQ remapping doesn't support X2APIC mode Jun 22 19:31:32 Tower kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 Jun 22 19:31:32 Tower kernel: TSC deadline timer enabled Jun 22 19:31:32 Tower kernel: smpboot: CPU0: Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz (family: 0x6, model: 0x3c, stepping: 0x3) Jun 22 19:31:32 Tower kernel: Performance Events: PEBS fmt2+, Haswell events, 16-deep LBR, full-width counters, Intel PMU driver. Jun 22 19:31:32 Tower kernel: ... version: 3 Jun 22 19:31:32 Tower kernel: ... bit width: 48 Jun 22 19:31:32 Tower kernel: ... generic registers: 4 Jun 22 19:31:32 Tower kernel: ... value mask: 0000ffffffffffff Jun 22 19:31:32 Tower kernel: ... max period: 00007fffffffffff Jun 22 19:31:32 Tower kernel: ... fixed-purpose events: 3 Jun 22 19:31:32 Tower kernel: ... event mask: 000000070000000f Jun 22 19:31:32 Tower kernel: Hierarchical SRCU implementation. Jun 22 19:31:32 Tower kernel: smp: Bringing up secondary CPUs ... Jun 22 19:31:32 Tower kernel: x86: Booting SMP configuration: Jun 22 19:31:32 Tower kernel: .... node #0, CPUs: #1 #2 #3 #4 #5 #6 #7 Jun 22 19:31:32 Tower kernel: smp: Brought up 1 node, 8 CPUs Jun 22 19:31:32 Tower kernel: smpboot: Total of 8 processors activated (57705.16 BogoMIPS) Jun 22 19:31:32 Tower kernel: devtmpfs: initialized Jun 22 19:31:32 Tower kernel: x86/mm: Memory block size: 128MB Jun 22 19:31:32 Tower kernel: PM: Registering ACPI NVS region [mem 0xb3ad4000-0xb3adafff] (28672 bytes) Jun 22 19:31:32 Tower kernel: PM: Registering ACPI NVS region [mem 0xc8932000-0xc8e72fff] (5509120 bytes) Jun 22 19:31:32 Tower kernel: clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275000 ns Jun 22 19:31:32 Tower kernel: futex hash table entries: 2048 (order: 5, 131072 bytes) Jun 22 19:31:32 Tower kernel: xor: automatically using best checksumming function avx Jun 22 19:31:32 Tower kernel: pinctrl core: initialized pinctrl subsystem Jun 22 19:31:32 Tower kernel: NET: Registered protocol family 16 Jun 22 19:31:32 Tower kernel: cpuidle: using governor ladder Jun 22 19:31:32 Tower kernel: cpuidle: using governor menu Jun 22 19:31:32 Tower kernel: ACPI FADT declares the system doesn't support PCIe ASPM, so disable it Jun 22 19:31:32 Tower kernel: ACPI: bus type PCI registered Jun 22 19:31:32 Tower kernel: PCI: MMCONFIG for domain 0000 [bus 00-7f] at [mem 0xf0000000-0xf7ffffff] (base 0xf0000000) Jun 22 19:31:32 Tower kernel: PCI: MMCONFIG at [mem 0xf0000000-0xf7ffffff] reserved in E820 Jun 22 19:31:32 Tower kernel: pmd_set_huge: Cannot satisfy [mem 0xf0000000-0xf0200000] with a huge-page mapping due to MTRR override. Jun 22 19:31:32 Tower kernel: PCI: Using configuration type 1 for base access Jun 22 19:31:32 Tower kernel: core: PMU erratum BJ122, BV98, HSD29 worked around, HT is on Jun 22 19:31:32 Tower kernel: raid6: sse2x1 gen() 12421 MB/s Jun 22 19:31:32 Tower kernel: raid6: sse2x1 xor() 8396 MB/s Jun 22 19:31:32 Tower kernel: raid6: sse2x2 gen() 14757 MB/s Jun 22 19:31:32 Tower kernel: raid6: sse2x2 xor() 9716 MB/s Jun 22 19:31:32 Tower kernel: raid6: sse2x4 gen() 18000 MB/s Jun 22 19:31:32 Tower kernel: raid6: sse2x4 xor() 11771 MB/s Jun 22 19:31:32 Tower kernel: raid6: avx2x1 gen() 24351 MB/s Jun 22 19:31:32 Tower kernel: raid6: avx2x1 xor() 16111 MB/s Jun 22 19:31:32 Tower kernel: raid6: avx2x2 gen() 28359 MB/s Jun 22 19:31:32 Tower kernel: raid6: avx2x2 xor() 18359 MB/s Jun 22 19:31:32 Tower kernel: raid6: avx2x4 gen() 33386 MB/s Jun 22 19:31:32 Tower kernel: raid6: avx2x4 xor() 21619 MB/s Jun 22 19:31:32 Tower kernel: raid6: using algorithm avx2x4 gen() 33386 MB/s Jun 22 19:31:32 Tower kernel: raid6: .... xor() 21619 MB/s, rmw enabled Jun 22 19:31:32 Tower kernel: raid6: using avx2x2 recovery algorithm Jun 22 19:31:32 Tower kernel: ACPI: Added _OSI(Module Device) Jun 22 19:31:32 Tower kernel: ACPI: Added _OSI(Processor Device) Jun 22 19:31:32 Tower kernel: ACPI: Added _OSI(3.0 _SCP Extensions) Jun 22 19:31:32 Tower kernel: ACPI: Added _OSI(Processor Aggregator Device) Jun 22 19:31:32 Tower kernel: ACPI: Executed 1 blocks of module-level executable AML code Jun 22 19:31:32 Tower kernel: ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored Jun 22 19:31:32 Tower kernel: ACPI: Dynamic OEM Table Load: Jun 22 19:31:32 Tower kernel: ACPI: SSDT 0xFFFF88041D0AE000 0003D3 (v01 PmRef Cpu0Cst 00003001 INTL 20091112) Jun 22 19:31:32 Tower kernel: ACPI: Dynamic OEM Table Load: Jun 22 19:31:32 Tower kernel: ACPI: SSDT 0xFFFF88041D5A7000 0005AA (v01 PmRef ApIst 00003000 INTL 20091112) Jun 22 19:31:32 Tower kernel: ACPI: Dynamic OEM Table Load: Jun 22 19:31:32 Tower kernel: ACPI: SSDT 0xFFFF88041D7E6C00 000119 (v01 PmRef ApCst 00003000 INTL 20091112) Jun 22 19:31:32 Tower kernel: ACPI: Interpreter enabled Jun 22 19:31:32 Tower kernel: ACPI: (supports S0 S3 S5) Jun 22 19:31:32 Tower kernel: ACPI: Using IOAPIC for interrupt routing Jun 22 19:31:32 Tower kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug Jun 22 19:31:32 Tower kernel: ACPI: Enabled 9 GPEs in block 00 to 3F Jun 22 19:31:32 Tower kernel: ACPI: Power Resource [FN00] (off) Jun 22 19:31:32 Tower kernel: ACPI: Power Resource [FN01] (off) Jun 22 19:31:32 Tower kernel: ACPI: Power Resource [FN02] (off) Jun 22 19:31:32 Tower kernel: ACPI: Power Resource [FN03] (off) Jun 22 19:31:32 Tower kernel: ACPI: Power Resource [FN04] (off) Jun 22 19:31:32 Tower kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e]) Jun 22 19:31:32 Tower kernel: acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] Jun 22 19:31:32 Tower kernel: acpi PNP0A08:00: _OSC: platform does not support [PCIeHotplug PME] Jun 22 19:31:32 Tower kernel: acpi PNP0A08:00: _OSC: OS now controls [AER PCIeCapability] Jun 22 19:31:32 Tower kernel: acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration Jun 22 19:31:32 Tower kernel: PCI host bridge to bus 0000:00 Jun 22 19:31:32 Tower kernel: pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7 window] Jun 22 19:31:32 Tower kernel: pci_bus 0000:00: root bus resource [io 0x0d00-0xffff window] Jun 22 19:31:32 Tower kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window] Jun 22 19:31:32 Tower kernel: pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff window] Jun 22 19:31:32 Tower kernel: pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff window] Jun 22 19:31:32 Tower kernel: pci_bus 0000:00: root bus resource [mem 0x000e0000-0x000e3fff window] Jun 22 19:31:32 Tower kernel: pci_bus 0000:00: root bus resource [mem 0x000e4000-0x000e7fff window] Jun 22 19:31:32 Tower kernel: pci_bus 0000:00: root bus resource [mem 0xcf200000-0xfeafffff window] Jun 22 19:31:32 Tower kernel: pci_bus 0000:00: root bus resource [bus 00-7e] Jun 22 19:31:32 Tower kernel: pci 0000:00:00.0: [8086:0c00] type 00 class 0x060000 Jun 22 19:31:32 Tower kernel: pci 0000:00:01.0: [8086:0c01] type 01 class 0x060400 Jun 22 19:31:32 Tower kernel: pci 0000:00:01.0: PME# supported from D0 D3hot D3cold Jun 22 19:31:32 Tower kernel: pci 0000:00:02.0: [8086:0412] type 00 class 0x030000 Jun 22 19:31:32 Tower kernel: pci 0000:00:02.0: reg 0x10: [mem 0xef800000-0xefbfffff 64bit] Jun 22 19:31:32 Tower kernel: pci 0000:00:02.0: reg 0x18: [mem 0xd0000000-0xdfffffff 64bit pref] Jun 22 19:31:32 Tower kernel: pci 0000:00:02.0: reg 0x20: [io 0xf000-0xf03f] Jun 22 19:31:32 Tower kernel: pci 0000:00:03.0: [8086:0c0c] type 00 class 0x040300 Jun 22 19:31:32 Tower kernel: pci 0000:00:03.0: reg 0x10: [mem 0xefe34000-0xefe37fff 64bit] Jun 22 19:31:32 Tower kernel: pci 0000:00:14.0: [8086:8c31] type 00 class 0x0c0330 Jun 22 19:31:32 Tower kernel: pci 0000:00:14.0: reg 0x10: [mem 0xefe20000-0xefe2ffff 64bit] Jun 22 19:31:32 Tower kernel: pci 0000:00:14.0: PME# supported from D3hot D3cold Jun 22 19:31:32 Tower kernel: pci 0000:00:16.0: [8086:8c3a] type 00 class 0x078000 Jun 22 19:31:32 Tower kernel: pci 0000:00:16.0: reg 0x10: [mem 0xefe3f000-0xefe3f00f 64bit] Jun 22 19:31:32 Tower kernel: pci 0000:00:16.0: PME# supported from D0 D3hot D3cold Jun 22 19:31:32 Tower kernel: pci 0000:00:19.0: [8086:153b] type 00 class 0x020000 Jun 22 19:31:32 Tower kernel: pci 0000:00:19.0: reg 0x10: [mem 0xefe00000-0xefe1ffff] Jun 22 19:31:32 Tower kernel: pci 0000:00:19.0: reg 0x14: [mem 0xefe3d000-0xefe3dfff] Jun 22 19:31:32 Tower kernel: pci 0000:00:19.0: reg 0x18: [io 0xf080-0xf09f] Jun 22 19:31:32 Tower kernel: pci 0000:00:19.0: PME# supported from D0 D3hot D3cold Jun 22 19:31:32 Tower kernel: pci 0000:00:1a.0: [8086:8c2d] type 00 class 0x0c0320 Jun 22 19:31:32 Tower kernel: pci 0000:00:1a.0: reg 0x10: [mem 0xefe3c000-0xefe3c3ff] Jun 22 19:31:32 Tower kernel: pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold Jun 22 19:31:32 Tower kernel: pci 0000:00:1b.0: [8086:8c20] type 00 class 0x040300 Jun 22 19:31:32 Tower kernel: pci 0000:00:1b.0: reg 0x10: [mem 0xefe30000-0xefe33fff 64bit] Jun 22 19:31:32 Tower kernel: pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold Jun 22 19:31:32 Tower kernel: pci 0000:00:1c.0: [8086:8c10] type 01 class 0x060400 Jun 22 19:31:32 Tower kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold Jun 22 19:31:32 Tower kernel: pci 0000:00:1c.5: [8086:8c1a] type 01 class 0x060400 Jun 22 19:31:32 Tower kernel: pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold Jun 22 19:31:32 Tower kernel: pci 0000:00:1d.0: [8086:8c26] type 00 class 0x0c0320 Jun 22 19:31:32 Tower kernel: pci 0000:00:1d.0: reg 0x10: [mem 0xefe3b000-0xefe3b3ff] Jun 22 19:31:32 Tower kernel: pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold Jun 22 19:31:32 Tower kernel: pci 0000:00:1f.0: [8086:8c44] type 00 class 0x060100 Jun 22 19:31:32 Tower kernel: pci 0000:00:1f.2: [8086:8c02] type 00 class 0x010601 Jun 22 19:31:32 Tower kernel: pci 0000:00:1f.2: reg 0x10: [io 0xf0d0-0xf0d7] Jun 22 19:31:32 Tower kernel: pci 0000:00:1f.2: reg 0x14: [io 0xf0c0-0xf0c3] Jun 22 19:31:32 Tower kernel: pci 0000:00:1f.2: reg 0x18: [io 0xf0b0-0xf0b7] Jun 22 19:31:32 Tower kernel: pci 0000:00:1f.2: reg 0x1c: [io 0xf0a0-0xf0a3] Jun 22 19:31:32 Tower kernel: pci 0000:00:1f.2: reg 0x20: [io 0xf060-0xf07f] Jun 22 19:31:32 Tower kernel: pci 0000:00:1f.2: reg 0x24: [mem 0xefe3a000-0xefe3a7ff] Jun 22 19:31:32 Tower kernel: pci 0000:00:1f.2: PME# supported from D3hot Jun 22 19:31:32 Tower kernel: pci 0000:00:1f.3: [8086:8c22] type 00 class 0x0c0500 Jun 22 19:31:32 Tower kernel: pci 0000:00:1f.3: reg 0x10: [mem 0xefe39000-0xefe390ff 64bit] Jun 22 19:31:32 Tower kernel: pci 0000:00:1f.3: reg 0x20: [io 0xf040-0xf05f] Jun 22 19:31:32 Tower kernel: pci 0000:01:00.0: [1000:0072] type 00 class 0x010700 Jun 22 19:31:32 Tower kernel: pci 0000:01:00.0: reg 0x10: [io 0xe000-0xe0ff] Jun 22 19:31:32 Tower kernel: pci 0000:01:00.0: reg 0x14: [mem 0xefdc0000-0xefdc3fff 64bit] Jun 22 19:31:32 Tower kernel: pci 0000:01:00.0: reg 0x1c: [mem 0xefd80000-0xefdbffff 64bit] Jun 22 19:31:32 Tower kernel: pci 0000:01:00.0: reg 0x30: [mem 0xefd00000-0xefd7ffff pref] Jun 22 19:31:32 Tower kernel: pci 0000:01:00.0: supports D1 D2 Jun 22 19:31:32 Tower kernel: pci 0000:01:00.0: reg 0x174: [mem 0x00000000-0x00003fff 64bit] Jun 22 19:31:32 Tower kernel: pci 0000:01:00.0: VF(n) BAR0 space: [mem 0x00000000-0x0003ffff 64bit] (contains BAR0 for 16 VFs) Jun 22 19:31:32 Tower kernel: pci 0000:01:00.0: reg 0x17c: [mem 0x00000000-0x0003ffff 64bit] Jun 22 19:31:32 Tower kernel: pci 0000:01:00.0: VF(n) BAR2 space: [mem 0x00000000-0x003fffff 64bit] (contains BAR2 for 16 VFs) Jun 22 19:31:32 Tower kernel: pci 0000:00:01.0: PCI bridge to [bus 01] Jun 22 19:31:32 Tower kernel: pci 0000:00:01.0: bridge window [io 0xe000-0xefff] Jun 22 19:31:32 Tower kernel: pci 0000:00:01.0: bridge window [mem 0xefd00000-0xefdfffff] Jun 22 19:31:32 Tower kernel: pci 0000:00:1c.0: PCI bridge to [bus 02] Jun 22 19:31:32 Tower kernel: pci 0000:03:00.0: [1b21:0612] type 00 class 0x010601 Jun 22 19:31:32 Tower kernel: pci 0000:03:00.0: reg 0x10: [io 0xd050-0xd057] Jun 22 19:31:32 Tower kernel: pci 0000:03:00.0: reg 0x14: [io 0xd040-0xd043] Jun 22 19:31:32 Tower kernel: pci 0000:03:00.0: reg 0x18: [io 0xd030-0xd037] Jun 22 19:31:32 Tower kernel: pci 0000:03:00.0: reg 0x1c: [io 0xd020-0xd023] Jun 22 19:31:32 Tower kernel: pci 0000:03:00.0: reg 0x20: [io 0xd000-0xd01f] Jun 22 19:31:32 Tower kernel: pci 0000:03:00.0: reg 0x24: [mem 0xefc00000-0xefc001ff] Jun 22 19:31:32 Tower kernel: pci 0000:00:1c.5: PCI bridge to [bus 03] Jun 22 19:31:32 Tower kernel: pci 0000:00:1c.5: bridge window [io 0xd000-0xdfff] Jun 22 19:31:32 Tower kernel: pci 0000:00:1c.5: bridge window [mem 0xefc00000-0xefcfffff] Jun 22 19:31:32 Tower kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15) Jun 22 19:31:32 Tower kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 *4 5 6 7 10 11 12 14 15) Jun 22 19:31:32 Tower kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 *6 7 10 11 12 14 15) Jun 22 19:31:32 Tower kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 11 12 14 *15) Jun 22 19:31:32 Tower kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 *5 6 7 10 11 12 14 15) Jun 22 19:31:32 Tower kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 *10 11 12 14 15) Jun 22 19:31:32 Tower kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs *3 4 5 6 7 10 11 12 14 15) Jun 22 19:31:32 Tower kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 *14 15) Jun 22 19:31:32 Tower kernel: pci 0000:00:02.0: vgaarb: setting as boot VGA device Jun 22 19:31:32 Tower kernel: pci 0000:00:02.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none Jun 22 19:31:32 Tower kernel: pci 0000:00:02.0: vgaarb: bridge control possible Jun 22 19:31:32 Tower kernel: vgaarb: loaded Jun 22 19:31:32 Tower kernel: SCSI subsystem initialized Jun 22 19:31:32 Tower kernel: libata version 3.00 loaded. Jun 22 19:31:32 Tower kernel: ACPI: bus type USB registered Jun 22 19:31:32 Tower kernel: usbcore: registered new interface driver usbfs Jun 22 19:31:32 Tower kernel: usbcore: registered new interface driver hub Jun 22 19:31:32 Tower kernel: usbcore: registered new device driver usb Jun 22 19:31:32 Tower kernel: EDAC MC: Ver: 3.0.0 Jun 22 19:31:32 Tower kernel: PCI: Using ACPI for IRQ routing Jun 22 19:31:32 Tower kernel: PCI: pci_cache_line_size set to 64 bytes Jun 22 19:31:32 Tower kernel: e820: reserve RAM buffer [mem 0x0009c400-0x0009ffff] Jun 22 19:31:32 Tower kernel: e820: reserve RAM buffer [mem 0xb3ad4000-0xb3ffffff] Jun 22 19:31:32 Tower kernel: e820: reserve RAM buffer [mem 0xb3f35000-0xb3ffffff] Jun 22 19:31:32 Tower kernel: e820: reserve RAM buffer [mem 0xc8710000-0xcbffffff] Jun 22 19:31:32 Tower kernel: e820: reserve RAM buffer [mem 0xca000000-0xcbffffff] Jun 22 19:31:32 Tower kernel: e820: reserve RAM buffer [mem 0x42fe00000-0x42fffffff] Jun 22 19:31:32 Tower kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0 Jun 22 19:31:32 Tower kernel: hpet0: 8 comparators, 64-bit 14.318180 MHz counter Jun 22 19:31:32 Tower kernel: clocksource: Switched to clocksource hpet Jun 22 19:31:32 Tower kernel: FS-Cache: Loaded Jun 22 19:31:32 Tower kernel: pnp: PnP ACPI init Jun 22 19:31:32 Tower kernel: system 00:00: [mem 0xfed40000-0xfed44fff] has been reserved Jun 22 19:31:32 Tower kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active) Jun 22 19:31:32 Tower kernel: system 00:01: [io 0x0680-0x069f] has been reserved Jun 22 19:31:32 Tower kernel: system 00:01: [io 0xffff] has been reserved Jun 22 19:31:32 Tower kernel: system 00:01: [io 0xffff] has been reserved Jun 22 19:31:32 Tower kernel: system 00:01: [io 0xffff] has been reserved Jun 22 19:31:32 Tower kernel: system 00:01: [io 0x1c00-0x1cfe] has been reserved Jun 22 19:31:32 Tower kernel: system 00:01: [io 0x1d00-0x1dfe] has been reserved Jun 22 19:31:32 Tower kernel: system 00:01: [io 0x1e00-0x1efe] has been reserved Jun 22 19:31:32 Tower kernel: system 00:01: [io 0x1f00-0x1ffe] has been reserved Jun 22 19:31:32 Tower kernel: system 00:01: [io 0x1800-0x18fe] has been reserved Jun 22 19:31:32 Tower kernel: system 00:01: [io 0x164e-0x164f] has been reserved Jun 22 19:31:32 Tower kernel: system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active) Jun 22 19:31:32 Tower kernel: pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active) Jun 22 19:31:32 Tower kernel: system 00:03: [io 0x1854-0x1857] has been reserved Jun 22 19:31:32 Tower kernel: system 00:03: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active) Jun 22 19:31:32 Tower kernel: system 00:04: [io 0x0290-0x029f] has been reserved Jun 22 19:31:32 Tower kernel: system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active) Jun 22 19:31:32 Tower kernel: system 00:05: [io 0x04d0-0x04d1] has been reserved Jun 22 19:31:32 Tower kernel: system 00:05: Plug and Play ACPI device, IDs PNP0c02 (active) Jun 22 19:31:32 Tower kernel: system 00:06: [mem 0xfed1c000-0xfed1ffff] has been reserved Jun 22 19:31:32 Tower kernel: system 00:06: [mem 0xfed10000-0xfed17fff] has been reserved Jun 22 19:31:32 Tower kernel: system 00:06: [mem 0xfed18000-0xfed18fff] has been reserved Jun 22 19:31:32 Tower kernel: system 00:06: [mem 0xfed19000-0xfed19fff] has been reserved Jun 22 19:31:32 Tower kernel: system 00:06: [mem 0xf0000000-0xf7ffffff] has been reserved Jun 22 19:31:32 Tower kernel: system 00:06: [mem 0xfed20000-0xfed3ffff] has been reserved Jun 22 19:31:32 Tower kernel: system 00:06: [mem 0xfed90000-0xfed93fff] has been reserved Jun 22 19:31:32 Tower kernel: system 00:06: [mem 0xfed45000-0xfed8ffff] has been reserved Jun 22 19:31:32 Tower kernel: system 00:06: [mem 0xff000000-0xffffffff] has been reserved Jun 22 19:31:32 Tower kernel: system 00:06: [mem 0xfee00000-0xfeefffff] could not be reserved Jun 22 19:31:32 Tower kernel: system 00:06: [mem 0xeffdf000-0xeffdffff] has been reserved Jun 22 19:31:32 Tower kernel: system 00:06: [mem 0xeffe0000-0xeffeffff] has been reserved Jun 22 19:31:32 Tower kernel: system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active) Jun 22 19:31:32 Tower kernel: pnp: PnP ACPI: found 7 devices Jun 22 19:31:32 Tower kernel: clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns Jun 22 19:31:32 Tower kernel: pci_bus 0000:00: max bus depth: 1 pci_try_num: 2 Jun 22 19:31:32 Tower kernel: pci 0000:01:00.0: BAR 9: no space for [mem size 0x00400000 64bit] Jun 22 19:31:32 Tower kernel: pci 0000:01:00.0: BAR 9: failed to assign [mem size 0x00400000 64bit] Jun 22 19:31:32 Tower kernel: pci 0000:01:00.0: BAR 7: no space for [mem size 0x00040000 64bit] Jun 22 19:31:32 Tower kernel: pci 0000:01:00.0: BAR 7: failed to assign [mem size 0x00040000 64bit] Jun 22 19:31:32 Tower kernel: pci 0000:00:01.0: PCI bridge to [bus 01] Jun 22 19:31:32 Tower kernel: pci 0000:00:01.0: bridge window [io 0xe000-0xefff] Jun 22 19:31:32 Tower kernel: pci 0000:00:01.0: bridge window [mem 0xefd00000-0xefdfffff] Jun 22 19:31:32 Tower kernel: pci 0000:00:1c.0: PCI bridge to [bus 02] Jun 22 19:31:32 Tower kernel: pci 0000:00:1c.5: PCI bridge to [bus 03] Jun 22 19:31:32 Tower kernel: pci 0000:00:1c.5: bridge window [io 0xd000-0xdfff] Jun 22 19:31:32 Tower kernel: pci 0000:00:1c.5: bridge window [mem 0xefc00000-0xefcfffff] Jun 22 19:31:32 Tower kernel: pci_bus 0000:00: No. 2 try to assign unassigned res Jun 22 19:31:32 Tower kernel: release child resource [mem 0xefd00000-0xefd7ffff pref] Jun 22 19:31:32 Tower kernel: release child resource [mem 0xefd80000-0xefdbffff 64bit] Jun 22 19:31:32 Tower kernel: release child resource [mem 0xefdc0000-0xefdc3fff 64bit] Jun 22 19:31:32 Tower kernel: pci 0000:00:01.0: resource 14 [mem 0xefd00000-0xefdfffff] released Jun 22 19:31:32 Tower kernel: pci 0000:00:01.0: PCI bridge to [bus 01] Jun 22 19:31:32 Tower kernel: pci 0000:00:01.0: bridge window [mem 0x00100000-0x001fffff] to [bus 01] add_size 500000 add_align 100000 Jun 22 19:31:32 Tower kernel: pci 0000:00:01.0: BAR 14: assigned [mem 0xcf200000-0xcf7fffff] Jun 22 19:31:32 Tower kernel: pci 0000:01:00.0: BAR 6: assigned [mem 0xcf200000-0xcf27ffff pref] Jun 22 19:31:32 Tower kernel: pci 0000:01:00.0: BAR 3: assigned [mem 0xcf280000-0xcf2bffff 64bit] Jun 22 19:31:32 Tower kernel: pci 0000:01:00.0: BAR 9: assigned [mem 0xcf2c0000-0xcf6bffff 64bit] Jun 22 19:31:32 Tower kernel: pci 0000:01:00.0: BAR 1: assigned [mem 0xcf6c0000-0xcf6c3fff 64bit] Jun 22 19:31:32 Tower kernel: pci 0000:01:00.0: BAR 7: assigned [mem 0xcf6c4000-0xcf703fff 64bit] Jun 22 19:31:32 Tower kernel: pci 0000:00:01.0: PCI bridge to [bus 01] Jun 22 19:31:32 Tower kernel: pci 0000:00:01.0: bridge window [io 0xe000-0xefff] Jun 22 19:31:32 Tower kernel: pci 0000:00:01.0: bridge window [mem 0xcf200000-0xcf7fffff] Jun 22 19:31:32 Tower kernel: pci 0000:00:1c.0: PCI bridge to [bus 02] Jun 22 19:31:32 Tower kernel: pci 0000:00:1c.5: PCI bridge to [bus 03] Jun 22 19:31:32 Tower kernel: pci 0000:00:1c.5: bridge window [io 0xd000-0xdfff] Jun 22 19:31:32 Tower kernel: pci 0000:00:1c.5: bridge window [mem 0xefc00000-0xefcfffff] Jun 22 19:31:32 Tower kernel: pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7 window] Jun 22 19:31:32 Tower kernel: pci_bus 0000:00: resource 5 [io 0x0d00-0xffff window] Jun 22 19:31:32 Tower kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window] Jun 22 19:31:32 Tower kernel: pci_bus 0000:00: resource 7 [mem 0x000d8000-0x000dbfff window] Jun 22 19:31:32 Tower kernel: pci_bus 0000:00: resource 8 [mem 0x000dc000-0x000dffff window] Jun 22 19:31:32 Tower kernel: pci_bus 0000:00: resource 9 [mem 0x000e0000-0x000e3fff window] Jun 22 19:31:32 Tower kernel: pci_bus 0000:00: resource 10 [mem 0x000e4000-0x000e7fff window] Jun 22 19:31:32 Tower kernel: pci_bus 0000:00: resource 11 [mem 0xcf200000-0xfeafffff window] Jun 22 19:31:32 Tower kernel: pci_bus 0000:01: resource 0 [io 0xe000-0xefff] Jun 22 19:31:32 Tower kernel: pci_bus 0000:01: resource 1 [mem 0xcf200000-0xcf7fffff] Jun 22 19:31:32 Tower kernel: pci_bus 0000:03: resource 0 [io 0xd000-0xdfff] Jun 22 19:31:32 Tower kernel: pci_bus 0000:03: resource 1 [mem 0xefc00000-0xefcfffff] Jun 22 19:31:32 Tower kernel: NET: Registered protocol family 2 Jun 22 19:31:32 Tower kernel: TCP established hash table entries: 131072 (order: 8, 1048576 bytes) Jun 22 19:31:32 Tower kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) Jun 22 19:31:32 Tower kernel: TCP: Hash tables configured (established 131072 bind 65536) Jun 22 19:31:32 Tower kernel: UDP hash table entries: 8192 (order: 6, 262144 bytes) Jun 22 19:31:32 Tower kernel: UDP-Lite hash table entries: 8192 (order: 6, 262144 bytes) Jun 22 19:31:32 Tower kernel: NET: Registered protocol family 1 Jun 22 19:31:32 Tower kernel: pci 0000:00:02.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff] Jun 22 19:31:32 Tower kernel: PCI: CLS 64 bytes, default 64 Jun 22 19:31:32 Tower kernel: Unpacking initramfs... Jun 22 19:31:32 Tower kernel: Freeing initrd memory: 80448K Jun 22 19:31:32 Tower kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB) Jun 22 19:31:32 Tower kernel: software IO TLB [mem 0xc4710000-0xc8710000] (64MB) mapped at [ffff8800c4710000-ffff8800c870ffff] Jun 22 19:31:32 Tower kernel: workingset: timestamp_bits=40 max_order=22 bucket_order=0 Jun 22 19:31:32 Tower kernel: squashfs: version 4.0 (2009/01/31) Phillip Lougher Jun 22 19:31:32 Tower kernel: fuse init (API version 7.26) Jun 22 19:31:32 Tower kernel: Key type asymmetric registered Jun 22 19:31:32 Tower kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) Jun 22 19:31:32 Tower kernel: io scheduler noop registered (default) Jun 22 19:31:32 Tower kernel: io scheduler deadline registered Jun 22 19:31:32 Tower kernel: io scheduler cfq registered Jun 22 19:31:32 Tower kernel: io scheduler mq-deadline registered Jun 22 19:31:32 Tower kernel: io scheduler kyber registered Jun 22 19:31:32 Tower kernel: intel_idle: MWAIT substates: 0x42120 Jun 22 19:31:32 Tower kernel: intel_idle: v0.4.1 model 0x3C Jun 22 19:31:32 Tower kernel: intel_idle: lapic_timer_reliable_states 0xffffffff Jun 22 19:31:32 Tower kernel: ipmi message handler version 39.2 Jun 22 19:31:32 Tower kernel: Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled Jun 22 19:31:32 Tower kernel: lp: driver loaded but no devices found Jun 22 19:31:32 Tower kernel: Hangcheck: starting hangcheck timer 0.9.1 (tick is 180 seconds, margin is 60 seconds). Jun 22 19:31:32 Tower kernel: AMD IOMMUv2 driver by Joerg Roedel <jroedel@suse.de> Jun 22 19:31:32 Tower kernel: AMD IOMMUv2 functionality not available on this system Jun 22 19:31:32 Tower kernel: loop: module loaded Jun 22 19:31:32 Tower kernel: VFIO - User Level meta-driver version: 0.3 Jun 22 19:31:32 Tower kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver Jun 22 19:31:32 Tower kernel: ehci-pci: EHCI PCI platform driver Jun 22 19:31:32 Tower kernel: ehci-pci 0000:00:1a.0: EHCI Host Controller Jun 22 19:31:32 Tower kernel: ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1 Jun 22 19:31:32 Tower kernel: ehci-pci 0000:00:1a.0: debug port 2 Jun 22 19:31:32 Tower kernel: ehci-pci 0000:00:1a.0: cache line size of 64 is not supported Jun 22 19:31:32 Tower kernel: ehci-pci 0000:00:1a.0: irq 16, io mem 0xefe3c000 Jun 22 19:31:32 Tower kernel: ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00 Jun 22 19:31:32 Tower kernel: hub 1-0:1.0: USB hub found Jun 22 19:31:32 Tower kernel: hub 1-0:1.0: 2 ports detected Jun 22 19:31:32 Tower kernel: ehci-pci 0000:00:1d.0: EHCI Host Controller Jun 22 19:31:32 Tower kernel: ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2 Jun 22 19:31:32 Tower kernel: ehci-pci 0000:00:1d.0: debug port 2 Jun 22 19:31:32 Tower kernel: ehci-pci 0000:00:1d.0: cache line size of 64 is not supported Jun 22 19:31:32 Tower kernel: ehci-pci 0000:00:1d.0: irq 23, io mem 0xefe3b000 Jun 22 19:31:32 Tower kernel: ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00 Jun 22 19:31:32 Tower kernel: hub 2-0:1.0: USB hub found Jun 22 19:31:32 Tower kernel: hub 2-0:1.0: 2 ports detected Jun 22 19:31:32 Tower kernel: ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver Jun 22 19:31:32 Tower kernel: ohci-pci: OHCI PCI platform driver Jun 22 19:31:32 Tower kernel: uhci_hcd: USB Universal Host Controller Interface driver Jun 22 19:31:32 Tower kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller Jun 22 19:31:32 Tower kernel: xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 3 Jun 22 19:31:32 Tower kernel: xhci_hcd 0000:00:14.0: hcc params 0x200077c1 hci version 0x100 quirks 0x00009810 Jun 22 19:31:32 Tower kernel: xhci_hcd 0000:00:14.0: cache line size of 64 is not supported Jun 22 19:31:32 Tower kernel: hub 3-0:1.0: USB hub found Jun 22 19:31:32 Tower kernel: hub 3-0:1.0: 14 ports detected Jun 22 19:31:32 Tower kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller Jun 22 19:31:32 Tower kernel: xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 4 Jun 22 19:31:32 Tower kernel: hub 4-0:1.0: USB hub found Jun 22 19:31:32 Tower kernel: hub 4-0:1.0: 6 ports detected Jun 22 19:31:32 Tower kernel: usbcore: registered new interface driver usb-storage Jun 22 19:31:32 Tower kernel: i8042: PNP: No PS/2 controller found. Jun 22 19:31:32 Tower kernel: mousedev: PS/2 mouse device common for all mice Jun 22 19:31:32 Tower kernel: usbcore: registered new interface driver synaptics_usb Jun 22 19:31:32 Tower kernel: input: PC Speaker as /devices/platform/pcspkr/input/input0 Jun 22 19:31:32 Tower kernel: rtc_cmos 00:02: RTC can wake from S4 Jun 22 19:31:32 Tower kernel: rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0 Jun 22 19:31:32 Tower kernel: rtc_cmos 00:02: alarms up to one month, y3k, 242 bytes nvram, hpet irqs Jun 22 19:31:32 Tower kernel: IR NEC protocol handler initialized Jun 22 19:31:32 Tower kernel: IR RC5(x/sz) protocol handler initialized Jun 22 19:31:32 Tower kernel: IR RC6 protocol handler initialized Jun 22 19:31:32 Tower kernel: IR JVC protocol handler initialized Jun 22 19:31:32 Tower kernel: IR Sony protocol handler initialized Jun 22 19:31:32 Tower kernel: IR SANYO protocol handler initialized Jun 22 19:31:32 Tower kernel: IR Sharp protocol handler initialized Jun 22 19:31:32 Tower kernel: IR MCE Keyboard/mouse protocol handler initialized Jun 22 19:31:32 Tower kernel: IR XMP protocol handler initialized Jun 22 19:31:32 Tower kernel: intel_pstate: Intel P-state driver initializing Jun 22 19:31:32 Tower kernel: hidraw: raw HID events driver (C) Jiri Kosina Jun 22 19:31:32 Tower kernel: usbcore: registered new interface driver usbhid Jun 22 19:31:32 Tower kernel: usbhid: USB HID core driver Jun 22 19:31:32 Tower kernel: Netfilter messages via NETLINK v0.30. Jun 22 19:31:32 Tower kernel: nfnl_acct: registering with nfnetlink. Jun 22 19:31:32 Tower kernel: nf_conntrack version 0.5.0 (65536 buckets, 262144 max) Jun 22 19:31:32 Tower kernel: nf_tables: (c) 2007-2009 Patrick McHardy <kaber@trash.net> Jun 22 19:31:32 Tower kernel: nf_tables_compat: (c) 2012 Pablo Neira Ayuso <pablo@netfilter.org> Jun 22 19:31:32 Tower kernel: xt_time: kernel timezone is -0000 Jun 22 19:31:32 Tower kernel: ipip: IPv4 and MPLS over IPv4 tunneling driver Jun 22 19:31:32 Tower kernel: gre: GRE over IPv4 demultiplexor driver Jun 22 19:31:32 Tower kernel: ip_gre: GRE over IPv4 tunneling driver Jun 22 19:31:32 Tower kernel: IPv4 over IPsec tunneling driver Jun 22 19:31:32 Tower kernel: Initializing XFRM netlink socket Jun 22 19:31:32 Tower kernel: NET: Registered protocol family 10 Jun 22 19:31:32 Tower kernel: Segment Routing with IPv6 Jun 22 19:31:32 Tower kernel: sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver Jun 22 19:31:32 Tower kernel: NET: Registered protocol family 17 Jun 22 19:31:32 Tower kernel: Bridge firewalling registered Jun 22 19:31:32 Tower kernel: 8021q: 802.1Q VLAN Support v1.8 Jun 22 19:31:32 Tower kernel: 9pnet: Installing 9P2000 support Jun 22 19:31:32 Tower kernel: Key type dns_resolver registered Jun 22 19:31:32 Tower kernel: microcode: sig=0x306c3, pf=0x2, revision=0x22 Jun 22 19:31:32 Tower kernel: microcode: Microcode Update Driver: v2.2. Jun 22 19:31:32 Tower kernel: sched_clock: Marking stable (6612937668, 0)->(6618307204, -5369536) Jun 22 19:31:32 Tower kernel: registered taskstats version 1 Jun 22 19:31:32 Tower kernel: Btrfs loaded, crc32c=crc32c-generic Jun 22 19:31:32 Tower kernel: rtc_cmos 00:02: setting system clock to 2018-06-23 00:31:26 UTC (1529713886) Jun 22 19:31:32 Tower kernel: usb 1-1: new high-speed USB device number 2 using ehci-pci Jun 22 19:31:32 Tower kernel: usb 3-3: new high-speed USB device number 2 using xhci_hcd Jun 22 19:31:32 Tower kernel: usb 2-1: new high-speed USB device number 2 using ehci-pci Jun 22 19:31:32 Tower kernel: hub 1-1:1.0: USB hub found Jun 22 19:31:32 Tower kernel: hub 1-1:1.0: 6 ports detected Jun 22 19:31:32 Tower kernel: hub 2-1:1.0: USB hub found Jun 22 19:31:32 Tower kernel: hub 2-1:1.0: 8 ports detected Jun 22 19:31:32 Tower kernel: hub 3-3:1.0: USB hub found Jun 22 19:31:32 Tower kernel: hub 3-3:1.0: 4 ports detected Jun 22 19:31:32 Tower kernel: usb 4-3: new SuperSpeed USB device number 2 using xhci_hcd Jun 22 19:31:32 Tower kernel: usb 3-14: new full-speed USB device number 3 using xhci_hcd Jun 22 19:31:32 Tower kernel: hub 4-3:1.0: USB hub found Jun 22 19:31:32 Tower kernel: hub 4-3:1.0: 4 ports detected Jun 22 19:31:32 Tower kernel: input: Mini Keyboard as /devices/pci0000:00/0000:00:14.0/usb3/3-14/3-14:1.0/0003:1997:2433.0001/input/input1 Jun 22 19:31:32 Tower kernel: hid-generic 0003:1997:2433.0001: input,hidraw0: USB HID v1.01 Keyboard [ Mini Keyboard] on usb-0000:00:14.0-14/input0 Jun 22 19:31:32 Tower kernel: input: Mini Keyboard as /devices/pci0000:00/0000:00:14.0/usb3/3-14/3-14:1.1/0003:1997:2433.0002/input/input2 Jun 22 19:31:32 Tower kernel: usb 3-3.4: new high-speed USB device number 4 using xhci_hcd Jun 22 19:31:32 Tower kernel: tsc: Refined TSC clocksource calibration: 3606.257 MHz Jun 22 19:31:32 Tower kernel: clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x33fb6a3089e, max_idle_ns: 440795340235 ns Jun 22 19:31:32 Tower kernel: hid-generic 0003:1997:2433.0002: input,hidraw1: USB HID v1.01 Mouse [ Mini Keyboard] on usb-0000:00:14.0-14/input1 Jun 22 19:31:32 Tower kernel: usb-storage 3-3.4:1.0: USB Mass Storage device detected Jun 22 19:31:32 Tower kernel: scsi host0: usb-storage 3-3.4:1.0 Jun 22 19:31:32 Tower kernel: clocksource: Switched to clocksource tsc Jun 22 19:31:32 Tower kernel: scsi 0:0:0:0: Direct-Access SanDisk Cruzer Fit 1.27 PQ: 0 ANSI: 6 Jun 22 19:31:32 Tower kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0 Jun 22 19:31:32 Tower kernel: sd 0:0:0:0: [sda] 31266816 512-byte logical blocks: (16.0 GB/14.9 GiB) Jun 22 19:31:32 Tower kernel: sd 0:0:0:0: [sda] Write Protect is off Jun 22 19:31:32 Tower kernel: sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00 Jun 22 19:31:32 Tower kernel: sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA Jun 22 19:31:32 Tower kernel: sda: sda1 Jun 22 19:31:32 Tower kernel: sd 0:0:0:0: [sda] Attached SCSI removable disk Jun 22 19:31:32 Tower kernel: floppy0: no floppy controllers found Jun 22 19:31:32 Tower kernel: Freeing unused kernel memory: 1080K Jun 22 19:31:32 Tower kernel: Write protecting the kernel read-only data: 12288k Jun 22 19:31:32 Tower kernel: Freeing unused kernel memory: 2012K Jun 22 19:31:32 Tower kernel: Freeing unused kernel memory: 96K Jun 22 19:31:32 Tower kernel: rodata_test: all tests were successful Jun 22 19:31:32 Tower kernel: random: crng init done Jun 22 19:31:32 Tower kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3 Jun 22 19:31:32 Tower kernel: ACPI: Power Button [PWRB] Jun 22 19:31:32 Tower kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4 Jun 22 19:31:32 Tower kernel: (NULL device *): hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info(). Jun 22 19:31:32 Tower kernel: thermal LNXTHERM:00: registered as thermal_zone0 Jun 22 19:31:32 Tower kernel: ACPI: Thermal Zone [TZ00] (28 C) Jun 22 19:31:32 Tower kernel: thermal LNXTHERM:01: registered as thermal_zone1 Jun 22 19:31:32 Tower kernel: ACPI: Thermal Zone [TZ01] (30 C) Jun 22 19:31:32 Tower kernel: ACPI: Power Button [PWRF] Jun 22 19:31:32 Tower kernel: RAPL PMU: API unit is 2^-32 Joules, 4 fixed counters, 655360 ms ovfl timer Jun 22 19:31:32 Tower kernel: RAPL PMU: hw unit of domain pp0-core 2^-14 Joules Jun 22 19:31:32 Tower kernel: RAPL PMU: hw unit of domain package 2^-14 Joules Jun 22 19:31:32 Tower kernel: RAPL PMU: hw unit of domain dram 2^-14 Joules Jun 22 19:31:32 Tower kernel: RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules Jun 22 19:31:32 Tower kernel: pps_core: LinuxPPS API ver. 1 registered Jun 22 19:31:32 Tower kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> Jun 22 19:31:32 Tower kernel: PTP clock support registered Jun 22 19:31:32 Tower kernel: i801_smbus 0000:00:1f.3: SPD Write Disable is set Jun 22 19:31:32 Tower kernel: i801_smbus 0000:00:1f.3: SMBus using PCI interrupt Jun 22 19:31:32 Tower kernel: ahci 0000:00:1f.2: version 3.0 Jun 22 19:31:32 Tower kernel: ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x3f impl SATA mode Jun 22 19:31:32 Tower kernel: ahci 0000:00:1f.2: flags: 64bit ncq led clo pio slum part ems apst Jun 22 19:31:32 Tower kernel: mpt3sas version 15.100.00.00 loaded Jun 22 19:31:32 Tower kernel: mpt3sas 0000:01:00.0: can't disable ASPM; OS doesn't have ASPM control Jun 22 19:31:32 Tower kernel: mpt2sas_cm0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (16303312 kB) Jun 22 19:31:32 Tower kernel: scsi host2: ahci Jun 22 19:31:32 Tower kernel: scsi host3: ahci Jun 22 19:31:32 Tower kernel: scsi host4: ahci Jun 22 19:31:32 Tower kernel: scsi host5: ahci Jun 22 19:31:32 Tower kernel: scsi host6: ahci Jun 22 19:31:32 Tower kernel: scsi host7: ahci Jun 22 19:31:32 Tower kernel: ata1: SATA max UDMA/133 abar m2048@0xefe3a000 port 0xefe3a100 irq 25 Jun 22 19:31:32 Tower kernel: ata2: SATA max UDMA/133 abar m2048@0xefe3a000 port 0xefe3a180 irq 25 Jun 22 19:31:32 Tower kernel: ata3: SATA max UDMA/133 abar m2048@0xefe3a000 port 0xefe3a200 irq 25 Jun 22 19:31:32 Tower kernel: ata4: SATA max UDMA/133 abar m2048@0xefe3a000 port 0xefe3a280 irq 25 Jun 22 19:31:32 Tower kernel: ata5: SATA max UDMA/133 abar m2048@0xefe3a000 port 0xefe3a300 irq 25 Jun 22 19:31:32 Tower kernel: ata6: SATA max UDMA/133 abar m2048@0xefe3a000 port 0xefe3a380 irq 25 Jun 22 19:31:32 Tower kernel: ahci 0000:03:00.0: SSS flag set, parallel bus scan disabled Jun 22 19:31:32 Tower kernel: ahci 0000:03:00.0: AHCI 0001.0200 32 slots 2 ports 6 Gbps 0x3 impl SATA mode Jun 22 19:31:32 Tower kernel: ahci 0000:03:00.0: flags: 64bit ncq sntf stag led clo pmp pio slum part ccc Jun 22 19:31:32 Tower kernel: scsi host8: ahci Jun 22 19:31:32 Tower kernel: scsi host9: ahci Jun 22 19:31:32 Tower kernel: ata7: SATA max UDMA/133 abar m512@0xefc00000 port 0xefc00100 irq 26 Jun 22 19:31:32 Tower kernel: ata8: SATA max UDMA/133 abar m512@0xefc00000 port 0xefc00180 irq 26 Jun 22 19:31:32 Tower kernel: e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k Jun 22 19:31:32 Tower kernel: e1000e: Copyright(c) 1999 - 2015 Intel Corporation. Jun 22 19:31:32 Tower kernel: e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode Jun 22 19:31:32 Tower kernel: mpt2sas_cm0: MSI-X vectors supported: 1, no of cores: 8, max_msix_vectors: -1 Jun 22 19:31:32 Tower kernel: mpt2sas0-msix0: PCI-MSI-X enabled: IRQ 28 Jun 22 19:31:32 Tower kernel: mpt2sas_cm0: iomem(0x00000000cf6c0000), mapped(0xffffc90001ad4000), size(16384) Jun 22 19:31:32 Tower kernel: mpt2sas_cm0: ioport(0x000000000000e000), size(256) Jun 22 19:31:32 Tower kernel: AVX2 version of gcm_enc/dec engaged. Jun 22 19:31:32 Tower kernel: AES CTR mode by8 optimization enabled Jun 22 19:31:32 Tower kernel: kvm: disabled by bios Jun 22 19:31:32 Tower kernel: e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): registered PHC clock Jun 22 19:31:32 Tower kernel: mpt2sas_cm0: sending message unit reset !! Jun 22 19:31:32 Tower kernel: mpt2sas_cm0: message unit reset: SUCCESS Jun 22 19:31:32 Tower kernel: kvm: disabled by bios Jun 22 19:31:32 Tower kernel: mpt2sas_cm0: Allocated physical memory: size(7579 kB) Jun 22 19:31:32 Tower kernel: mpt2sas_cm0: Current Controller Queue Depth(3364),Max Controller Queue Depth(3432) Jun 22 19:31:32 Tower kernel: mpt2sas_cm0: Scatter Gather Elements per IO(128) Jun 22 19:31:32 Tower kernel: e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 40:16:7e:25:dd:b9 Jun 22 19:31:32 Tower kernel: e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection Jun 22 19:31:32 Tower kernel: e1000e 0000:00:19.0 eth0: MAC: 11, PHY: 12, PBA No: FFFFFF-0FF Jun 22 19:31:32 Tower kernel: mpt2sas_cm0: LSISAS2008: FWVersion(20.00.07.00), ChipRevision(0x03), BiosVersion(07.39.02.00) Jun 22 19:31:32 Tower kernel: mpt2sas_cm0: Protocol=( Jun 22 19:31:32 Tower kernel: Initiator Jun 22 19:31:32 Tower kernel: ,Target Jun 22 19:31:32 Tower kernel: ), Jun 22 19:31:32 Tower kernel: Capabilities=( Jun 22 19:31:32 Tower kernel: TLR Jun 22 19:31:32 Tower kernel: ,EEDP Jun 22 19:31:32 Tower kernel: ,Snapshot Buffer Jun 22 19:31:32 Tower kernel: ,Diag Trace Buffer Jun 22 19:31:32 Tower kernel: ,Task Set Full Jun 22 19:31:32 Tower kernel: ,NCQ Jun 22 19:31:32 Tower kernel: ) Jun 22 19:31:32 Tower kernel: scsi host1: Fusion MPT SAS Host Jun 22 19:31:32 Tower kernel: mpt2sas_cm0: sending port enable !! Jun 22 19:31:32 Tower kernel: mpt2sas_cm0: host_add: handle(0x0001), sas_addr(0x500605b0044bc9c0), phys(8) Jun 22 19:31:32 Tower kernel: mpt2sas_cm0: port enable: SUCCESS Jun 22 19:31:32 Tower kernel: scsi 1:0:0:0: Direct-Access ATA HGST HUS726060AL T1E2 PQ: 0 ANSI: 6 Jun 22 19:31:32 Tower kernel: scsi 1:0:0:0: SATA: handle(0x000b), sas_addr(0x4433221107000000), phy(7), device_name(0x5000cca231c09e91) Jun 22 19:31:32 Tower kernel: scsi 1:0:0:0: SATA: enclosure_logical_id(0x500605b0044bc9c0), slot(4) Jun 22 19:31:32 Tower kernel: scsi 1:0:0:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y) Jun 22 19:31:32 Tower kernel: sd 1:0:0:0: Attached scsi generic sg1 type 0 Jun 22 19:31:32 Tower kernel: sd 1:0:0:0: [sdb] 11721045168 512-byte logical blocks: (6.00 TB/5.46 TiB) Jun 22 19:31:32 Tower kernel: scsi 1:0:1:0: Direct-Access ATA Hitachi HDS72404 A3B0 PQ: 0 ANSI: 6 Jun 22 19:31:32 Tower kernel: scsi 1:0:1:0: SATA: handle(0x0009), sas_addr(0x4433221105000000), phy(5), device_name(0x5000cca22bccf276) Jun 22 19:31:32 Tower kernel: scsi 1:0:1:0: SATA: enclosure_logical_id(0x500605b0044bc9c0), slot(6) Jun 22 19:31:32 Tower kernel: scsi 1:0:1:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y) Jun 22 19:31:32 Tower kernel: sd 1:0:0:0: [sdb] Write Protect is off Jun 22 19:31:32 Tower kernel: sd 1:0:0:0: [sdb] Mode Sense: 7f 00 10 08 Jun 22 19:31:32 Tower kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA Jun 22 19:31:32 Tower kernel: sd 1:0:1:0: Attached scsi generic sg2 type 0 Jun 22 19:31:32 Tower kernel: scsi 1:0:2:0: Direct-Access ATA Hitachi HDS5C404 A3B0 PQ: 0 ANSI: 6 Jun 22 19:31:32 Tower kernel: scsi 1:0:2:0: SATA: handle(0x000a), sas_addr(0x4433221106000000), phy(6), device_name(0x5000cca22ec3e184) Jun 22 19:31:32 Tower kernel: scsi 1:0:2:0: SATA: enclosure_logical_id(0x500605b0044bc9c0), slot(5) Jun 22 19:31:32 Tower kernel: scsi 1:0:2:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y) Jun 22 19:31:32 Tower kernel: sd 1:0:1:0: [sdc] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB) Jun 22 19:31:32 Tower kernel: sd 1:0:1:0: [sdc] 4096-byte physical blocks Jun 22 19:31:32 Tower kernel: sd 1:0:2:0: Attached scsi generic sg3 type 0 Jun 22 19:31:32 Tower kernel: sd 1:0:2:0: [sdd] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB) Jun 22 19:31:32 Tower kernel: sd 1:0:2:0: [sdd] 4096-byte physical blocks Jun 22 19:31:32 Tower kernel: sdb: sdb1 Jun 22 19:31:32 Tower kernel: sd 1:0:0:0: [sdb] Attached SCSI disk Jun 22 19:31:32 Tower kernel: ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jun 22 19:31:32 Tower kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jun 22 19:31:32 Tower kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jun 22 19:31:32 Tower kernel: ata1.00: ATA-9: WDC WD60EFRX-68MYMN1, WD-WX11D74RH18C, 82.00A82, max UDMA/133 Jun 22 19:31:32 Tower kernel: ata1.00: 11721045168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA Jun 22 19:31:32 Tower kernel: ata7: SATA link down (SStatus 0 SControl 300) Jun 22 19:31:32 Tower kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jun 22 19:31:32 Tower kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jun 22 19:31:32 Tower kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jun 22 19:31:32 Tower kernel: ata3.00: ATA-8: Hitachi HDS5C3020ALA632, ML2220F339LXKE, ML6OA800, max UDMA/133 Jun 22 19:31:32 Tower kernel: ata3.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA Jun 22 19:31:32 Tower kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170728/psargs-364) Jun 22 19:31:32 Tower kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT4._GTF, AE_NOT_FOUND (20170728/psparse-550) Jun 22 19:31:32 Tower kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170728/psargs-364) Jun 22 19:31:32 Tower kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT5._GTF, AE_NOT_FOUND (20170728/psparse-550) Jun 22 19:31:32 Tower kernel: ata1.00: configured for UDMA/133 Jun 22 19:31:32 Tower kernel: ata4.00: ATA-9: WDC WD60EFRX-68MYMN1, WD-WX11D74RH2PJ, 82.00A82, max UDMA/133 Jun 22 19:31:32 Tower kernel: ata4.00: 11721045168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA Jun 22 19:31:32 Tower kernel: scsi 2:0:0:0: Direct-Access ATA WDC WD60EFRX-68M 0A82 PQ: 0 ANSI: 5 Jun 22 19:31:32 Tower kernel: ata6.00: ATA-8: Hitachi HDS724040ALE640, PK1310PAG5ZPNJ, MJAOA3B0, max UDMA/133 Jun 22 19:31:32 Tower kernel: ata6.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA Jun 22 19:31:32 Tower kernel: sd 2:0:0:0: Attached scsi generic sg4 type 0 Jun 22 19:31:32 Tower kernel: sd 2:0:0:0: [sde] 11721045168 512-byte logical blocks: (6.00 TB/5.46 TiB) Jun 22 19:31:32 Tower kernel: sd 2:0:0:0: [sde] 4096-byte physical blocks Jun 22 19:31:32 Tower kernel: sd 2:0:0:0: [sde] Write Protect is off Jun 22 19:31:32 Tower kernel: sd 2:0:0:0: [sde] Mode Sense: 00 3a 00 00 Jun 22 19:31:32 Tower kernel: sd 2:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jun 22 19:31:32 Tower kernel: ata4.00: configured for UDMA/133 Jun 22 19:31:32 Tower kernel: ata3.00: configured for UDMA/133 Jun 22 19:31:32 Tower kernel: ata2.00: ATA-8: Hitachi HDS5C4040ALE630, PL1321LAG9AAVH, MPAOA3B0, max UDMA/133 Jun 22 19:31:32 Tower kernel: ata2.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA Jun 22 19:31:32 Tower kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170728/psargs-364) Jun 22 19:31:32 Tower kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT5._GTF, AE_NOT_FOUND (20170728/psparse-550) Jun 22 19:31:32 Tower kernel: ata6.00: configured for UDMA/133 Jun 22 19:31:32 Tower kernel: ata2.00: configured for UDMA/133 Jun 22 19:31:32 Tower kernel: scsi 3:0:0:0: Direct-Access ATA Hitachi HDS5C404 A3B0 PQ: 0 ANSI: 5 Jun 22 19:31:32 Tower kernel: sd 3:0:0:0: Attached scsi generic sg5 type 0 Jun 22 19:31:32 Tower kernel: sd 3:0:0:0: [sdf] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB) Jun 22 19:31:32 Tower kernel: sd 3:0:0:0: [sdf] 4096-byte physical blocks Jun 22 19:31:32 Tower kernel: sd 3:0:0:0: [sdf] Write Protect is off Jun 22 19:31:32 Tower kernel: sd 3:0:0:0: [sdf] Mode Sense: 00 3a 00 00 Jun 22 19:31:32 Tower kernel: sd 3:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jun 22 19:31:32 Tower kernel: scsi 4:0:0:0: Direct-Access ATA Hitachi HDS5C302 A800 PQ: 0 ANSI: 5 Jun 22 19:31:32 Tower kernel: sd 4:0:0:0: Attached scsi generic sg6 type 0 Jun 22 19:31:32 Tower kernel: sd 4:0:0:0: [sdg] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB) Jun 22 19:31:32 Tower kernel: scsi 5:0:0:0: Direct-Access ATA WDC WD60EFRX-68M 0A82 PQ: 0 ANSI: 5 Jun 22 19:31:32 Tower kernel: sd 4:0:0:0: [sdg] Write Protect is off Jun 22 19:31:32 Tower kernel: sd 5:0:0:0: Attached scsi generic sg7 type 0 Jun 22 19:31:32 Tower kernel: sd 5:0:0:0: [sdh] 11721045168 512-byte logical blocks: (6.00 TB/5.46 TiB) Jun 22 19:31:32 Tower kernel: sd 5:0:0:0: [sdh] 4096-byte physical blocks Jun 22 19:31:32 Tower kernel: sd 5:0:0:0: [sdh] Write Protect is off Jun 22 19:31:32 Tower kernel: sd 5:0:0:0: [sdh] Mode Sense: 00 3a 00 00 Jun 22 19:31:32 Tower kernel: sd 5:0:0:0: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jun 22 19:31:32 Tower kernel: sd 4:0:0:0: [sdg] Mode Sense: 00 3a 00 00 Jun 22 19:31:32 Tower kernel: sd 4:0:0:0: [sdg] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jun 22 19:31:32 Tower kernel: sdg: sdg1 Jun 22 19:31:32 Tower kernel: sd 4:0:0:0: [sdg] Attached SCSI disk Jun 22 19:31:32 Tower kernel: ata5.00: ATA-9: HGST HDN726060ALE614, K1KNJ6ND, APGNW7JH, max UDMA/133 Jun 22 19:31:32 Tower kernel: ata5.00: 11721045168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA Jun 22 19:31:32 Tower kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170728/psargs-364) Jun 22 19:31:32 Tower kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT4._GTF, AE_NOT_FOUND (20170728/psparse-550) Jun 22 19:31:32 Tower kernel: sdf: sdf1 Jun 22 19:31:32 Tower kernel: sd 3:0:0:0: [sdf] Attached SCSI disk Jun 22 19:31:32 Tower kernel: ata5.00: configured for UDMA/133 Jun 22 19:31:32 Tower kernel: scsi 6:0:0:0: Direct-Access ATA HGST HDN726060AL W7JH PQ: 0 ANSI: 5 Jun 22 19:31:32 Tower kernel: sd 6:0:0:0: Attached scsi generic sg8 type 0 Jun 22 19:31:32 Tower kernel: sd 6:0:0:0: [sdi] 11721045168 512-byte logical blocks: (6.00 TB/5.46 TiB) Jun 22 19:31:32 Tower kernel: sd 6:0:0:0: [sdi] 4096-byte physical blocks Jun 22 19:31:32 Tower kernel: sd 6:0:0:0: [sdi] Write Protect is off Jun 22 19:31:32 Tower kernel: sd 6:0:0:0: [sdi] Mode Sense: 00 3a 00 00 Jun 22 19:31:32 Tower kernel: sd 6:0:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jun 22 19:31:32 Tower kernel: scsi 7:0:0:0: Direct-Access ATA Hitachi HDS72404 A3B0 PQ: 0 ANSI: 5 Jun 22 19:31:32 Tower kernel: sd 7:0:0:0: Attached scsi generic sg9 type 0 Jun 22 19:31:32 Tower kernel: sd 7:0:0:0: [sdj] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB) Jun 22 19:31:32 Tower kernel: sd 7:0:0:0: [sdj] 4096-byte physical blocks Jun 22 19:31:32 Tower kernel: sd 7:0:0:0: [sdj] Write Protect is off Jun 22 19:31:32 Tower kernel: sd 7:0:0:0: [sdj] Mode Sense: 00 3a 00 00 Jun 22 19:31:32 Tower kernel: sd 7:0:0:0: [sdj] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jun 22 19:31:32 Tower kernel: sde: sde1 Jun 22 19:31:32 Tower kernel: sd 2:0:0:0: [sde] Attached SCSI disk Jun 22 19:31:32 Tower kernel: sdh: sdh1 Jun 22 19:31:32 Tower kernel: sd 5:0:0:0: [sdh] Attached SCSI disk Jun 22 19:31:32 Tower kernel: sdj: sdj1 Jun 22 19:31:32 Tower kernel: sd 7:0:0:0: [sdj] Attached SCSI disk Jun 22 19:31:32 Tower kernel: sdi: sdi1 Jun 22 19:31:32 Tower kernel: sd 6:0:0:0: [sdi] Attached SCSI disk Jun 22 19:31:32 Tower kernel: sd 1:0:1:0: [sdc] Write Protect is off Jun 22 19:31:32 Tower kernel: sd 1:0:1:0: [sdc] Mode Sense: 7f 00 10 08 Jun 22 19:31:32 Tower kernel: sd 1:0:1:0: [sdc] Write cache: enabled, read cache: enabled, supports DPO and FUA Jun 22 19:31:32 Tower kernel: sd 1:0:2:0: [sdd] Write Protect is off Jun 22 19:31:32 Tower kernel: sd 1:0:2:0: [sdd] Mode Sense: 7f 00 10 08 Jun 22 19:31:32 Tower kernel: sd 1:0:2:0: [sdd] Write cache: enabled, read cache: enabled, supports DPO and FUA Jun 22 19:31:32 Tower kernel: ata8: SATA link down (SStatus 0 SControl 300) Jun 22 19:31:32 Tower kernel: sdc: sdc1 Jun 22 19:31:32 Tower kernel: sdd: sdd1 Jun 22 19:31:32 Tower kernel: sd 1:0:1:0: [sdc] Attached SCSI disk Jun 22 19:31:32 Tower kernel: sd 1:0:2:0: [sdd] Attached SCSI disk Jun 22 19:31:32 Tower kernel: kvm: disabled by bios Jun 22 19:31:32 Tower kernel: kvm: disabled by bios Jun 22 19:31:32 Tower kernel: kvm: disabled by bios Jun 22 19:31:33 Tower rc.inet1: ip -4 addr add 127.0.0.1/8 dev lo Jun 22 19:31:33 Tower rc.inet1: ip -6 addr add ::1/128 dev lo Jun 22 19:31:33 Tower rc.inet1: ip link set lo up Jun 22 19:31:33 Tower rc.inet1: polling up to 60 sec for DHCP server on interface eth0 Jun 22 19:31:33 Tower rc.inet1: timeout 60 dhcpcd -w -q -t 10 -h Tower -4 eth0 Jun 22 19:31:33 Tower dhcpcd[1600]: eth0: waiting for carrier Jun 22 19:31:33 Tower kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready Jun 22 19:31:33 Tower rsyslogd: [origin software="rsyslogd" swVersion="8.29.0" x-pid="1490" x-info="http://www.rsyslog.com"] start Jun 22 19:31:36 Tower dhcpcd[1600]: eth0: carrier acquired Jun 22 19:31:36 Tower kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None Jun 22 19:31:36 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Jun 22 19:31:37 Tower dhcpcd[1600]: eth0: soliciting a DHCP lease Jun 22 19:31:42 Tower dhcpcd[1600]: eth0: probing for an IPv4LL address Jun 22 19:31:44 Tower dhcpcd[1600]: eth0: offered 192.168.200.174 from 192.168.200.1 Jun 22 19:31:44 Tower dhcpcd[1600]: eth0: probing address 192.168.200.174/24 Jun 22 19:31:47 Tower dhcpcd[1600]: eth0: using IPv4LL address 169.254.112.26 Jun 22 19:31:47 Tower dhcpcd[1600]: eth0: adding route to 169.254.0.0/16 Jun 22 19:31:47 Tower dhcpcd[1600]: eth0: adding default route Jun 22 19:31:47 Tower dhcpcd[1600]: forked to background, child pid 1646 Jun 22 19:31:47 Tower rc.inet1: ip link set eth0 up Jun 22 19:31:47 Tower rc.inet1: ip -4 route add default via 192.168.77.1 metric 1 Jun 22 19:31:47 Tower dhcpcd[1646]: eth0: deleting default route Jun 22 19:31:47 Tower rpc.statd[1674]: Version 2.1.1 starting Jun 22 19:31:47 Tower sm-notify[1675]: Version 2.1.1 starting Jun 22 19:31:47 Tower rpc.statd[1674]: Failed to read /var/lib/nfs/state: Success Jun 22 19:31:47 Tower rpc.statd[1674]: Initializing NSM state Jun 22 19:31:47 Tower sshd[1692]: Server listening on 0.0.0.0 port 22. Jun 22 19:31:47 Tower sshd[1692]: Server listening on :: port 22. Jun 22 19:31:47 Tower ntpd[1702]: ntpd [email protected] Thu Oct 5 18:26:25 UTC 2017 (1): Starting Jun 22 19:31:47 Tower ntpd[1702]: Command line: /usr/sbin/ntpd -g -u ntp:ntp Jun 22 19:31:47 Tower crond[1719]: /usr/sbin/crond 4.5 dillon's cron daemon, started with loglevel notice Jun 22 19:31:47 Tower ntpd[1704]: proto: precision = 0.065 usec (-24) Jun 22 19:31:47 Tower ntpd[1704]: Listen normally on 0 lo 127.0.0.1:123 Jun 22 19:31:47 Tower ntpd[1704]: Listen normally on 1 eth0 169.254.112.26:123 Jun 22 19:31:47 Tower ntpd[1704]: Listen normally on 2 lo [::1]:123 Jun 22 19:31:47 Tower ntpd[1704]: Listening on routing socket on fd #19 for interface updates Jun 22 19:31:47 Tower acpid: starting up with netlink and the input layer Jun 22 19:31:47 Tower acpid: 1 rule loaded Jun 22 19:31:47 Tower acpid: waiting for events: event logging is off Jun 22 19:31:47 Tower root: Installing user plugins Jun 22 19:31:47 Tower root: plugin: installing: /boot/config/plugins/ca.cleanup.appdata.plg Jun 22 19:31:47 Tower root: plugin: running: anonymous Jun 22 19:31:47 Tower root: Jun 22 19:31:47 Tower root: Jun 22 19:31:47 Tower root: Jun 22 19:31:47 Tower root: Jun 22 19:31:47 Tower root: plugin: running: anonymous Jun 22 19:31:47 Tower root: plugin: skipping: /boot/config/plugins/ca.cleanup.appdata/ca.cleanup.appdata-2018.03.15-x86_64-1.txz already exists Jun 22 19:31:47 Tower root: plugin: running: /boot/config/plugins/ca.cleanup.appdata/ca.cleanup.appdata-2018.03.15-x86_64-1.txz Jun 22 19:31:47 Tower root: Jun 22 19:31:47 Tower root: +============================================================================== Jun 22 19:31:47 Tower root: | Installing new package /boot/config/plugins/ca.cleanup.appdata/ca.cleanup.appdata-2018.03.15-x86_64-1.txz Jun 22 19:31:47 Tower root: +============================================================================== Jun 22 19:31:47 Tower root: Jun 22 19:31:47 Tower root: Verifying package ca.cleanup.appdata-2018.03.15-x86_64-1.txz. Jun 22 19:31:47 Tower root: Installing package ca.cleanup.appdata-2018.03.15-x86_64-1.txz: Jun 22 19:31:47 Tower root: PACKAGE DESCRIPTION: Jun 22 19:31:47 Tower root: Package ca.cleanup.appdata-2018.03.15-x86_64-1.txz installed. Jun 22 19:31:47 Tower root: Jun 22 19:31:47 Tower root: Jun 22 19:31:47 Tower root: plugin: running: anonymous Jun 22 19:31:47 Tower root: Jun 22 19:31:47 Tower root: ---------------------------------------------------- Jun 22 19:31:47 Tower root: ca.cleanup.appdata has been installed. Jun 22 19:31:47 Tower root: Copyright 2015-2016, Andrew Zawadzki Jun 22 19:31:47 Tower root: Version: 2018.03.15 Jun 22 19:31:47 Tower root: ---------------------------------------------------- Jun 22 19:31:47 Tower root: Jun 22 19:31:47 Tower root: plugin: installed Jun 22 19:31:47 Tower root: plugin: installing: /boot/config/plugins/community.applications.plg Jun 22 19:31:47 Tower root: plugin: running: anonymous Jun 22 19:31:47 Tower root: Jun 22 19:31:47 Tower root: Jun 22 19:31:47 Tower root: Cleaning Up Old Versions Jun 22 19:31:47 Tower root: Jun 22 19:31:47 Tower root: Jun 22 19:31:47 Tower root: plugin: running: anonymous Jun 22 19:31:47 Tower root: plugin: skipping: /boot/config/plugins/community.applications/community.applications-2018.05.05.txz already exists Jun 22 19:31:47 Tower root: plugin: running: /boot/config/plugins/community.applications/community.applications-2018.05.05.txz Jun 22 19:31:47 Tower root: Jun 22 19:31:47 Tower root: +============================================================================== Jun 22 19:31:47 Tower root: | Installing new package /boot/config/plugins/community.applications/community.applications-2018.05.05.txz Jun 22 19:31:47 Tower root: +============================================================================== Jun 22 19:31:47 Tower root: Jun 22 19:31:47 Tower root: Verifying package community.applications-2018.05.05.txz. Jun 22 19:31:47 Tower root: Installing package community.applications-2018.05.05.txz: Jun 22 19:31:47 Tower root: PACKAGE DESCRIPTION: Jun 22 19:31:47 Tower root: Package community.applications-2018.05.05.txz installed. Jun 22 19:31:47 Tower root: Jun 22 19:31:47 Tower root: Jun 22 19:31:47 Tower root: plugin: running: anonymous Jun 22 19:31:47 Tower root: Creating Directories Jun 22 19:31:47 Tower root: Jun 22 19:31:47 Tower root: ---------------------------------------------------- Jun 22 19:31:47 Tower root: community.applications has been installed. Jun 22 19:31:47 Tower root: Copyright 2015-2018, Andrew Zawadzki Jun 22 19:31:47 Tower root: Version: 2018.05.05 Jun 22 19:31:47 Tower root: ---------------------------------------------------- Jun 22 19:31:47 Tower root: Jun 22 19:31:47 Tower root: plugin: installed Jun 22 19:31:47 Tower root: plugin: installing: /boot/config/plugins/dynamix.local.master.plg Jun 22 19:31:47 Tower root: plugin: running: anonymous Jun 22 19:31:47 Tower root: plugin: skipping: /boot/config/plugins/dynamix.local.master/dynamix.local.master.txz already exists Jun 22 19:31:47 Tower root: plugin: running: /boot/config/plugins/dynamix.local.master/dynamix.local.master.txz Jun 22 19:31:47 Tower root: Jun 22 19:31:47 Tower root: +============================================================================== Jun 22 19:31:47 Tower root: | Installing new package /boot/config/plugins/dynamix.local.master/dynamix.local.master.txz Jun 22 19:31:47 Tower root: +============================================================================== Jun 22 19:31:47 Tower root: Jun 22 19:31:47 Tower root: Verifying package dynamix.local.master.txz. Jun 22 19:31:47 Tower root: Installing package dynamix.local.master.txz: Jun 22 19:31:47 Tower root: PACKAGE DESCRIPTION: Jun 22 19:31:47 Tower root: Package dynamix.local.master.txz installed. Jun 22 19:31:47 Tower root: Jun 22 19:31:47 Tower root: Jun 22 19:31:47 Tower root: plugin: running: anonymous Jun 22 19:31:47 Tower root: Jun 22 19:31:47 Tower root: ----------------------------------------------------------- Jun 22 19:31:47 Tower root: Plugin dynamix.local.master is installed. Jun 22 19:31:47 Tower root: This plugin requires Dynamix webGui to operate Jun 22 19:31:47 Tower root: Copyright 2016, Bergware International Jun 22 19:31:47 Tower root: Version: 2016.09.13a Jun 22 19:31:47 Tower root: ----------------------------------------------------------- Jun 22 19:31:47 Tower root: Jun 22 19:31:47 Tower root: plugin: installed Jun 22 19:31:47 Tower root: plugin: installing: /boot/config/plugins/dynamix.plg Jun 22 19:31:47 Tower root: plugin: installed unRAID version is too high, require at most version 6.1.9 Jun 22 19:31:47 Tower root: plugin: installing: /boot/config/plugins/dynamix.system.temp.plg Jun 22 19:31:47 Tower root: plugin: running: anonymous Jun 22 19:31:47 Tower root: plugin: skipping: /boot/config/plugins/dynamix.system.temp/dynamix.system.temp.txz already exists Jun 22 19:31:47 Tower root: plugin: running: /boot/config/plugins/dynamix.system.temp/dynamix.system.temp.txz Jun 22 19:31:47 Tower root: Jun 22 19:31:47 Tower root: +============================================================================== Jun 22 19:31:47 Tower root: | Installing new package /boot/config/plugins/dynamix.system.temp/dynamix.system.temp.txz Jun 22 19:31:47 Tower root: +============================================================================== Jun 22 19:31:47 Tower root: Jun 22 19:31:47 Tower root: Verifying package dynamix.system.temp.txz. Jun 22 19:31:47 Tower root: Installing package dynamix.system.temp.txz: Jun 22 19:31:47 Tower root: PACKAGE DESCRIPTION: Jun 22 19:31:47 Tower root: Package dynamix.system.temp.txz installed. Jun 22 19:31:47 Tower root: Jun 22 19:31:47 Tower root: Jun 22 19:31:47 Tower root: plugin: skipping: /boot/config/plugins/dynamix.system.temp/sensors-detect already exists Jun 22 19:31:47 Tower root: plugin: creating: /usr/sbin/sensors-detect - copying LOCAL file /boot/config/plugins/dynamix.system.temp/sensors-detect Jun 22 19:31:47 Tower root: plugin: setting: /usr/sbin/sensors-detect - mode to 0755 Jun 22 19:31:47 Tower root: plugin: running: anonymous Jun 22 19:31:47 Tower root: Jun 22 19:31:47 Tower root: ----------------------------------------------------------- Jun 22 19:31:47 Tower root: Plugin dynamix.system.temp is installed. Jun 22 19:31:47 Tower root: This plugin requires Dynamix webGui to operate Jun 22 19:31:47 Tower root: Copyright 2017, Bergware International Jun 22 19:31:47 Tower root: Version: 2018.03.18 Jun 22 19:31:47 Tower root: ----------------------------------------------------------- Jun 22 19:31:47 Tower root: Jun 22 19:31:47 Tower root: plugin: installed Jun 22 19:31:47 Tower root: plugin: installing: /boot/config/plugins/fix.common.problems.plg Jun 22 19:31:47 Tower root: plugin: skipping: /boot/config/plugins/fix.common.problems/fix.common.problems-2018.04.25-x86_64-1.txz already exists Jun 22 19:31:47 Tower root: plugin: running: /boot/config/plugins/fix.common.problems/fix.common.problems-2018.04.25-x86_64-1.txz Jun 22 19:31:47 Tower root: Jun 22 19:31:47 Tower root: +============================================================================== Jun 22 19:31:47 Tower root: | Installing new package /boot/config/plugins/fix.common.problems/fix.common.problems-2018.04.25-x86_64-1.txz Jun 22 19:31:47 Tower root: +============================================================================== Jun 22 19:31:47 Tower root: Jun 22 19:31:47 Tower root: Verifying package fix.common.problems-2018.04.25-x86_64-1.txz. Jun 22 19:31:48 Tower root: Installing package fix.common.problems-2018.04.25-x86_64-1.txz: Jun 22 19:31:48 Tower root: PACKAGE DESCRIPTION: Jun 22 19:31:48 Tower root: Package fix.common.problems-2018.04.25-x86_64-1.txz installed. Jun 22 19:31:48 Tower root: Jun 22 19:31:48 Tower root: Jun 22 19:31:48 Tower root: plugin: running: anonymous Jun 22 19:31:48 Tower root: Jun 22 19:31:48 Tower root: ---------------------------------------------------- Jun 22 19:31:48 Tower root: fix.common.problems has been installed. Jun 22 19:31:48 Tower root: Copyright 2016, Andrew Zawadzki Jun 22 19:31:48 Tower root: Version: 2018.04.25 Jun 22 19:31:48 Tower root: ---------------------------------------------------- Jun 22 19:31:48 Tower root: Jun 22 19:31:48 Tower root: plugin: installed Jun 22 19:31:48 Tower root: plugin: installing: /boot/config/plugins/unassigned.devices.plg Jun 22 19:31:48 Tower root: plugin: running: anonymous Jun 22 19:31:48 Tower root: Jun 22 19:31:48 Tower root: Jun 22 19:31:48 Tower root: Jun 22 19:31:48 Tower root: Jun 22 19:31:48 Tower root: plugin: running: anonymous Jun 22 19:31:48 Tower root: plugin: skipping: /boot/config/plugins/unassigned.devices/packages/unassigned.devices-2018.04.09.tgz already exists Jun 22 19:31:48 Tower root: plugin: skipping: /boot/config/plugins/unassigned.devices/packages/nmap-7.12-x86_64-1.txz already exists Jun 22 19:31:48 Tower root: plugin: running: /boot/config/plugins/unassigned.devices/packages/nmap-7.12-x86_64-1.txz Jun 22 19:31:48 Tower root: Jun 22 19:31:48 Tower root: +============================================================================== Jun 22 19:31:48 Tower root: | Installing new package /boot/config/plugins/unassigned.devices/packages/nmap-7.12-x86_64-1.txz Jun 22 19:31:48 Tower root: +============================================================================== Jun 22 19:31:48 Tower root: Jun 22 19:31:48 Tower root: Verifying package nmap-7.12-x86_64-1.txz. Jun 22 19:31:48 Tower root: Installing package nmap-7.12-x86_64-1.txz: Jun 22 19:31:48 Tower root: PACKAGE DESCRIPTION: Jun 22 19:31:48 Tower root: # nmap (network scanner) Jun 22 19:31:48 Tower root: # Jun 22 19:31:48 Tower root: # Nmap ("Network Mapper") is an open source utility for network Jun 22 19:31:48 Tower root: # exploration or security auditing. It was designed to rapidly scan Jun 22 19:31:48 Tower root: # large networks, although it works fine against single hosts. Nmap Jun 22 19:31:48 Tower root: # uses raw IP packets in novel ways to determine what hosts are Jun 22 19:31:48 Tower root: # available on the network, what services (ports) they are offering, Jun 22 19:31:48 Tower root: # what operating system (and OS version) they are running, what type of Jun 22 19:31:48 Tower root: # packet filters/firewalls are in use, and dozens of other Jun 22 19:31:48 Tower root: # characteristics. Nmap runs on most types of computers, and both Jun 22 19:31:48 Tower root: # console and graphical versions are available. Jun 22 19:31:49 Tower dhcpcd[1646]: eth0: leased 192.168.200.174 for 600 seconds Jun 22 19:31:49 Tower dhcpcd[1646]: eth0: adding route to 192.168.200.0/24 Jun 22 19:31:49 Tower dhcpcd[1646]: eth0: adding default route via 192.168.200.1 Jun 22 19:31:49 Tower dhcpcd[1646]: eth0: deleting route to 169.254.0.0/16 Jun 22 19:31:49 Tower root: Executing install script for nmap-7.12-x86_64-1.txz. Jun 22 19:31:49 Tower root: Package nmap-7.12-x86_64-1.txz installed. Jun 22 19:31:49 Tower root: Jun 22 19:31:49 Tower root: Jun 22 19:31:49 Tower root: plugin: skipping: /boot/config/plugins/unassigned.devices/packages/exfat-utils-1.2.7-x86_64-1_slonly.txz already exists Jun 22 19:31:49 Tower root: plugin: running: /boot/config/plugins/unassigned.devices/packages/exfat-utils-1.2.7-x86_64-1_slonly.txz Jun 22 19:31:49 Tower root: Jun 22 19:31:49 Tower root: +============================================================================== Jun 22 19:31:49 Tower root: | Installing new package /boot/config/plugins/unassigned.devices/packages/exfat-utils-1.2.7-x86_64-1_slonly.txz Jun 22 19:31:49 Tower root: +============================================================================== Jun 22 19:31:49 Tower root: Jun 22 19:31:49 Tower root: Verifying package exfat-utils-1.2.7-x86_64-1_slonly.txz. Jun 22 19:31:49 Tower root: Installing package exfat-utils-1.2.7-x86_64-1_slonly.txz: Jun 22 19:31:49 Tower root: PACKAGE DESCRIPTION: Jun 22 19:31:49 Tower root: # exfat-utils (exFAT system utilities) Jun 22 19:31:49 Tower root: # Jun 22 19:31:49 Tower root: # This project aims to provide a full-featured exFAT file system Jun 22 19:31:49 Tower root: # implementation for GNU/Linux and other Unix-like systems as a FUSE Jun 22 19:31:49 Tower root: # module and a set of utilities. Jun 22 19:31:49 Tower root: # module. Jun 22 19:31:49 Tower root: # Jun 22 19:31:49 Tower root: # This package contains the utilities. Jun 22 19:31:49 Tower root: # Jun 22 19:31:49 Tower root: # Homepage: https://github.com/relan/exfat Jun 22 19:31:49 Tower root: # Jun 22 19:31:49 Tower root: Executing install script for exfat-utils-1.2.7-x86_64-1_slonly.txz. Jun 22 19:31:49 Tower root: Package exfat-utils-1.2.7-x86_64-1_slonly.txz installed. Jun 22 19:31:49 Tower root: Jun 22 19:31:49 Tower root: Jun 22 19:31:49 Tower root: plugin: skipping: /boot/config/plugins/unassigned.devices/packages/fuse-exfat-1.2.7-x86_64-1_slonly.txz already exists Jun 22 19:31:49 Tower root: plugin: running: /boot/config/plugins/unassigned.devices/packages/fuse-exfat-1.2.7-x86_64-1_slonly.txz Jun 22 19:31:49 Tower root: Jun 22 19:31:49 Tower root: +============================================================================== Jun 22 19:31:49 Tower root: | Installing new package /boot/config/plugins/unassigned.devices/packages/fuse-exfat-1.2.7-x86_64-1_slonly.txz Jun 22 19:31:49 Tower root: +============================================================================== Jun 22 19:31:49 Tower root: Jun 22 19:31:49 Tower root: Verifying package fuse-exfat-1.2.7-x86_64-1_slonly.txz. Jun 22 19:31:49 Tower root: Installing package fuse-exfat-1.2.7-x86_64-1_slonly.txz: Jun 22 19:31:49 Tower root: PACKAGE DESCRIPTION: Jun 22 19:31:49 Tower root: # fuse-exfat (exFAT FUSE module) Jun 22 19:31:49 Tower root: # Jun 22 19:31:49 Tower root: # This project aims to provide a full-featured exFAT file system Jun 22 19:31:49 Tower root: # implementation for GNU/Linux and other Unix-like systems as a FUSE Jun 22 19:31:49 Tower root: # module and a set of utilities. Jun 22 19:31:49 Tower root: # module. Jun 22 19:31:49 Tower root: # Jun 22 19:31:49 Tower root: # This package contains the FUSE module. Jun 22 19:31:49 Tower root: # Jun 22 19:31:49 Tower root: # Homepage: https://github.com/relan/exfat Jun 22 19:31:49 Tower root: # Jun 22 19:31:49 Tower root: Executing install script for fuse-exfat-1.2.7-x86_64-1_slonly.txz. Jun 22 19:31:49 Tower root: Package fuse-exfat-1.2.7-x86_64-1_slonly.txz installed. Jun 22 19:31:49 Tower root: Jun 22 19:31:49 Tower root: Jun 22 19:31:49 Tower root: plugin: skipping: /boot/config/plugins/unassigned.devices/packages/hfsprogs-332.25-x86_64-2sl.txz already exists Jun 22 19:31:49 Tower root: plugin: running: /boot/config/plugins/unassigned.devices/packages/hfsprogs-332.25-x86_64-2sl.txz Jun 22 19:31:49 Tower root: Jun 22 19:31:49 Tower root: +============================================================================== Jun 22 19:31:49 Tower root: | Installing new package /boot/config/plugins/unassigned.devices/packages/hfsprogs-332.25-x86_64-2sl.txz Jun 22 19:31:49 Tower root: +============================================================================== Jun 22 19:31:49 Tower root: Jun 22 19:31:49 Tower root: Verifying package hfsprogs-332.25-x86_64-2sl.txz. Jun 22 19:31:49 Tower root: Installing package hfsprogs-332.25-x86_64-2sl.txz: Jun 22 19:31:49 Tower root: PACKAGE DESCRIPTION: Jun 22 19:31:49 Tower root: # hfsprogs - hfs+ user space utils Jun 22 19:31:49 Tower root: # Jun 22 19:31:49 Tower root: # The HFS+ file system used by Apple Computer for their Mac OS is Jun 22 19:31:49 Tower root: # supported by the Linux kernel. Apple provides mkfs and fsck for Jun 22 19:31:49 Tower root: # HFS+ with the Unix core of their operating system, Darwin. Jun 22 19:31:49 Tower root: # Jun 22 19:31:49 Tower root: # This package is a port of Apple's tools for HFS+ filesystems. Jun 22 19:31:49 Tower root: # Jun 22 19:31:49 Tower root: # http://www.opensource.apple.com Jun 22 19:31:49 Tower root: Package hfsprogs-332.25-x86_64-2sl.txz installed. Jun 22 19:31:49 Tower root: Jun 22 19:31:49 Tower root: Jun 22 19:31:49 Tower root: plugin: skipping: /boot/config/plugins/unassigned.devices/packages/libbsd-0.8.6-x86_64-1_slonly.txz already exists Jun 22 19:31:49 Tower root: plugin: running: /boot/config/plugins/unassigned.devices/packages/libbsd-0.8.6-x86_64-1_slonly.txz Jun 22 19:31:49 Tower root: Jun 22 19:31:49 Tower root: +============================================================================== Jun 22 19:31:49 Tower root: | Installing new package /boot/config/plugins/unassigned.devices/packages/libbsd-0.8.6-x86_64-1_slonly.txz Jun 22 19:31:49 Tower root: +============================================================================== Jun 22 19:31:49 Tower root: Jun 22 19:31:49 Tower root: Verifying package libbsd-0.8.6-x86_64-1_slonly.txz. Jun 22 19:31:49 Tower root: Installing package libbsd-0.8.6-x86_64-1_slonly.txz: Jun 22 19:31:49 Tower root: PACKAGE DESCRIPTION: Jun 22 19:31:49 Tower root: # libbsd (library of BSD functions) Jun 22 19:31:49 Tower root: # Jun 22 19:31:49 Tower root: # This library provides useful functions commonly found on BSD systems, Jun 22 19:31:49 Tower root: # and lacking on others like GNU systems, thus making it easier to port Jun 22 19:31:49 Tower root: # projects with strong BSD origins, without needing to embed the same Jun 22 19:31:49 Tower root: # code over and over again on each project. Jun 22 19:31:49 Tower root: # Jun 22 19:31:49 Tower root: # Homepage: http://libbsd.freedesktop.org/wiki/ Jun 22 19:31:49 Tower root: # Jun 22 19:31:49 Tower root: Executing install script for libbsd-0.8.6-x86_64-1_slonly.txz. Jun 22 19:31:49 Tower root: Package libbsd-0.8.6-x86_64-1_slonly.txz installed. Jun 22 19:31:49 Tower root: Jun 22 19:31:49 Tower root: Jun 22 19:31:49 Tower root: plugin: skipping: /boot/config/plugins/unassigned.devices/packages/parted-3.2-x86_64-2.txz already exists Jun 22 19:31:49 Tower root: plugin: running: /boot/config/plugins/unassigned.devices/packages/parted-3.2-x86_64-2.txz Jun 22 19:31:49 Tower root: Jun 22 19:31:49 Tower root: +============================================================================== Jun 22 19:31:49 Tower root: | Installing new package /boot/config/plugins/unassigned.devices/packages/parted-3.2-x86_64-2.txz Jun 22 19:31:49 Tower root: +============================================================================== Jun 22 19:31:49 Tower root: Jun 22 19:31:49 Tower root: Verifying package parted-3.2-x86_64-2.txz. Jun 22 19:31:49 Tower root: Installing package parted-3.2-x86_64-2.txz: Jun 22 19:31:49 Tower root: PACKAGE DESCRIPTION: Jun 22 19:31:49 Tower root: # parted (GNU disk partitioning tool) Jun 22 19:31:49 Tower root: # Jun 22 19:31:49 Tower root: # GNU Parted is a program for creating, destroying, resizing, checking Jun 22 19:31:49 Tower root: # and copying partitions, and the filesystems on them. This is useful Jun 22 19:31:49 Tower root: # for creating space for new operating systems, reorganizing disk Jun 22 19:31:49 Tower root: # usage, copying data between hard disks, and disk imaging. Jun 22 19:31:49 Tower root: # Jun 22 19:31:49 Tower root: Executing install script for parted-3.2-x86_64-2.txz. Jun 22 19:31:49 Tower root: Package parted-3.2-x86_64-2.txz installed. Jun 22 19:31:49 Tower root: Jun 22 19:31:49 Tower root: Jun 22 19:31:49 Tower root: plugin: skipping: /boot/config/plugins/unassigned.devices/packages/libnl-1.1.4-x86_64-1.txz already exists Jun 22 19:31:49 Tower root: plugin: running: /boot/config/plugins/unassigned.devices/packages/libnl-1.1.4-x86_64-1.txz Jun 22 19:31:49 Tower root: Jun 22 19:31:49 Tower root: +============================================================================== Jun 22 19:31:49 Tower root: | Installing new package /boot/config/plugins/unassigned.devices/packages/libnl-1.1.4-x86_64-1.txz Jun 22 19:31:49 Tower root: +============================================================================== Jun 22 19:31:49 Tower root: Jun 22 19:31:49 Tower root: Verifying package libnl-1.1.4-x86_64-1.txz. Jun 22 19:31:49 Tower root: Installing package libnl-1.1.4-x86_64-1.txz: Jun 22 19:31:49 Tower root: PACKAGE DESCRIPTION: Jun 22 19:31:49 Tower root: # libnl (netlink socket library) Jun 22 19:31:49 Tower root: # Jun 22 19:31:49 Tower root: # libnl is a library for applications dealing with netlink sockets. Jun 22 19:31:49 Tower root: # The library provides an interface for raw netlink messaging and Jun 22 19:31:49 Tower root: # various netlink family specific interfaces. Jun 22 19:31:49 Tower root: # Jun 22 19:31:49 Tower root: # Homepage: http://people.suug.ch/~tgr/libnl/ Jun 22 19:31:49 Tower root: # Jun 22 19:31:49 Tower root: # Jun 22 19:31:49 Tower root: Executing install script for libnl-1.1.4-x86_64-1.txz. Jun 22 19:31:49 Tower root: Package libnl-1.1.4-x86_64-1.txz installed. Jun 22 19:31:49 Tower root: Jun 22 19:31:49 Tower root: Jun 22 19:31:49 Tower root: plugin: creating: /tmp/start_unassigned_devices - from INLINE content Jun 22 19:31:49 Tower root: plugin: setting: /tmp/start_unassigned_devices - mode to 0770 Jun 22 19:31:49 Tower root: plugin: skipping: /boot/config/plugins/unassigned.devices/unassigned.devices.cfg already exists Jun 22 19:31:49 Tower root: plugin: skipping: /boot/config/plugins/unassigned.devices/samba_mount.cfg already exists Jun 22 19:31:49 Tower root: plugin: skipping: /boot/config/plugins/unassigned.devices/iso_mount.cfg already exists Jun 22 19:31:49 Tower root: plugin: running: anonymous Jun 22 19:31:49 Tower root: Jun 22 19:31:49 Tower root: ----------------------------------------------------------- Jun 22 19:31:49 Tower root: unassigned.devices has been installed. Jun 22 19:31:49 Tower root: This plugin requires Dynamix webGui to operate Jun 22 19:31:49 Tower root: Copyright 2015, gfjardim Jun 22 19:31:49 Tower root: Copyright 2016-2018, dlandon Jun 22 19:31:49 Tower root: Version: 2018.04.09 Jun 22 19:31:49 Tower root: ----------------------------------------------------------- Jun 22 19:31:49 Tower root: Jun 22 19:31:49 Tower root: plugin: installed Jun 22 19:31:49 Tower root: Starting go script Jun 22 19:31:49 Tower root: Starting emhttpd Jun 22 19:31:49 Tower emhttpd: unRAID System Management Utility version 6.4.1 Jun 22 19:31:49 Tower emhttpd: Copyright (C) 2005-2018, Lime Technology, Inc. Jun 22 19:31:49 Tower emhttpd: shcmd (8): modprobe md-mod super=/boot/config/super.dat Jun 22 19:31:49 Tower kernel: md: unRAID driver 2.9.3 installed Jun 22 19:31:49 Tower emhttpd: Pro key detected, GUID: 0781-5571-0101-200617120100 FILE: /boot/config/Pro.key Jun 22 19:31:49 Tower emhttpd: Device inventory: Jun 22 19:31:49 Tower emhttpd: Hitachi_HDS724040ALE640_PK1310PAG5ZPNJ (sdj) 512 7814037168 Jun 22 19:31:49 Tower emhttpd: Hitachi_HDS5C3020ALA632_ML2220F339LXKE (sdg) 512 3907029168 Jun 22 19:31:49 Tower emhttpd: WDC_WD60EFRX-68MYMN1_WD-WX11D74RH2PJ (sdh) 512 11721045168 Jun 22 19:31:49 Tower emhttpd: Hitachi_HDS5C4040ALE630_PL2321LAG8JNJJ (sdd) 512 7814037168 Jun 22 19:31:49 Tower emhttpd: WDC_WD60EFRX-68MYMN1_WD-WX11D74RH18C (sde) 512 11721045168 Jun 22 19:31:49 Tower emhttpd: HGST_HUS726060ALA640_AR31001EV1B7GC (sdb) 512 11721045168 Jun 22 19:31:49 Tower emhttpd: Hitachi_HDS5C4040ALE630_PL1321LAG9AAVH (sdf) 512 7814037168 Jun 22 19:31:49 Tower emhttpd: Hitachi_HDS724040ALE640_PK2331PAGXGY1T (sdc) 512 7814037168 Jun 22 19:31:49 Tower emhttpd: HGST_HDN726060ALE614_K1KNJ6ND (sdi) 512 11721045168 Jun 22 19:31:49 Tower emhttpd: SanDisk_Cruzer_Fit_4C530101200617120100-0:0 (sda) 512 31266816 Jun 22 19:31:49 Tower kernel: mdcmd (1): import 0 sdh 64 5860522532 0 WDC_WD60EFRX-68MYMN1_WD-WX11D74RH2PJ Jun 22 19:31:49 Tower kernel: md: import disk0: (sdh) WDC_WD60EFRX-68MYMN1_WD-WX11D74RH2PJ size: 5860522532 Jun 22 19:31:50 Tower kernel: mdcmd (2): import 1 sdj 64 3907018532 0 Hitachi_HDS724040ALE640_PK1310PAG5ZPNJ Jun 22 19:31:50 Tower kernel: md: import disk1: (sdj) Hitachi_HDS724040ALE640_PK1310PAG5ZPNJ size: 3907018532 Jun 22 19:31:50 Tower kernel: mdcmd (3): import 2 sdd 64 3907018532 0 Hitachi_HDS5C4040ALE630_PL2321LAG8JNJJ Jun 22 19:31:50 Tower kernel: md: import disk2: (sdd) Hitachi_HDS5C4040ALE630_PL2321LAG8JNJJ size: 3907018532 Jun 22 19:31:50 Tower kernel: mdcmd (4): import 3 sdg 64 1953514552 0 Hitachi_HDS5C3020ALA632_ML2220F339LXKE Jun 22 19:31:50 Tower kernel: md: import disk3: (sdg) Hitachi_HDS5C3020ALA632_ML2220F339LXKE size: 1953514552 Jun 22 19:31:50 Tower kernel: mdcmd (5): import 4 sdi 64 5860522532 0 HGST_HDN726060ALE614_K1KNJ6ND Jun 22 19:31:50 Tower kernel: md: import disk4: (sdi) HGST_HDN726060ALE614_K1KNJ6ND size: 5860522532 Jun 22 19:31:50 Tower kernel: mdcmd (6): import 5 sdf 64 3907018532 0 Hitachi_HDS5C4040ALE630_PL1321LAG9AAVH Jun 22 19:31:50 Tower kernel: md: import disk5: (sdf) Hitachi_HDS5C4040ALE630_PL1321LAG9AAVH size: 3907018532 Jun 22 19:31:50 Tower kernel: mdcmd (7): import 6 sdb 64 5860522532 0 HGST_HUS726060ALA640_AR31001EV1B7GC Jun 22 19:31:50 Tower kernel: md: import disk6: (sdb) HGST_HUS726060ALA640_AR31001EV1B7GC size: 5860522532 Jun 22 19:31:50 Tower kernel: mdcmd (8): import 7 sdc 64 3907018532 0 Hitachi_HDS724040ALE640_PK2331PAGXGY1T Jun 22 19:31:50 Tower kernel: md: import disk7: (sdc) Hitachi_HDS724040ALE640_PK2331PAGXGY1T size: 3907018532 Jun 22 19:31:50 Tower kernel: mdcmd (9): import 8 Jun 22 19:31:50 Tower kernel: mdcmd (10): import 9 Jun 22 19:31:50 Tower kernel: mdcmd (11): import 10 Jun 22 19:31:50 Tower kernel: mdcmd (12): import 11 Jun 22 19:31:50 Tower kernel: mdcmd (13): import 12 Jun 22 19:31:50 Tower kernel: mdcmd (14): import 13 Jun 22 19:31:50 Tower kernel: mdcmd (15): import 14 Jun 22 19:31:50 Tower kernel: mdcmd (16): import 15 Jun 22 19:31:50 Tower kernel: mdcmd (17): import 16 Jun 22 19:31:50 Tower kernel: mdcmd (18): import 17 Jun 22 19:31:50 Tower kernel: mdcmd (19): import 18 Jun 22 19:31:50 Tower kernel: mdcmd (20): import 19 Jun 22 19:31:50 Tower kernel: mdcmd (21): import 20 Jun 22 19:31:50 Tower kernel: mdcmd (22): import 21 Jun 22 19:31:50 Tower kernel: mdcmd (23): import 22 Jun 22 19:31:50 Tower kernel: mdcmd (24): import 23 Jun 22 19:31:50 Tower kernel: mdcmd (25): import 24 Jun 22 19:31:50 Tower kernel: mdcmd (26): import 25 Jun 22 19:31:50 Tower kernel: mdcmd (27): import 26 Jun 22 19:31:50 Tower kernel: mdcmd (28): import 27 Jun 22 19:31:50 Tower kernel: mdcmd (29): import 28 Jun 22 19:31:50 Tower emhttpd: import 30 cache device: no device Jun 22 19:31:50 Tower emhttpd: import flash device: sda Jun 22 19:31:50 Tower kernel: mdcmd (30): import 29 sde 64 5860522532 0 WDC_WD60EFRX-68MYMN1_WD-WX11D74RH18C Jun 22 19:31:50 Tower kernel: md: import disk29: (sde) WDC_WD60EFRX-68MYMN1_WD-WX11D74RH18C size: 5860522532 Jun 22 19:31:50 Tower ntpd[1704]: Listen normally on 3 eth0 192.168.200.174:123 Jun 22 19:31:50 Tower ntpd[1704]: Deleting interface #1 eth0, 169.254.112.26#123, interface stats: received=0, sent=0, dropped=0, active_time=3 secs Jun 22 19:31:50 Tower ntpd[1704]: 193.228.143.13 local addr 169.254.112.26 -> <null> Jun 22 19:31:50 Tower ntpd[1704]: new interface(s) found: waking up resolver Jun 22 19:31:51 Tower emhttpd: Starting services... Jun 22 19:31:51 Tower emhttpd: shcmd (15): /etc/rc.d/rc.nfsd start Jun 22 19:31:51 Tower kernel: RPC: Registered named UNIX socket transport module. Jun 22 19:31:51 Tower kernel: RPC: Registered udp transport module. Jun 22 19:31:51 Tower kernel: RPC: Registered tcp transport module. Jun 22 19:31:51 Tower kernel: RPC: Registered tcp NFSv4.1 backchannel transport module. Jun 22 19:31:51 Tower kernel: Installing knfsd (copyright (C) 1996 [email protected]). Jun 22 19:31:51 Tower root: Starting NFS server daemons: Jun 22 19:31:51 Tower root: /usr/sbin/exportfs -r Jun 22 19:31:51 Tower root: /usr/sbin/rpc.nfsd 8 Jun 22 19:31:51 Tower root: /usr/sbin/rpc.mountd Jun 22 19:31:51 Tower rpc.mountd[3392]: Version 2.1.1 starting Jun 22 19:31:51 Tower emhttpd: shcmd (18): /etc/rc.d/rc.avahidaemon start Jun 22 19:31:51 Tower root: Starting Avahi mDNS/DNS-SD Daemon: /usr/sbin/avahi-daemon -D Jun 22 19:31:51 Tower avahi-daemon[3407]: Found user 'avahi' (UID 61) and group 'avahi' (GID 214). Jun 22 19:31:51 Tower avahi-daemon[3407]: Successfully dropped root privileges. Jun 22 19:31:51 Tower avahi-daemon[3407]: avahi-daemon 0.7 starting up. Jun 22 19:31:51 Tower avahi-daemon[3407]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns! Jun 22 19:31:51 Tower avahi-daemon[3407]: Successfully called chroot(). Jun 22 19:31:51 Tower avahi-daemon[3407]: Successfully dropped remaining capabilities. Jun 22 19:31:51 Tower avahi-daemon[3407]: Loading service file /services/sftp-ssh.service. Jun 22 19:31:51 Tower avahi-daemon[3407]: Loading service file /services/smb.service. Jun 22 19:31:51 Tower avahi-daemon[3407]: Loading service file /services/ssh.service. Jun 22 19:31:51 Tower avahi-daemon[3407]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::4216:7eff:fe25:ddb9. Jun 22 19:31:51 Tower avahi-daemon[3407]: New relevant interface eth0.IPv6 for mDNS. Jun 22 19:31:51 Tower avahi-daemon[3407]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.200.174. Jun 22 19:31:51 Tower avahi-daemon[3407]: New relevant interface eth0.IPv4 for mDNS. Jun 22 19:31:51 Tower avahi-daemon[3407]: Network interface enumeration completed. Jun 22 19:31:51 Tower avahi-daemon[3407]: Registering new address record for fe80::4216:7eff:fe25:ddb9 on eth0.*. Jun 22 19:31:51 Tower avahi-daemon[3407]: Registering new address record for 192.168.200.174 on eth0.IPv4. Jun 22 19:31:51 Tower emhttpd: shcmd (19): /etc/rc.d/rc.avahidnsconfd start Jun 22 19:31:51 Tower root: Starting Avahi mDNS/DNS-SD DNS Server Configuration Daemon: /usr/sbin/avahi-dnsconfd -D Jun 22 19:31:51 Tower avahi-dnsconfd[3417]: Successfully connected to Avahi daemon. Jun 22 19:31:51 Tower emhttpd: shcmd (24): /etc/rc.d/rc.php-fpm start Jun 22 19:31:51 Tower root: Starting php-fpm done Jun 22 19:31:51 Tower emhttpd: shcmd (25): /etc/rc.d/rc.nginx start Jun 22 19:31:51 Tower root: Starting Nginx server daemon... Jun 22 19:31:51 Tower emhttpd: shcmd (26): /usr/local/sbin/set_ncq sdh 1 Jun 22 19:31:51 Tower kernel: mdcmd (31): set md_num_stripes 1280 Jun 22 19:31:51 Tower kernel: mdcmd (32): set md_sync_window 384 Jun 22 19:31:51 Tower kernel: mdcmd (33): set md_sync_thresh 192 Jun 22 19:31:51 Tower kernel: mdcmd (34): set md_write_method Jun 22 19:31:51 Tower kernel: mdcmd (35): set spinup_group 0 0 Jun 22 19:31:51 Tower kernel: mdcmd (36): set spinup_group 1 0 Jun 22 19:31:51 Tower kernel: mdcmd (37): set spinup_group 2 0 Jun 22 19:31:51 Tower kernel: mdcmd (38): set spinup_group 3 0 Jun 22 19:31:51 Tower kernel: mdcmd (39): set spinup_group 4 0 Jun 22 19:31:51 Tower kernel: mdcmd (40): set spinup_group 5 0 Jun 22 19:31:51 Tower kernel: mdcmd (41): set spinup_group 6 0 Jun 22 19:31:51 Tower kernel: mdcmd (42): set spinup_group 7 0 Jun 22 19:31:51 Tower kernel: mdcmd (43): set spinup_group 29 0 Jun 22 19:31:51 Tower root: set_ncq: setting sdh queue_depth to 1 Jun 22 19:31:51 Tower emhttpd: shcmd (27): echo 128 > /sys/block/sdh/queue/nr_requests Jun 22 19:31:51 Tower emhttpd: shcmd (28): /usr/local/sbin/set_ncq sdj 1 Jun 22 19:31:51 Tower root: set_ncq: setting sdj queue_depth to 1 Jun 22 19:31:51 Tower emhttpd: shcmd (29): echo 128 > /sys/block/sdj/queue/nr_requests Jun 22 19:31:51 Tower emhttpd: shcmd (30): /usr/local/sbin/set_ncq sdd 1 Jun 22 19:31:51 Tower root: set_ncq: setting sdd queue_depth to 1 Jun 22 19:31:51 Tower emhttpd: shcmd (31): echo 128 > /sys/block/sdd/queue/nr_requests Jun 22 19:31:51 Tower emhttpd: shcmd (32): /usr/local/sbin/set_ncq sdg 1 Jun 22 19:31:51 Tower root: set_ncq: setting sdg queue_depth to 1 Jun 22 19:31:51 Tower emhttpd: shcmd (33): echo 128 > /sys/block/sdg/queue/nr_requests Jun 22 19:31:51 Tower emhttpd: shcmd (34): /usr/local/sbin/set_ncq sdi 1 Jun 22 19:31:51 Tower root: set_ncq: setting sdi queue_depth to 1 Jun 22 19:31:51 Tower emhttpd: shcmd (35): echo 128 > /sys/block/sdi/queue/nr_requests Jun 22 19:31:51 Tower emhttpd: shcmd (36): /usr/local/sbin/set_ncq sdf 1 Jun 22 19:31:51 Tower root: set_ncq: setting sdf queue_depth to 1 Jun 22 19:31:51 Tower emhttpd: shcmd (37): echo 128 > /sys/block/sdf/queue/nr_requests Jun 22 19:31:51 Tower emhttpd: shcmd (38): /usr/local/sbin/set_ncq sdb 1 Jun 22 19:31:51 Tower root: set_ncq: setting sdb queue_depth to 1 Jun 22 19:31:51 Tower emhttpd: shcmd (39): echo 128 > /sys/block/sdb/queue/nr_requests Jun 22 19:31:51 Tower emhttpd: shcmd (40): /usr/local/sbin/set_ncq sdc 1 Jun 22 19:31:51 Tower root: set_ncq: setting sdc queue_depth to 1 Jun 22 19:31:51 Tower emhttpd: shcmd (41): echo 128 > /sys/block/sdc/queue/nr_requests Jun 22 19:31:51 Tower emhttpd: shcmd (42): /usr/local/sbin/set_ncq sde 1 Jun 22 19:31:51 Tower root: set_ncq: setting sde queue_depth to 1 Jun 22 19:31:51 Tower emhttpd: shcmd (43): echo 128 > /sys/block/sde/queue/nr_requests Jun 22 19:31:51 Tower kernel: mdcmd (44): start STOPPED Jun 22 19:31:51 Tower kernel: unraid: allocating 46460K for 1280 stripes (9 disks) Jun 22 19:31:51 Tower kernel: md1: running, size: 3907018532 blocks Jun 22 19:31:51 Tower kernel: md2: running, size: 3907018532 blocks Jun 22 19:31:51 Tower kernel: md3: running, size: 1953514552 blocks Jun 22 19:31:51 Tower kernel: md4: running, size: 5860522532 blocks Jun 22 19:31:51 Tower kernel: md5: running, size: 3907018532 blocks Jun 22 19:31:51 Tower kernel: md6: running, size: 5860522532 blocks Jun 22 19:31:51 Tower kernel: md7: running, size: 3907018532 blocks Jun 22 19:31:51 Tower emhttpd: shcmd (44): udevadm settle Jun 22 19:31:51 Tower emhttpd: Autostart enabled Jun 22 19:31:51 Tower root: Starting /usr/local/emhttp/webGui/scripts/diskload Jun 22 19:31:51 Tower emhttpd: Mounting disks... Jun 22 19:31:51 Tower emhttpd: shcmd (52): /sbin/btrfs device scan Jun 22 19:31:52 Tower avahi-daemon[3407]: Server startup complete. Host name is Tower.local. Local service cookie is 163112546. Jun 22 19:31:52 Tower root: Scanning for Btrfs filesystems Jun 22 19:31:52 Tower emhttpd: shcmd (53): mkdir -p /mnt/disk1 Jun 22 19:31:52 Tower emhttpd: shcmd (54): mount -t reiserfs -o noatime,nodiratime /dev/md1 /mnt/disk1 Jun 22 19:31:52 Tower kernel: REISERFS (device md1): found reiserfs format "3.6" with standard journal Jun 22 19:31:52 Tower kernel: REISERFS (device md1): using ordered data mode Jun 22 19:31:52 Tower kernel: reiserfs: using flush barriers Jun 22 19:31:52 Tower kernel: REISERFS (device md1): journal params: device md1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Jun 22 19:31:52 Tower kernel: REISERFS (device md1): checking transaction log (md1) Jun 22 19:31:52 Tower root: error: /webGui/include/ProcessStatus.php: wrong csrf_token Jun 22 19:31:52 Tower kernel: REISERFS (device md1): Using r5 hash to sort names Jun 22 19:31:52 Tower emhttpd: shcmd (55): mount -t reiserfs -o remount,user_xattr,acl,noatime,nodiratime /dev/md1 /mnt/disk1 Jun 22 19:31:52 Tower emhttpd: reiserfs: resizing /mnt/disk1 Jun 22 19:31:52 Tower emhttpd: shcmd (56): mkdir -p /mnt/disk2 Jun 22 19:31:52 Tower emhttpd: shcmd (57): mount -t reiserfs -o noatime,nodiratime /dev/md2 /mnt/disk2 Jun 22 19:31:52 Tower kernel: REISERFS (device md2): found reiserfs format "3.6" with standard journal Jun 22 19:31:52 Tower kernel: REISERFS (device md2): using ordered data mode Jun 22 19:31:52 Tower kernel: reiserfs: using flush barriers Jun 22 19:31:52 Tower kernel: REISERFS (device md2): journal params: device md2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Jun 22 19:31:52 Tower kernel: REISERFS (device md2): checking transaction log (md2) Jun 22 19:31:52 Tower kernel: REISERFS (device md2): Using r5 hash to sort names Jun 22 19:31:52 Tower emhttpd: shcmd (58): mount -t reiserfs -o remount,user_xattr,acl,noatime,nodiratime /dev/md2 /mnt/disk2 Jun 22 19:31:52 Tower emhttpd: reiserfs: resizing /mnt/disk2 Jun 22 19:31:52 Tower emhttpd: shcmd (59): mkdir -p /mnt/disk3 Jun 22 19:31:52 Tower emhttpd: shcmd (60): mount -t reiserfs -o noatime,nodiratime /dev/md3 /mnt/disk3 Jun 22 19:31:52 Tower kernel: REISERFS (device md3): found reiserfs format "3.6" with standard journal Jun 22 19:31:52 Tower kernel: REISERFS (device md3): using ordered data mode Jun 22 19:31:52 Tower kernel: reiserfs: using flush barriers Jun 22 19:31:53 Tower kernel: REISERFS (device md3): journal params: device md3, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Jun 22 19:31:53 Tower kernel: REISERFS (device md3): checking transaction log (md3) Jun 22 19:31:53 Tower avahi-daemon[3407]: Service "Tower" (/services/ssh.service) successfully established. Jun 22 19:31:53 Tower avahi-daemon[3407]: Service "Tower" (/services/smb.service) successfully established. Jun 22 19:31:53 Tower avahi-daemon[3407]: Service "Tower" (/services/sftp-ssh.service) successfully established. Jun 22 19:31:53 Tower kernel: REISERFS (device md3): Using r5 hash to sort names Jun 22 19:31:53 Tower emhttpd: shcmd (61): mount -t reiserfs -o remount,user_xattr,acl,noatime,nodiratime /dev/md3 /mnt/disk3 Jun 22 19:31:53 Tower emhttpd: reiserfs: resizing /mnt/disk3 Jun 22 19:31:53 Tower emhttpd: shcmd (62): mkdir -p /mnt/disk4 Jun 22 19:31:53 Tower emhttpd: shcmd (63): mount -t reiserfs -o noatime,nodiratime /dev/md4 /mnt/disk4 Jun 22 19:31:53 Tower kernel: REISERFS (device md4): found reiserfs format "3.6" with standard journal Jun 22 19:31:53 Tower kernel: REISERFS (device md4): using ordered data mode Jun 22 19:31:53 Tower kernel: reiserfs: using flush barriers Jun 22 19:31:53 Tower kernel: REISERFS (device md4): journal params: device md4, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Jun 22 19:31:53 Tower kernel: REISERFS (device md4): checking transaction log (md4) Jun 22 19:31:53 Tower kernel: REISERFS (device md4): Using r5 hash to sort names Jun 22 19:31:53 Tower emhttpd: shcmd (64): mount -t reiserfs -o remount,user_xattr,acl,noatime,nodiratime /dev/md4 /mnt/disk4 Jun 22 19:31:53 Tower emhttpd: reiserfs: resizing /mnt/disk4 Jun 22 19:31:53 Tower emhttpd: shcmd (65): mkdir -p /mnt/disk5 Jun 22 19:31:53 Tower emhttpd: shcmd (66): mount -t reiserfs -o noatime,nodiratime /dev/md5 /mnt/disk5 Jun 22 19:31:53 Tower kernel: REISERFS (device md5): found reiserfs format "3.6" with standard journal Jun 22 19:31:53 Tower kernel: REISERFS (device md5): using ordered data mode Jun 22 19:31:53 Tower kernel: reiserfs: using flush barriers Jun 22 19:31:53 Tower kernel: REISERFS (device md5): journal params: device md5, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Jun 22 19:31:53 Tower kernel: REISERFS (device md5): checking transaction log (md5) Jun 22 19:31:53 Tower kernel: REISERFS (device md5): Using r5 hash to sort names Jun 22 19:31:53 Tower emhttpd: shcmd (67): mount -t reiserfs -o remount,user_xattr,acl,noatime,nodiratime /dev/md5 /mnt/disk5 Jun 22 19:31:53 Tower emhttpd: reiserfs: resizing /mnt/disk5 Jun 22 19:31:54 Tower emhttpd: shcmd (68): mkdir -p /mnt/disk6 Jun 22 19:31:54 Tower emhttpd: /mnt/disk6 mount error: Unsupported partition layout Jun 22 19:31:54 Tower emhttpd: shcmd (69): umount /mnt/disk6 Jun 22 19:31:54 Tower root: umount: /mnt/disk6: not mounted. Jun 22 19:31:54 Tower emhttpd: shcmd (69): exit status: 32 Jun 22 19:31:54 Tower emhttpd: shcmd (70): rmdir /mnt/disk6 Jun 22 19:31:54 Tower emhttpd: shcmd (71): mkdir -p /mnt/disk7 Jun 22 19:31:54 Tower emhttpd: /mnt/disk7 mount error: Unsupported partition layout Jun 22 19:31:54 Tower emhttpd: shcmd (72): umount /mnt/disk7 Jun 22 19:31:54 Tower root: umount: /mnt/disk7: not mounted. Jun 22 19:31:54 Tower emhttpd: shcmd (72): exit status: 32 Jun 22 19:31:54 Tower emhttpd: shcmd (73): rmdir /mnt/disk7 Jun 22 19:31:54 Tower emhttpd: shcmd (74): sync Jun 22 19:31:54 Tower emhttpd: shcmd (75): mkdir /mnt/user Jun 22 19:31:54 Tower emhttpd: shcmd (76): /usr/local/sbin/shfs /mnt/user -disks 254 -o noatime,big_writes,allow_other -o remember=330 |& logger Jun 22 19:31:54 Tower emhttpd: shcmd (78): /usr/local/sbin/update_cron Jun 22 19:31:54 Tower root: Delaying execution of fix common problems scan for 10 minutes Jun 22 19:31:54 Tower unassigned.devices: Mounting 'Auto Mount' Devices... Jun 22 19:31:54 Tower emhttpd: Starting services... Jun 22 19:31:54 Tower emhttpd: shcmd (109): /usr/local/sbin/mount_image '/mnt/user/Docker/docker.img' /var/lib/docker 10 Jun 22 19:31:55 Tower kernel: BTRFS: device fsid 43548896-9618-4446-a6a9-6ddd8de70913 devid 1 transid 41111 /dev/loop2 Jun 22 19:31:55 Tower kernel: BTRFS info (device loop2): disk space caching is enabled Jun 22 19:31:55 Tower kernel: BTRFS info (device loop2): has skinny extents Jun 22 19:31:55 Tower root: Resize '/var/lib/docker' of 'max' Jun 22 19:31:55 Tower kernel: BTRFS info (device loop2): new size for /dev/loop2 is 10737418240 Jun 22 19:31:55 Tower emhttpd: shcmd (111): /etc/rc.d/rc.docker start Jun 22 19:31:55 Tower root: starting dockerd ... Jun 22 19:31:57 Tower kernel: ip_tables: (C) 2000-2006 Netfilter Core Team Jun 22 19:31:58 Tower avahi-daemon[3407]: Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1. Jun 22 19:31:58 Tower avahi-daemon[3407]: New relevant interface docker0.IPv4 for mDNS. Jun 22 19:31:58 Tower avahi-daemon[3407]: Registering new address record for 172.17.0.1 on docker0.IPv4. Jun 22 19:31:58 Tower kernel: IPv6: ADDRCONF(NETDEV_UP): docker0: link is not ready Jun 22 19:32:00 Tower root: plex: started succesfully! Jun 22 19:32:00 Tower emhttpd: nothing to sync Jun 22 19:41:00 Tower root: Fix Common Problems Version 2018.04.25 Jun 22 19:41:11 Tower root: Fix Common Problems: Warning: Docker Application MKVToolNix has an update available for it Jun 22 19:41:11 Tower root: Fix Common Problems: Warning: Docker Application plex has an update available for it Jun 22 20:11:56 Tower emhttpd: req (1): startState=STARTED&file=&unmountable_mask=192&cmdCheck=Check&optionCorrect=correct&csrf_token=**************** Jun 22 20:11:56 Tower kernel: mdcmd (45): check correct Jun 22 20:11:56 Tower kernel: md: recovery thread: check P Q ... Jun 22 20:11:56 Tower kernel: md: using 1536k window, over a total of 5860522532 blocks. Jun 22 20:11:56 Tower kernel: md: recovery thread: PQ corrected, sector=128 Jun 22 20:11:57 Tower kernel: md: recovery thread: Q corrected, sector=65688 Jun 22 20:11:57 Tower kernel: md: recovery thread: Q corrected, sector=263384 Jun 22 20:12:38 Tower kernel: md: recovery thread: PQ corrected, sector=10987336 Jun 23 00:24:20 Tower kernel: md: recovery thread: PQ corrected, sector=2389180464 Jun 23 03:40:01 Tower root: mover: cache not present, or only cache present Jun 23 04:07:29 Tower kernel: mdcmd (46): spindown 3 Jun 23 04:18:49 Tower kernel: md: recovery thread: PQ corrected, sector=4811915336 Jun 23 04:18:49 Tower kernel: md: recovery thread: PQ corrected, sector=4811915352 Jun 23 05:50:25 Tower kernel: md: recovery thread: PQ corrected, sector=5878055056 Jun 23 06:45:16 Tower kernel: md: recovery thread: PQ corrected, sector=6460538896 Jun 23 10:16:04 Tower kernel: mdcmd (47): spindown 5 Jun 23 10:20:27 Tower emhttpd: req (2): cmd=/webGui/scripts/disk_log&arg1=sdb&csrf_token=**************** Jun 23 10:20:27 Tower emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/disk_log sdb Jun 23 10:21:05 Tower emhttpd: req (3): cmdSpinup=disk5&csrf_token=**************** Jun 23 10:21:05 Tower kernel: mdcmd (48): spinup 5 Jun 23 10:34:17 Tower sshd[32226]: Accepted none for root from 192.168.200.222 port 55170 ssh2 Jun 23 11:06:54 Tower sshd[3192]: Accepted none for root from 192.168.200.222 port 56300 ssh2 Jun 23 11:16:04 Tower kernel: mdcmd (49): spindown 1 Jun 23 11:16:05 Tower kernel: mdcmd (50): spindown 7 Jun 23 11:21:06 Tower kernel: mdcmd (51): spindown 5 Jun 23 11:23:22 Tower sshd[5071]: Accepted none for root from 192.168.200.222 port 56411 ssh2 Jun 23 13:13:49 Tower kernel: mdcmd (52): spindown 5 Jun 23 14:37:24 Tower kernel: md: sync done. time=66327sec Jun 23 14:37:24 Tower kernel: md: recovery thread: completion status: 0 I will wait until i am given further instructions. Quote Link to comment
SSD Posted June 23, 2018 Share Posted June 23, 2018 @Ron - Parity is computed on the PARTITION not the ENTIRE DISK. So if one disk starts are section 2048 and another starts on sector 64, the first parity block of the first disk would begin at physical sector 2048 and the first sector of the other would start at physical sector 64. So if a disks partition were updated to start at a difference sector, you'd think parity would be out of sync virtually everywhere. We are only seeing 9 parity errors, very consistent with why you'd see after a hard shutdown. This is good news IMO for your ability to recover your data. The most important question that comes out of this is how unRAID is treating the odd paritioning of disk6 and disk7. Is it assuming that the disk partition is 63 or 64 based on the disk size, and sort of ignoring the partition table values? Or is it assuming the disk partition is accurate and hence the first parity block for disk6 is at the 2k point? (And it must have been that way from the time they were added to the array.). Hoping that Tom ( @limetech ) will weigh in here. My hypothesis is if we can correct the partition tables for disks 6 and 7, your data will be valid. The question is, what is correct? See below for my interpretation of the parity check log entries. Jun 22 20:11:56 Tower kernel: mdcmd (45): check correct - This is a correcting check - so parity is updated for every parity mismatch found Jun 22 20:11:56 Tower kernel: md: recovery thread: check P Q ... - Dual parity (P and Q) Jun 22 20:11:56 Tower kernel: md: using 1536k window, over a total of 5860522532 blocks. Jun 22 20:11:56 Tower kernel: md: recovery thread: PQ corrected, sector=128 - First parity corruption. Sector listed is always the first of 8 sectors (4k bytes). So we don't know if they were off in only a single sector, or if they were off in all 8 of the sectors between 128-135. - What is interesting is that sectors 0-127 had no corruption. And there are only 9 sectors reported corrected. If the starting sector of disk6 should have been 64 (which is what unRAID would have done), and the parity check was instead starting at 2048 due to the partition table, you'd have to believe that this would impact virtually every sector on the disk. Does this mean that the parity check was assigning a starting sector of 64? Or does this mean that the disk has consistently been treating the first sector of the partition starting at sector 2048. (@limetech) Jun 22 20:11:57 Tower kernel: md: recovery thread: Q corrected, sector=65688 - Over 64k of accurate parity blocks before this. Notice that only Q parity is corrected, P parity is accurate. I'd say this would be expected type of corruption for a hard shutdown. Jun 22 20:11:57 Tower kernel: md: recovery thread: Q corrected, sector=263384 - Look at the timestamps. This one is very close to the prior one. Again, this is typical of corruption from hard shutdown. Again affecting only Q parity. It is logical that P parity is updated first and Q parity second. So appears a hard shutdown happened between those 2 I/Os. Jun 22 20:12:38 Tower kernel: md: recovery thread: PQ corrected, sector=10987336 - This one is 41 seconds later - typical correction from hard shutdown Jun 23 00:24:20 Tower kernel: md: recovery thread: PQ corrected, sector=2389180464 - This one is 12 minutes later. Still typical from hard shutdown. Jun 23 04:18:49 Tower kernel: md: recovery thread: PQ corrected, sector=4811915336 - This one is almost 4 hours later. Again, a lot of parity is accurate. Typical. Jun 23 04:18:49 Tower kernel: md: recovery thread: PQ corrected, sector=4811915352 - Very close to last one. Probably I/O on the same file. Typical. Jun 23 05:50:25 Tower kernel: md: recovery thread: PQ corrected, sector=5878055056 - Over 1.5 hours later. Typical. Jun 23 06:45:16 Tower kernel: md: recovery thread: PQ corrected, sector=6460538896 - 1 hour later. Typcial. Jun 23 14:37:24 Tower kernel: md: sync done. time=66327sec - Parity check done. Just under 7 hours from last Parity correction. A lot of valid parity. Jun 23 14:37:24 Tower kernel: md: recovery thread: completion status: 0 - Parity check finished successfully Note there is a max number of parity errors that unRAID will log. It has varied by unRAID version, but think it is in the hundreds. There were only 9 found, so expect all were logged. These few parity errors are very consistent with corruption from a hard shutdown. And updating parity is almost always the right thing to do, meaning all of the parity is likely corrected appropriately. This is not what I'd expect with misaligned partitions. If we can correct the partition tables for disks 6 and 7, I believe the disks will mount and your data will be valid. The question is, what is correct? Tom, or one of our other very technical users, may be able to advise. 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.