similar to: I/O error

On Tue, Feb 17, 2015 at 12:57:32PM +0100, Jur van der Burg via Syslinux wrote: > We have been using syslinux (V4.05) in our product for years without a problem. > Since we encounter more and more systems that do a UEFI boot by default > we want to support that too. So I've been using syslinux V6.03 to create > usb sticks and harddisks to allow both bios and uefi boot which works

We have been using syslinux (V4.05) in our product for years without a problem. Since we encounter more and more systems that do a UEFI boot by default we want to support that too. So I've been using syslinux V6.03 to create usb sticks and harddisks to allow both bios and uefi boot which works fine. The problem I run into now is that it is not possible to create a dvd that is capable of

> We have been using syslinux (V4.05) in our product for years without a problem. > Since we encounter more and more systems that do a UEFI boot by default > we want to support that too. So I've been using syslinux V6.03 to create > usb sticks and harddisks to allow both bios and uefi boot which works fine. > > The problem I run into now is that it is not possible to create

Hi, I found a bug in extlinux/main.c. Writing a bootloader on a file mounted via /dev/mapper in Lunix it crashed on me with a segment fault. The bug is here: if (!ioctl(devfd, HDIO_GETGEO, &geo)) { Since we are already called with geo as a pointer the & is wrong as the pointer itself will be overwritten. This works: int get_geometry(int devfd, uint64_t totalbytes, struct

> Thank you all. > > It looks like -mno-red-zone flag is already in master branch since > commit 7d70885d, but it seems it is applied to all EFI builds. Finally we are on the same page. > > IIUC, the problem only affects efi64 builds. Have you actually tested efi32 (ia32) builds? > > So here's the modification of my patch to only apply -mno-red-zone >

Thank you very much for this, I have been running into this issue a number of times but could never get a firm grip on it. Especially HP Gen9 proliants seem to suffer from it by sometimes throwing a stack dump very early in the boot. In the past we worked around it by forcing bios boot. After rebuilding it with -mno-red-zone the problem appears to be fixed, at least after a couple of hours of

Hello, I have a problem with special characters such as "?" or "?" when using hwriter. This only happens when I use windows, it works fine on mac. If I do: print(datosdv) "Ciencias Sociales y Jur?dicas n:74 | 33.94%" but: hwrite(datosdv, p, br=TRUE) "Ciencias Sociales y Jur?dicas n:74 | 33.94%" The bad sign is in the code, is not a problem of the

Hi All, For those testing EXT4 I seem to have found an issue with anaconda where by if you specify EXT4 fstype in your kickstart file it will not install and complains that if needs another 250MB of disk space. I've tried with my kickstart set for 10G for root at ext3 and it works fine. 10,15 and 20GB with EXT4 all fail. BTW: can't put /boot on it either. Just a heads up for all.

2012/6/5 Kok, Auke-jan H <auke-jan.h.kok@intel.com> wrote on systemd-devel list: > It seems your system is taking well into 15+ seconds before btrfs is > actually *ready* on your system, which seems to be the main hiccup > (note, speculation here). I''ve personally become a bit displeased with > btrfs performance recently myself, so, I''m wondering if you should

Hi Konrad, Does this look at all familiar? There is some more info in the full bug log at http://bugs.debian.org/637234 . In particular, contrary to the message below, the user subsequently confirmed that the issue appears to be Xen specific (doesn''t happen on native or vmware) and that it arose between 2.6.39-2-686-pae and 3.0.0-1-686-pae. Could it be related to edf6ef59ec7e

Hi Artem, Was the volume size correct before the bricks were expanded? This sounds like [1] but that should have been fixed in 4.0.0. Can you let us know the values of shared-brick-count in the files in /var/lib/glusterd/vols/dev_apkmirror_data/ ? [1] https://bugzilla.redhat.com/show_bug.cgi?id=1541880 On 17 April 2018 at 05:17, Artem Russakovskii <archon810 at gmail.com> wrote: > Hi

To clarify, I was on 3.13.2 previously, recently updated to 4.0.1, and the bug seems to persist in 4.0.1. Sincerely, Artem -- Founder, Android Police <http://www.androidpolice.com>, APK Mirror <http://www.apkmirror.com/>, Illogical Robot LLC beerpla.net | +ArtemRussakovskii <https://plus.google.com/+ArtemRussakovskii> | @ArtemR <http://twitter.com/ArtemR> On Mon, Apr

Hi Nithya, I'm on Gluster 4.0.1. I don't think the bricks were smaller before - if they were, maybe 20GB because Linode's minimum is 20GB, then I extended them to 25GB, resized with resize2fs as instructed, and rebooted many times over since. Yet, gluster refuses to see the full disk size. Here's the status detail output: gluster volume status dev_apkmirror_data detail Status

That might be the reason. Perhaps the volfiles were not regenerated after upgrading to the version with the fix. There is a workaround detailed in [2] for the time being (you will need to copy the shell script into the correct directory for your Gluster release). [2] https://bugzilla.redhat.com/show_bug.cgi?id=1517260#c19 On 17 April 2018 at 09:58, Artem Russakovskii <archon810 at

Hello, setting up the newest OpenStack Grizzly release seems to be really straight-forward. Red Hat has put together all support for this at http://openstack.redhat.com/. I've documented installation, post-install config tweaks, how to add a few ready-to-use guest images and links to a few gotchas on the following wiki page: http://jur-linux.org/testwiki/index.php/CloudLinux/OpenStack

i make a image file connected to /dev/loop0 formated as ext4 partition and connect it losetup /dev/loop0 /root/disk.img then make format the loop drive with mkfs.ext4 -o rw,usrquota,grpquota /dev/loop0 connected it to /test the only way to write there other users except root is setting with chmod o+w /test from windows 7 using samba 4 i can write to folder but i cannot set security setting

On Wed, Dec 27, 2017 at 12:12:33AM +0100, Dmitry Katsubo via samba wrote: > Dear Samba community, > > I am facing the following problem. I have the following share in my > /etc/samba/smb.conf: > > [external] > comment = "External Hard Drive" > path = /mnt/external > read only = no > > Sometimes it happens that external hard drive fails. Kernel

I just remembered that I didn't run https://docs.gluster.org/en/v3/Upgrade-Guide/op_version/ for this test volume/box like I did for the main production gluster, and one of these ops - either heal or the op-version, resolved the issue. I'm now seeing: pylon:/var/lib/glusterd/vols/dev_apkmirror_data # ack shared-brick-count dev_apkmirror_data.pylon.mnt-pylon_block3-dev_apkmirror_data.vol

Dear Samba community, I am facing the following problem. I have the following share in my /etc/samba/smb.conf: [external] comment = "External Hard Drive" path = /mnt/external read only = no Sometimes it happens that external hard drive fails. Kernel issues USB reset and the device /dev/sde1 in example below becomes invalid/inaccessible: Dec 26 21:41:03.523585 kernel: usb

Ok, it looks like the same problem. @Amar, this fix is supposed to be in 4.0.1. Is it possible to regenerate the volfiles to fix this? Regards, Nithya On 17 April 2018 at 09:57, Artem Russakovskii <archon810 at gmail.com> wrote: > pylon:/var/lib/glusterd/vols/dev_apkmirror_data # ack shared-brick-count > dev_apkmirror_data.pylon.mnt-pylon_block3-dev_apkmirror_data.vol > 3: