Good ${greeting_time}, Kai!

20 Oct 2016 18:46:36, you wrote to Gert Andersen:

 AV>>> JFYI: when the installation program suggests to make separate
 AV>>> partition for /boot, you'd better don't use the distribution
 AV>>> built by idiots.
 KR> Just ignore comments that were done without knowledge about your
 KR> system configuration.

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

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

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

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

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

 GA>>>>>> but now will linux not mount it and says there is error on the
 GA>>>>>> harddisk. It comes with that the superblok is missing o it
 GA>> I still have all the files on my first node system
 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.

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

 KR> If i had a working backup of the lost files i wouldn't put too
 KR> much time into rescue actions. But Alexeys steps are a good start.

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

 KR> It may be possible that the badblocks stay on the fist sectors of
 KR> the disk and do not grow. If so, the disk may be used further but
 KR> should be considered unsafe and stay under frequently observation.
 KR> If the smartctl data grows, discard the disk.

2 GA: if you have 3 or more such disks, you may still use them in a RAID-1
(mirroring) storage, using it as one of backup places (building with only 2
failing devices would be unsafe).


--
Alexey V. Vissarionov aka Gremlin from Kremlin
gremlin.ru!gremlin; +vii-cmiii-cmlxxvii-mmxlviii

... :wq!
--- /bin/vi