search for: sdi2

...001 0000 88af e8e0 0000 00001d0 0000 0000 0000 0000 0000 0000 0000 0000 * 00001f0 0000 0000 0000 0000 0000 0000 0000 aa55 0000200 So far, so normal. This works fine under 2.6.32-220.23.1.el6.x86_64 Personalities : [raid1] [raid10] [raid6] [raid5] [raid4] md127 : active raid5 sdj3[2] sdi2[1] sdk4[3] sdh1[0] 5860537344 blocks level 5, 64k chunk, algorithm 2 [4/4] [UUUU] However, I just patched to CentOS 6.3 and on reboot this array failed to be built. The 2.6.32-279 kernel complained that /dev/sdj was too similar to /dev/sdj3. But I reboot to -220.23.1 then it works. And,...

...8:80 0 2.7T 0 disk └─luks-sdf 254:5 0 2.7T 0 crypt sdg 8:96 0 2.7T 0 disk └─luks-sdg 254:6 0 2.7T 0 crypt sdh 8:112 0 2.7T 0 disk └─luks-sdh 254:7 0 2.7T 0 crypt sdi 8:128 1 119.2G 0 disk ├─sdi1 8:129 1 512M 0 part /boot/efi └─sdi2 8:130 1 118G 0 part / root at punishedkorppu /# zpool status pool: tank state: ONLINE scan: scrub repaired 0B in 18h41m with 0 errors on Mon Dec 25 17:18:44 2017 config: NAME STATE READ WRITE CKSUM tank ONLINE 0 0 0 raid...

I just noticed that by running by commands /usr/sbin/smbd -D or /usr/sbin/smbd -i without systemd's unit, all shares work perfectly so the problem must then be somehow related to systemd.. Let the testing continue.. I also tested what happens if I comment out everything and just use ExecStart=/usr/sbin/smbd -D as that command worked on the console. That did not help. For the record, this is

Hi, The error line is: *** STOP: 0x0000007B (0xF789AA94, 0xC0000034, 0x00000000, 0x00000000) Nothing more! (Of course there are some inrelevant text line about chkdsk, etc.) > Basically, what's required is the "STOP:" line + the image where it > fails (so, the line below). Image being likely to be NTOSKRNL.EXE > Nothing about NTOSKRNL.EXE on the blue screen! > >