search for: m4rtntns

...regards, Martin On Fri, Mar 7, 2014 at 5:57 PM, Andreas Dilger <adilger@dilger.ca> wrote: > Note that stride and stripe width only make sense for RAI-5/6 arrays. > For RAID-1 it doesn't really matter. > > Cheers, Andreas > >> On Mar 6, 2014, at 13:46, Martin T <m4rtntns@gmail.com> wrote: >> >> Hi, >> >> I created a RAID1 array of two physical HDD's with chunk size of 64KiB under Debian "wheezy" using mdadm. As a next step, I would like to create an ext3(or ext4) file-system to this RAID1 array using mke2fs utility. Accordin...

...bg option is used, since it already packs the bitmaps together and achieves the same effect. The second is meaningless for RAID-1 since writes go to every disk and there is no parity or read-modify-write for small or unaligned writes. Cheers, Andreas > On Mar 7, 2014, at 19:23, Martin T <m4rtntns@gmail.com> wrote: > > Andreas, > > why is it relevant only in case of RAID5 or RAID6? > > > regards, > Martin > >> On Fri, Mar 7, 2014 at 5:57 PM, Andreas Dilger <adilger@dilger.ca> wrote: >> Note that stride and stripe width only make sense for...

Note that stride and stripe width only make sense for RAI-5/6 arrays. For RAID-1 it doesn't really matter. Cheers, Andreas > On Mar 6, 2014, at 13:46, Martin T <m4rtntns@gmail.com> wrote: > > Hi, > > I created a RAID1 array of two physical HDD's with chunk size of 64KiB under Debian "wheezy" using mdadm. As a next step, I would like to create an ext3(or ext4) file-system to this RAID1 array using mke2fs utility. According to RAID-rela...

Hi, I created a RAID1 array of two physical HDD's with chunk size of 64KiB under Debian "wheezy" using mdadm. As a next step, I would like to create an ext3(or ext4) file-system to this RAID1 array using mke2fs utility. According to RAID-related tutorials, I should create the file-system like this: # mkfs.ext3 -v -L myarray -m 0.5 -b 4096 -E stride=16,stripe-width=32 /dev/md0

I would like to boot FreeDOS ISO image from USB memory stick using syslinux. I have done following: 1) I created a partition to my 2GB memory stick: root at debian64:~# fdisk -lu /dev/sdb Disk /dev/sdb: 2013 MB, 2013265920 bytes 62 heads, 62 sectors/track, 1022 cylinders, total 3932160 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size

Wrongly sent at first to the OP only, sorry. -------- Forwarded Message -------- Subject: Re: [syslinux] How to understand partition table on hybrid ISO image? Date: Tue, 23 Feb 2016 12:15:20 +0100 From: Didier Spaier <didier at slint.fr> To: Martin T <m4rtntns at gmail.com> On 23/02/2016 00:37, Martin T via Syslinux wrote: > When I try to understand what an hybrid ISO is, then looks like it is > a regular(according to El Torito standard) bootable ISO, which is > post-processes with isohybrid(?). > Isohybrid(https://gist.github.com/jsareni...

Thanks, this worked! What does the boot-time parameter "boot=casper" mean? In addition, what does the "cdrom-detect/try-usb=true" technically change? regards, Martin On Sun, Aug 16, 2015 at 9:24 PM, Marcin Celebucki <marcincelebucki at gmail.com> wrote: > Hi Martin > > You forgot add option which is required, see below: > > LABEL Ubuntu > LINUX

Hello, there is a "fdboot.img" floppy drive image included with FreeDOS ISO file. It's a floppy image file: root at debian64:~# file -s /home/martin/FreeDOS/isolinux/fdboot.img /home/martin/FreeDOS/isolinux/fdboot.img: x86 boot sector, FREE-DOS BEta 0.9 Bootloader KERNEL.SYS, code offset 0x40, OEM-ID "FreeDOS ", sectors/cluster 2, root entries 112, sectors 720 (volumes

Hi, I'm trying to install debian-6.0.5-amd64-CD-1.iso from USB memory-stick. The problem is, that Debian-Installer is not able to "Detect and mount CD-ROM" during the installation process. The USB memory-stick is a 2GB model containing MBR and FAT32 file system: # fdisk -lu /dev/sdb Disk /dev/sdb: 2013 MB, 2013265920 bytes 62 heads, 62 sectors/track, 1022 cylinders, total 3932160

I would like to boot Ubuntu 8.04 i386 from my USB flash drive. I was guided by this tutorial: http://syslinux.zytor.com/wiki/index.php/HowTos#How_to_Create_a_Bootable_USB:_For_Linux I took following steps: 1) made sure that usb_storage.ko kernel module is loaded root at martin-desktop:~# lsmod | grep -i storage usb_storage 39585 1 root at martin-desktop:~# 2) inserted USB flash

----------------------------------------------------------------------- Martin T soovib m?ningaid Google'i uusi lahedaid tooteid kasutades t?husamalt suhelda. Kui teil on juba Gmail v?i Google Talk, k?lastage: http://mail.google.com/mail/b-b1582f7c47-bb95c4c048-xaFhqyy53hFz38AqKrnAp3IUOaM Kasutajaga Martin T vestlemiseks peate kl?psama seda linki. Selleks, et hankida endale Gmail ? rohkem

Hi, I zero-filled first 10MiB of my SSD(dd if=/dev/zero of=/dev/sda bs=10M count=1). As expected, this wiped my primary GPD header and first partition. Before the wipe, GPT was following: Disk /dev/sda: 250069680 sectors, 119.2 GiB Logical sector size: 512 bytes Disk identifier (GUID): 2EFD285D-F8E6-4262-B380-232E866AF15C Partition table holds up to 128 entries First usable sector is 34, last

Hi, I remember I had a bootable USB flash drive with few Linux distributions four to five years ago. iso files for Linux distributions and initial ramdisk(copied from extracted iso file) and Linux kernel(copied from extracted iso file) were on the USB flash drive. So I tried to create something similar with latest Ubuntu and in order to keep things simple, I did not add any additional

Hi, if I inspect an hybrid ISO with tools like fdisk and gdisk, then looks like hybrid ISO has both the MBR and GPT in order to support both the BIOS and UEFI: # gdisk -l /dev/sdb GPT fdisk (gdisk) version 0.8.10 Partition table scan: MBR: MBR only BSD: not present APM: not present GPT: present Found valid MBR and GPT. Which do you want to use? 1 - MBR 2 - GPT 3 - Create blank GPT