Siduction Forum

@Teriarch: Thanks very much.
I tried your (mock) package and it works perfectly, as far as I can say. It installs without problem, leading to 'policycoreutils-dbus' becoming upgraded next without problems. I also experienced no error or problem in the running system.

May be @towo can be 'persuaded' to put your package into the 'fixed' repo. [A Debian solution would be better, of course.]

Ob du das mit einer (anderen)neuen Platte machst, ist dir überlassen. 

Seit Jahren mache ich das mit einer extra Partition /media/DATA, die in der fstab steht und auf allen meinen Rechnern existiert. Den Abgleich macht mir unison.

 


Das erleichtert das lesen von Code, das solltet Ihr üben! Danke.

Quote from: Teriarch on Yesterday at 00:47:21Where else can update-initramfs get this information from?
$ sudo grep -r d0a9d5f0-05ea-4b68-b279-015c623e387f /etc/*
 

THANK YOU!
sudo grep -r d0a9d5f0-05ea-4b68-b279-015c623e387f /etc/*

Returned the followint lines:

/etc/default/grub.ucf-dist:GRUB_CMDLINE_LINUX_DEFAULT="quiet resume=UUID=d0a9d5f0-05ea-4b68-b279-015c623e387f systemd.show_status=1"
/etc/fstab.save:UUID=23CC34C6703D21EC /wd/ntfs auto defaults,nofail,x-systemd.automount 0 2d0a9d5f0-05ea-4b68-b279-015c623e387f swap          swap    defaults  0 0

So, the old UUID comes from two backup files:

/etc/default/grub.ucf-dist
/etc/fstab.save

Can I remove both files safely or shall I insert the new UUID in them manually?
Or how to update them by force?

sudo update-grub

returns the following message with the new UUID (despite of the fact I've already added it to the /ets/default/grub)

/usr/sbin/grub-mkconfig: 1: /etc/default/grub: f367fdb7-62c0-4ecf-83de-c645d598287c#: not found

How to correct this?

Where else can update-initramfs get this information from?
$ sudo grep -r d0a9d5f0-05ea-4b68-b279-015c623e387f /etc/*
 

cat /etc/initramfs-tools/conf.d/resume
This command returns no answer

@alexsid
> sudo update-initramfs -u
> update-initramfs: Generating /boot/initrd.img-7.1.4-1-siduction-amd64
> cryptsetup: ERROR: Couldn't resolve device
> UUID=d0a9d5f0-05ea-4b68-b279-015c623e387f
What about:
$ cat /etc/initramfs-tools/conf.d/resume

I think, there is nothing special to provide.
When booting, I got many lines of the following message
mdadm no arrays found in config file... etc
Than the normal green messages go and the system boots in
sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-7.1.4-1-siduction-amd64
cryptsetup: ERROR: Couldn't resolve device 
    UUID=d0a9d5f0-05ea-4b68-b279-015c623e387f
in  /etc/default/grub
i change resume uuid to the new one. The swap PARTITION is active (checked in gparted).
The system still looks for the old uuid. How to correct this?

I added new swap partition uuid to etc/default/grub file
resume=UUID=f367fdb7-62c0-4ecf-83de-c645d598287c

and I get the following error trying to update grub
sudo update-grub
/usr/sbin/grub-mkconfig: 1: /etc/default/grub: f367fdb7-62c0-4ecf-83de-c645d598287c#: not found

@alexsid
> But this resolved the issue only partially. I still get mdadm error while booting.
This indicates, that initrd has trouble finding the root device. An update-grub could
help.
> I tried to update initramfs, but cannot because initramfs looks for the old UUID.
Please provide the command together with the error messages.

Hi all!
shIt happened!
I had 2 OSes on the same SSD disk.
All of a sudden Siduction warned me my root dev is full and has no free space.
I just opened Gparted and deleted the second OS, increased my root partition and created a new SWAP file.
Updated grub.
When booting I started to get "mdadm no arrays found..." error.
I noticed UUID the system could not find and found in fstab that the lost UUID is the one of the old SWAP file. I change the UUID to the new one in fstab. OK.
But this resolved the issue only partially. I still get mdadm error while booting.
I tried to update initramfs, but cannot because initramfs looks for the old UUID.
I'm guilty, my fault, but what shall I do to get rid of this error?