fll-iso2usb takes more than half an hour...

[mylo]

Hi all,
I try to create a boot stick, however after more than 30 minutes the system is still on preparation:

Code Select Expand

fll-iso2usb -D /dev/sda -f none --iso /home/mylo/siduction.iso -p lang=de tz=Europe/Berlin
Grubversion: 2 - Grub2: true
O: using partition /dev/sda1
O: mounting /dev/sda1 on /tmp/install-usb.Tlhlek
O: mount point ready: /tmp/install-usb.Tlhlek
/tmp/install-usb.Tlhlek
O: installing grub on /dev/sda
installation beendet. Keine Fehler aufgetreten.
grep: /tmp/install-usb.Tlhlek/boot/grub/device.map: Datei oder Verzeichnis nicht gefunden
sed: kann /tmp/install-usb.Tlhlek/boot/grub/device.map nicht lesen: Datei oder Verzeichnis nicht gefunden
O: grub successfully installed to /dev/sda
O: mounting iso: /home/mylo/siduction.iso
O: iso mounted on /tmp/install-usb-iso.DzWJst
O: copying files to /tmp/install-usb.Tlhlek
,,/tmp/install-usb-iso.DzWJst/boot/initrd0.amd" -> ,,/tmp/install-usb.Tlhlek/boot/initrd0.amd"
,,/tmp/install-usb-iso.DzWJst/boot/vmlinuz0.amd" -> ,,/tmp/install-usb.Tlhlek/boot/vmlinuz0.amd"
,,/usr/share/grub/unicode.pf2" -> ,,/tmp/install-usb.Tlhlek/boot/graphics/unicode.pf2"
O: files copied to /tmp/install-usb.Tlhlek
O: copying the iso files to the /tmp/install-usb.Tlhlek
,,/home/mylo/siduction.iso" -> ,,/tmp/install-usb.Tlhlek/siduction.iso"
O: iso successfully copied to /tmp/install-usb.Tlhlek
O: Initializing persistent overlay
O: 10403152k free space on /tmp/install-usb.Tlhlek
O: creating persistent loopback file, count=634
3,36GB 0:34:13 [1,68MB/s]s]


And is has not come to the end by now. Has anybody here experience, that this takes so long? It is a 16 GB stick formatted to ext2.

[ayla]

Hi mylo,

didn't used ffl-iso2usb for a longer time, but your command line looks to me as you are installing to your first HD. Are you sure /dev/sda is the right target?

-D|--device <device>
              name of device where to install the "fromiso"

fll-iso2usb -D /dev/sda

and:

O: mounting /dev/sda1 on /tmp/install-usb.Tlhlek
O: 10403152k free space on /tmp/install-usb.Tlhlek

This is about 10 GB.


greets
ayla

[mylo]

Hi ayla,

device is sda, I checked that wih gparted.
When the stick is plugged in before starting the box, it is sda (the hd's then get sdb and sdc).

The stick has 16 GB and the message said, it already installed 2 or more GB, so that looks right.

[ayla]

ok then, have a free 8GB-Stick here, will try using your command (accordingly) and report back.

[ayla]

Hi mylo,

seems to be very slow here, too. 4.5MB/s -on an USB3-Device, which hdparm -tT --direct tells about 45MB/s.

It seems to finish now, but slooooowly:

fll-iso2usb -D /dev/sde -f none --iso /home/cal/siduction-13.2.rc1-december-kde-amd64-201312222013.iso -p lang=de tz=Europe/Berlin
Grubversion: 2 - Grub2: true
O: using partition /dev/sde1
O: mounting /dev/sde1 on /tmp/install-usb.f4yPVG
O: mount point ready: /tmp/install-usb.f4yPVG
/tmp/install-usb.f4yPVG
O: installing grub on /dev/sde
installation beendet. Keine Fehler aufgetreten.
grep: /tmp/install-usb.f4yPVG/boot/grub/device.map: Datei oder Verzeichnis nicht gefunden
sed: kann /tmp/install-usb.f4yPVG/boot/grub/device.map nicht lesen: Datei oder Verzeichnis nicht gefunden
O: grub successfully installed to /dev/sde
O: mounting iso: /home/cal/siduction-13.2.rc1-december-kde-amd64-201312222013.iso
O: iso mounted on /tmp/install-usb-iso.OzHZNY
O: copying files to /tmp/install-usb.f4yPVG
,,/tmp/install-usb-iso.OzHZNY/boot/initrd0.amd" -> ,,/tmp/install-usb.f4yPVG/boot/initrd0.amd"
,,/tmp/install-usb-iso.OzHZNY/boot/vmlinuz0.amd" -> ,,/tmp/install-usb.f4yPVG/boot/vmlinuz0.amd"
,,/usr/share/grub/unicode.pf2" -> ,,/tmp/install-usb.f4yPVG/boot/graphics/unicode.pf2"
O: files copied to /tmp/install-usb.f4yPVG
O: copying the iso files to the /tmp/install-usb.f4yPVG
,,/home/cal/siduction-13.2.rc1-december-kde-amd64-201312222013.iso" -> ,,/tmp/install-usb.f4yPVG/siduction.iso"
O: iso successfully copied to /tmp/install-usb.f4yPVG
O: Initializing persistent overlay
O: 6378564k free space on /tmp/install-usb.f4yPVG
O: creating persistent loopback file, count=389
389+0 Datensätze einMB/s]
389+0 Datensätze aus
3263168512 Bytes (3,3 GB) kopiert, 694,428 s, 4,7 MB/s
3,04GB 0:11:36 [4,47MB/s]
389+0 Datensätze ein
389+0 Datensätze aus
3263168512 Bytes (3,3 GB) kopiert, 698,559 s, 4,7 MB/s
mke2fs 1.42.8 (20-Jun-2013)
/tmp/install-usb.f4yPVG/siduction/siduction-rw is not a block special device.
Proceed anyway? (y,n) Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
199200 inodes, 796672 blocks
39833 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=817889280
25 block groups
32768 blocks per group, 32768 fragments per group
7968 inodes per group
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912

