Search Results

Search found 5 results on 1 pages for 'anteru'.

Page 1/1 | 1 

  • mdadm starts resync on every boot

    - by Anteru
    Since a few days (and I'm positive it started shortly before I updated my server from 13.04-13.10) my mdadm is resyncing on every boot. In the syslog, I get the following output [ 0.809256] md: linear personality registered for level -1 [ 0.811412] md: multipath personality registered for level -4 [ 0.813153] md: raid0 personality registered for level 0 [ 0.815201] md: raid1 personality registered for level 1 [ 1.101517] md: raid6 personality registered for level 6 [ 1.101520] md: raid5 personality registered for level 5 [ 1.101522] md: raid4 personality registered for level 4 [ 1.106825] md: raid10 personality registered for level 10 [ 1.935882] md: bind<sdc1> [ 1.943367] md: bind<sdb1> [ 1.945199] md/raid1:md0: not clean -- starting background reconstruction [ 1.945204] md/raid1:md0: active with 2 out of 2 mirrors [ 1.945225] md0: detected capacity change from 0 to 2000396680192 [ 1.945351] md: resync of RAID array md0 [ 1.945357] md: minimum _guaranteed_ speed: 1000 KB/sec/disk. [ 1.945359] md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for resync. [ 1.945362] md: using 128k window, over a total of 1953512383k. [ 2.220468] md0: unknown partition table I'm not sure what's up with that detected capacity change, looking at some old logs, this does have appeared earlier as well without a resync right afterwards. In fact, I let it run yesterday until completion and rebooted, and then it wouldn't resync, but today it does resync again. For instance, yesterday I got: [ 1.872123] md: bind<sdc1> [ 1.950946] md: bind<sdb1> [ 1.952782] md/raid1:md0: active with 2 out of 2 mirrors [ 1.952807] md0: detected capacity change from 0 to 2000396680192 [ 1.954598] md0: unknown partition table So it seems to be a problem that the RAID array does not get marked as clean after every shutdown? How can I troubleshoot this? The disks themselves are both fine, SMART tells me no errors, everything ok.

    Read the article

  • Can't set Windows XP background

    - by Anteru
    I have a Windows XP (Home) machine with a very weird problem. I cannot set the background image properly. That is, I can go to Desktop, Background image, select a different one, but the background has still the same solid colour. Now if I kill explorer.exe, I can see the background image correctly, but starting explorer.exe gives me the solid colour background back again. If I go to Desktop, Customise Desktop, Web, there is a checkbox at the bottom called "Fix desktop icons" or something like this (not sure how it's called in the English version.) If I enable this checkbox, I can see the background, but the desktop icons are drawn with solid-colour backgrounds (even though I have the "draw icon labels transparently" option set.) If I disable the checkbox, I have no desktop background. Active Desktop is disabled. Any idea how to fix this and what might be the reason for this behaviour in the first place?

    Read the article

  • Preparing a hyper-v VM image

    - by Anteru
    We have a Hyper-V Windows Server 2k3, and we're hosting multiple VMs on it. However, right now, we always start the VM creation right on the server, i.e. when preparing a new Ubuntu image, I just install it into a new VM and set it up and when I'm happy we store the disk image. I wonder if there is a way to prepare a hyper-v image locally on my desktop machine instead? I'm running Windows 7, and I would love to be able to set up a VM so that we can copy the image over to the server and be done with it. This is for linux images only, and we definitely need the hyperv network integration. Is there a recommended way how to prepare hyperv images without running a hyperv instance somewhere?

    Read the article

  • insertRecord into QSqlTableModel fails, but item appears in QListView

    - by Anteru
    I got a pretty weird problem with a QSqlTableModel. The underlying SQL Database has a constraint Title UNIQUE. If I add a record which violates the constraint using insertRecord, the call fails (return value is false.) However, the view which uses the model displays the entry -- I have to manually remove it in order to get rid of it. How can I change this so the view does not get updated when an insertRecord fails? I would have assumed that the view gets only updated if there is really a change ...

    Read the article

1