Tag Info

New answers tagged

1

bs=1 and count=66 you are delete only 66 bytes, the mbr code is 446 and the signatures is the last 2 bytes the MBR is not a partition but the first block of the disk, block 0 of size 512 bytes and is divided as follow: 446(bood code) + 64(partition table) + 2 (magic number) your problem is you are using skip man dd skip=N skip N ibs-sized blocks at ...


1

We have pinpointed the issue. This is ridiculous. The previous sysadmin had created an init script to make the directory and mount it on boot without outputting anything. Lesson for everyone -- please use standard configurations and save the sanity of the next person ahead of you.


3

Define "safe". As in: Does the system boot from USB? Yes Data integrity? No Fault tolerance? No I would not trust a file server to be booted from a single USB pen, unless it's a server just for testing/lab etc. We use USB drives (expensive ones) in our vSphere Cluster, and I've encountered failures many times. You've indicated that you have replaced the ...


3

Is it safe to boot Linux from a USB drive? Yes, why not? I do it regularly. But having said that, it's not entirely trivial to do it well. If you just straight install Linux to a USB disk it's usually really slow and doesn't really work that great. However, if you use a tool like unetbootin it'll create a more optimal installation with which you can ...


4

You can, but you probably shouldn't. The DL360 G7 doesn't present disks in a JBOD fashion. If you're using the onboard HP Smart Array controller, this won't work the way you expect. Depending on the OS you use, there are swap and other I/O activity considerations. Why go through all of this? If you want ZFS, just use it on the server in a baremetal OS ...


0

I believe the line you will need to add to your preseed file to answer "no" to that particular question is: d-i partman-partitioning/no_bootable_gpt_biosgrub boolean false


1

It's a bug This is really a bug (the static-network-up is not a job, it's an event signal). Moreover, using the network job as suggested in other answers is not the most correct solution. So, I created this bug report and submitted a patch to this problem. As a workaround, you can apply my proposed solution (at the end of this answer) and use the _netdev ...


0

You can PXE boot in UEFI mode or in Legacy mode... are you PXE booting the right way? is your PXE server able to provide the right NBP (Network Boot Program) depending on the boot mode. It seems to me you are PXE booting in the wrong mode that's why it fails but everything works if you somehow skip PXE from the boot sequence Note that the PXE is not ...


0

I don't know how "positive" you want to be that your AMI is clean, but it largely depends on the sensitivity and "statefulness" of the application and file system(s) running in the source instance. EBS snapshots don't have a capability to quiesce I/Os within the instance, so YMMV - it's basically as if you pulled the plug on your server. I personally have ...


0

In my configuration (corosync 1.4.2-3) I use the service.d out of corosync. /etc/corosync/service.d/pcmk service { # Load the Pacemaker Cluster Resource Manager name: pacemaker ver: 0 } This tells corosync to start the pacemaker resource manager. You won't have initscripts for pacemaker in this configuration (and even service ...


2

So it looks like, for some reason or another, having the PXE firmware be first in the boot order (which is how it was when I first got the server) breaks UEFI booting. When I set UEFI:debian as the first entry in the boot order, it boots all by itself, no intervention needed. The downside, of course, is that if I need a rescue OS over PXE, I need to first ...



Top 50 recent answers are included