Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
chambal <2iow-li6l at dea.spamcon.org> wrote: >chambal <2iow-li6l at dea.spamcon.org> wrote: > >>"J. Ryan Earl" <oss at jryanearl.us> wrote: >> >>>On Sun, Nov 7, 2010 at 1:04 AM, chambal <2iow-li6l at dea.spamcon.org> wrote: >>> >>>> >> Then at the "drbadadm attach r0" step, it crashed. Nothing >>>> >>>[...] >>> >>>> >> showed in the syslog or watch windows (it crashed instantly). >>>> >> After reboot, nothing in syslog after the above lines, until the >>>> >> new boot messages.It's a plain system, nothing special using the disk - >>>> it's an SSD >>>> with some partitions, there's no raid or anything, this 1GB >>>> /dev/sda2 partition is created and formatted by the OS installer >>>> but then I remove it from fstab and it's only used for drbd. >>> >>> >>>Have you zeroed out this this partition before running 'drbdadm create-md'? >> >>Yes, or at least the first part, via: >> >>dd if=/dev/zero bs=1M count=1 of=/dev/sda2 > >Follow-up: zeroing the entire partition made no difference. > >The problem is definitely the VIA EPIA M800 platform. No other non-VIA >Mini-ITX platform tried has these problems with the same SSD drives and >software. Follow-up on this thread: it turns out that on the VIA M800, problems like this occur if you use the SATA1 connector - but go away if you instead use the SATA2 connector. An accidental discovery that is rather puzzling. In fact, the same thing is true on the VIA M850 (which uses the VX900 chipset instead of VX800). Just move the SSD drive to the other SATA connector and this problem goes away.