How does device.map.old/device.map.new work?

English Install/Boot/Login
1

Hello, I recently cloned a portable opensuse system. But when I use this drive on my laptop and then after use it on the office’s computer, it always reports the /home partition is corrupted and I have to fsck everytime I do this.

I also notice that device.map.new under /boot/grub2 does not include the portable device where I installed it on, but it was shown on device.map.old.

And in YAST bootloader, the installation detail also doesn’t include the drive where I install the OS on but only the drive of the PC, which is identical to the content of device.map.old.

I think grub uses .new rather than .old right? Then why the drive where the os is installed is not listed in .new but .old???

Googled but still couldn’t understand how device.map.old is used by grub.

Anyone can explain how device.map.old/new works?

2

Grub2 does the mapping automatically, and uses device UUIDs (for unique identification), although it can be overridden with a manually-created map located in /boot/grub2/device.map if necessary.

3

On 2014-09-04 11:46, bonedriven wrote:
> I think grub uses .new rather than .old right? Then why the drive where
> the os is installed is not listed in .new but .old???

Probably neither. They are the old or previous version, and the proposal
for new version.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

4

As to need to run fsck. Are you shutting down properly before removing the drive? That would be the main reason to have to run it.

5

Well, once I saw device.map, but now I have only old and new.

It happened twice and in the same manner so I can’t make me believe I didn’t shutdown properly all the time. I’ll give it a try another time.

6

On 2014-09-04 20:16, bonedriven wrote:
> Well, once I saw device.map, but now I have only old and new.

Exactly.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)