Hey Alexey!

21 Oct 16, Alexey Vissarionov wrote to Kai Richter:

 KR>> Just ignore comments that were done without knowledge about your
 KR>> system configuration.

 AV> Do you think he's still using a 486? :-)

I don't know what he's using. That's why i don't think i can call him names.

 KR>> There are good reasons for seperate /boot partitions.

 AV> There _were_ some, but they are left in previous century.

My mailbox was build on 486/DX2, replaced by P1/166 in 2007, replaced by UEFI
doing BIOS system in 2013. It worked well to take the /boot partition through
the hardware changes, i just took over the IDE disks LVM array cage.

 KR>> Some older BIOS based machines can't boot too big harddisks
 KR>> without it.

 AV> It seems like you don't exactly know how does the boot-up process
 AV> work...

That is true for sure. With UEFI standard everything is new and with the EFI
System Partitions they invented a totally new concept of a seperate boot
partition. [/ironic]

 KR>> Backup is always good. The first action in broken HD faults is a
 KR>> disk copy with the tool dd_rescue. dd_rescue ignores read errors
 KR>> and all readable data is copied.

 AV> Ordinary /bin/dd works just fine: read `man dd` and find the conv=
 AV> section.

I'm too lazy for typing conv=noerror. dd_ can be TAB-ed and is easy to
remember. ;)

 AV> I simply have some real experience in data recovery, including broken
 AV> RAIDs (especially built with proprietary controllers) and LVMs (best
 AV> known way of losing all the data at once, thanks to errors in a
 AV> devmapper code).

Btw, with / on LVM a seperate /boot makes trouble shooting easier. I could
start shell or rescue to analyse the LVM trouble.

I would change to ZFS if it support disk removal instead of breaking a pool.

Tschuess

Kai

--- GoldED+/LNX 1.1.4.7