Ssh

[Maciek Rydzia]

Wysłane z iPada

Bug#1000239: Rescue system won't find root partition, but insists on /usr

[TomK]

In commercial and industrial applications It is common to have discrete 
partitions for /, /boot, /home, /usr swap and /var. The rationale for doing so 
lies in three areas. /var can and does fill up with log files frequently. 
Having it separate has long been a means to prevent / from filling up, and to 
permit resizing /var without taking down the system.

Many times hardware failure will destroy a partition, and it's much less work 
to recover if 'everything' does not reside on a single partition. Judicious use 
of disk space dictatates splitting large disks into smaller partitions, which 
function more efficiently.

If there is a /usr partition, /usr/share will be part of it. So, separate 
/usr/share is exactly as common s/as separate /usr. For home use none of this 
matters, because it is trivial to reinstall the OS. Although, my personal lappy 
has five partitions on the disk.

/usr/share has architecture independent files which are architecture 
independent only because they are not binaries. No documentation is 
architecture dependent!  The reader may be, but not the actual documentation, 
as is found in /usr/share/.  


 Original Message 
From: Pascal Hambourg 
Sent: December 8, 2021 11:41:11 AM UTC
To: Philip Hands , 1000...@bugs.debian.org, TomK 

Subject: Re: Bug#1000239: Rescue system won't find root partition, but insists 
on /usr

Le 08/12/2021 à 10:49, Philip Hands a écrit :
> 
> Is it a problem if /home or /usr/share are left unmounted during rescue?

/usr/share contains architecture-independent files for many programs 
such as bash, grub, os-prober, debconf, dpkg, initramfs-tools...

How common is it to have a separate /usr/share and what is the rationale 
for it ?

Bug#1001439: installation-reports: activating swap /dev/disk/by-uuid/..... failed to activate swap /dev/.....dependency failed ...

[Gérard ROBIN]

Package: installation-reports
Severity: important

(Please provide enough information to help the Debian
maintainers evaluate the report efficiently - e.g., by filling
in the sections below.)

Boot method: CD
Image version: debian-11.1.0-i386-netinst.iso
Date: 

Machine: ASUS A7N8X 400 mHz FSB DDR 400 Dual LAN IEEE 1394 6 USB Ports
Partitions: 


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it


Initial boot:   [O ]
Detect network card:[O ]
Configure network:  [O ]
Detect media:   [O ]
Load installer modules: [O ]
Clock/timezone setup:   [O ]
User/password setup:[O ]
Detect hard drives: [O ]
Partition hard drives:  [O ]
Install base system:[O ]
Install tasks:  [O ]
Install boot loader:[O]
Overall install:[O ]

Comments/Problems:

On my machine there are two hard drives on one (sda) there was 'stretch' on
the other (sdb) there was 'jessie'. The wifi connection is made with a USB
key which requires firmware-realtek.
After an upgrade on sda the wifi connection no longer worked but on sdb with
jessie the wifi connection worked.
After looking on the internet I concluded that the problem was with the
kernel used on sda and that a newer kernel should be upgraded.
So I went from stretch to buster without problems but the wifi still didn't
work. So I went from buster to bullseye but starting the machine (on sda) I
got:

FAILED failed to start file system check on /dev/disk/by-uuid

DEPEND dependency failed for /home
DEPEND dependency failed for local file system
DEPEND dependency failed for mark the need to relabel after reboot

to continue "Ctrl D" or give the root password 

I gave the root password and miracle the wifi work.
/home is mounted, normally, on /dev/sda8 but since it is not mounted I did:

fsck /dev/sda8 

but it can not repair the ext4 filesystem and I shutdown -h now.

The kernel 4.19 of "buster" had remained on sda and I started the machine on
this kernel and there the boot took place until the end but the wifi did not
work, so I created a CD bullseye and I installed bullseye completely with the 
CD.
When choosing the partitioning I chose to create the partitions:
/home
/var
/tmp  
The installation seems to be going normally and is completed.
So I start the machine again and the same thing starts over: 


FAILED failed to start file system check on /dev/disk/by-uuid

DEPEND dependency failed for /home
DEPEND dependency failed for local file system
DEPEND dependency failed for mark the need to relabel after reboot

to continue "Ctrl D" or give the root password 


So I think if I choose to create only one partition the problem with /home
will go away. So I reinstall bullseye with only one partition and this time
the bullseye startup goes to completion with another error on swap.

Part of /var/log/boot.log:

 Wed Dec 08 00:21:12 CET 2021 
/dev/sda1: clean, 109448/4825088 files, 1260233/19287296 blocks
[  OK  ] Finished Tell Plymouth To Write Out Runtime 
Data.
[  OK  ] Finished Set console font and keymap.
[  OK  ] Finished Create Volatile Files and Directories.
Starting Network Time Synchronization...
Starting Update UTMP about System Boot/Shutdown...
[  OK  ] Finished Update UTMP about System 
Boot/Shutdown.
[  OK  ] Started Network Time Synchronization.
[  OK  ] Reached target System Time Set.
[  OK  ] Reached target System Time Synchronized.
[  OK  ] Started Rule-based Manager for Device Events and 
Files.
 Starting Show Plymouth Boot Screen...
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth 
Directory Watch.
[  OK  ] Reached target Local Encrypted Volumes.
[  OK  ] Reached target Paths.
[  OK  ] Found device WDC_WD800BB-75CAA0.
 Activating swap 
/dev/disk/by-uuid/4fd7c431-260b-4140-bd9a-25ff51088540...
[  OK  ] Listening on Load/Save RF Kill Switch Status 
/dev/rfkill Watch.
[FAILED] Failed to activate swap 
/dev/disk/by-uuid/4fd7c431-260b-4140-bd9a-25ff51088540.
See 'systemctl status 
"dev-disk-by\\x2duuid-4fd7c431\\x2d260b\\x2d4140\\x2dbd9a\\x2d25ff51088540.swap"'
 for details.
[DEPEND] Dependency failed for Swap.
 Activating swap 
/dev/disk/by-uuid/4fd7c431-260b-4140-bd9a-