Allocating group tables: done                           
Writing inode tables: done                           
Writing superblocks and filesystem accounting information:     

greets
ayla

EDIT: Works now, after about 45 min, writing from system on Stick.

[mylo]

Hi ayla,

thanks for testing and reporting. I made the same experience and succeeded at the end also.
Now I am on my new box on the live-usb-stick-installation.

I will now go on to feed the 250 GB SSD. I am just thinkin about ext4 or btrfs. Has anyone a recommendation?

[dibl]

I am just thinkin about ext4 or btrfs. Has anyone a recommendation?

I use btrfs for a 2-drive filesystem of 2TB -- a pair of 1TB Western Digital drives.  It has been very stable -- that is where I keep all my longterm data.


But, btrfs offers no advantages on a 250GB SSD.  And it will not support a VM, unless they have fixed that issue since I last reviewed it.  So I recommend ext4 for an SSD, with a modified journal commit time in /etc/fstab.  For my desktop system SSD, I use commit=120, like this:

Code Select Expand

UUID=8cfe2acc-7572-4b45-b25f-ed021bb1d78b     /mnt/SDA2            ext4         noatime,commit=120


But 2 minutes is a long time in the life of a filesystem, so this would be too long if you are shutting the lid on a laptop 10 seconds after you saved a document.  The default commit time of 5 seconds is going to write on the same sector of your SSD every 5 seconds, so you might want to think about how long is safe to increase that interval, for your situation.

[mylo]

Thanks dibl,

I just succeeded to install on the ssd from the stick and will now enter fstab.
"noatime" seems important, I have to understand in detail what commit does  and set it then. I went for ext4. Thanks for your recommendation.

[dibl]

"commit=nn" is the number of seconds between journal writes on the media, in seconds.  Default (if you don't write the option in /etc/fstab) is 5 seconds.  So my commit=120 says to write the journal every 120 seconds, not every 5 seconds.  But this is a desktop system that runs for days between reboots, and runs on a UPS with battery backup.  If you are using a laptop for productive work, then 120 seconds might be too long to risk losing some data.


Also, I see when I copied my /etc/fstab line I missed the dump and pass values.  The entire line is

Code Select Expand

UUID=8cfe2acc-7572-4b45-b25f-ed021bb1d78b     /mnt/SDA2            ext4         noatime,commit=120           0    0

[mylo]

Hi dibl,

thanks I will go for your commit 120, seems reasonable for me.
I have three parts:

/, /home and /data.

Do I give all three of them the noatime and the commit?

What is your recommendation?

[devil]

If this is your new ssd, you also need 'discard' in your fstab lines, so TRIM gets to do it's job.


greetz
devil

[dibl]

If this is your new ssd, you also need 'discard' in your fstab lines, so TRIM gets to do it's job.

Or else you need to run fstrim once in awhile.  See

Code Select Expand

man fstrim

[ghstryder]

Or else you need to run fstrim once in awhile.

I run fstrim as a daily cron job. I'm far from expert, but I've been happy with the results to date.

[mylo]

"commit=nn" is the number of seconds between journal writes on the media, in seconds.  Default (if you don't write the option in /etc/fstab) is 5 seconds.  So my commit=120 says to write the journal every 120 seconds, not every 5 seconds. ...

Code Select Expand

UUID=8cfe2acc-7572-4b45-b25f-ed021bb1d78b     /mnt/SDA2            ext4         noatime,commit=120           0    0

Hi dibl,

do you have any recommendation for a commit preset value for

1) the /
2) the /home

partition?
Is it a high risk to have commit=120 for "/"?

[melmarker]

mylo: Standard is 5s - and Linus called all other, higher values braindead some times ago - i would think, that loosing not synced data is not so high, if there is any power backup - in case of the notebook the accu, in case of PC a usv, in case of a cache controller: batterypack for the controller and usv