[SOLVED] delete (created ?) block devices

cd187 · 2023-02-25 07:54:47

Hi,

I was installing archlinux arm on a raspberry pi4, and for aarch64 it was wrotten (in the arch linux arm installation guide), before unmount partitions, to use the command :
sed -i 's/mmcblk0/mmcblk1/g' root/etc/fstab
But (that was stupid error I know) I wrote :
sed -i 's/mmcblk1p0/mmcblk1p1/g' root/etc/fstab (I think the issue is from this command ...)

And now when I type lsblk command I obtain :

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 931,5G 0 disk
├─sda1 8:1 0 2G 0 part /boot
└─sda2 8:2 0 929,5G 0 part
└─root 254:0 0 929,5G 0 crypt /home
/
sr0 11:0 1 1024M 0 rom
mmcblk0 179:0 0 29,1G 0 disk
mmcblk0boot0 179:8 0 4M 1 disk
mmcblk0boot1 179:16 0 4M 1 disk
zram0 253:0 0 1,8G 0 disk [SWAP]

So I'd like to remove mmcblk0boot0 and mmcblk0boot1(in read only ?) because the only sd card reader I have is mmcblk0. I don't understand exactly how I did it and I don't know how to remove it.

As a noob, I thought I just need to remove them in /dev but it doesn't works ... I read udevadm man, I tried to find something in run/udev/data and usr/src/linux but I havn't found anything.

So it's time to recognize that I won't do it alone ... And I need your help.

Thanks guys for answer !

Last edited by cd187 (2023-02-25 13:50:21)

skunktrader · 2023-02-25 08:18:04

post the contents of /etc/fstab

cd187 · 2023-02-25 08:57:56

I already checked fstab and found nothing about mmcblk0 ... here is my /etc/fstab file :

# Static information about the filesystems.
# See fstab(5) for details.

# <file system> <dir> <type> <options> <dump> <pass>
# /dev/mapper/root
UUID=906c4af7-3791-48d0-9963-e9e2c8f8c206 / btrfs rw,noatime,compress=zstd:3,ssd,discard=async,space_cache=v2,subvolid=256,subvol=/@ 0 0

# /dev/sda1
UUID=A5C0-DFBE /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

# /dev/mapper/root
UUID=906c4af7-3791-48d0-9963-e9e2c8f8c206 /home btrfs rw,noatime,compress=zstd:3,ssd,discard=async,space_cache=v2,subvolid=257,subvol=/@home 0 0

seth · 2023-02-25 10:21:59

sed'ing around in fstab won't create block devices, it's far more likely that those partitions actually exist.
In any event devfs is transient, reboot and it'll be re-populized.

Also https://bbs.archlinux.org/misc.php?action=rules - ALARM has its own boards.

cd187 · 2023-02-25 10:40:14

I'm speaking about my arch on my laptop (not on the raspberry, for sur ther is no place in this forum for RPI).
The comand line created on my laptop this two block device .... it's not partition otherwise I could delete them easily with fdisk or gdisk, but I can't, It's considered as a block device so I can type :
fdisk /dev/mmcblk0boot0
or:
fdisk /dev/mmcblk0boot1
Moreover these two block device are read only so if I try to make partition inside I can't.

When i type the commande line fdisk /dev/mmcblk0boot0 it prevents me :
Le périphérique ne contient pas de table de partitions reconnue. (no partition table)
Création d'une nouvelle étiquette pour disque de type DOS avec identifiant de disque 0x2762bfb2 (the equivalent of the result for o command in fdisk).

I create a partition and when I wanna write, it answer :
fdisk: échec d'écriture de l'étiquette de disque: Opération non permise (error, not allowed)

the same answer with su commande before fdisk /dev/mmcblk0boot0

V1del · 2023-02-25 11:17:18

As already mentioned chances are these actually exist and are already part of the disk. Absolutely nothing about that sed command would create these kinds of devices. You are most likely worrying about a non issue.

seth · 2023-02-25 11:17:49

sed -i 's/mmcblk0/mmcblk1/g' root/etc/fstab

doesn't create block devices anywhere for absolutely sure.

You're using some kind of card reader here?
It probably has multiple slots that generate multiple devices, eg. an external usb sata reader here generates sdb, sdc, sdd & sde, but there's only one card inside, providing sdb1
There's really nothing special or worrysome about this.

Also, if you're looking at the output (that you should have posted in code tags for readability) mmcblk0boot* are read-only.

cd187 · 2023-02-25 11:42:09

I use the card reader (on the motherboard) only for the sd card in order to install archlinux arm on RPI, ther are not multi slot, only one

Before creating the SD card bootable I never saw (99,9% sure) this two block device and their name means I made something wrong cause I never saw this device appelation on any computer.

Effectively I found strange the fact that the command sed -i 's/mmcblk0/mmcblk1/g' root/etc/fstab could change device block...

What I want (it doesn't matter if I don't understand how I did it ...) is to remove these two block. But I don't know how. That's my question :

Is there a tool to manage block device ? or a file to modify to make them desapear ? If not I will close the subject. Anyway, I won't have any kind of problem, just curious to understand how I could do it and, how we can manage the device block ?

I'm a little bit maniac and , as I haven't seen it before, I'd like to restaure.

seth · 2023-02-25 11:51:27

Effectively I found strange the fact that the command sed -i 's/mmcblk0/mmcblk1/g' root/etc/fstab could change device block...

Because it doesn't.

Do the block devices remain if you remove the sd card? If you then reboot?

cd187 · 2023-02-25 12:10:26

Yes ... the block devices remains. There are two days I removed the sd card, so it's empty, and I power off my laptop many times.

seth · 2023-02-25 12:17:36

And what is the 29GB mmcblk0 ?

cd187 · 2023-02-25 12:24:32

mmcblk0 is the original flashdisk of the computer (there was a f***** windows 10 on this laptop, that why the owner give it to me because it was too slow). There is no partition inside (as you can see in lsblk result), I deleted all, and I don't use this device.

I put a SSD 1To and install my arch on it.

seth · 2023-02-25 12:26:26

Please post your complete system journal:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

cd187 · 2023-02-25 12:47:26

excuse me i tried to post but i got this msg
{user} was opened within itself, this is not allowed
I dont know what does i mean

seth · 2023-02-25 12:50:00

What?
"url"? That's a bbcode message, you're supposed to post the link that 0x0.st returns.
Don't post the text here, certainly not w/o code tags.
But really just post the 0x0.st link.

cd187 · 2023-02-25 12:54:02

http://0x0.st/Hs0Q.txt

seth · 2023-02-25 13:29:26

févr. 25 13:35:05 pacman-bois kernel: sdhci: Secure Digital Host Controller Interface driver
févr. 25 13:35:05 pacman-bois kernel: sdhci: Copyright(c) Pierre Ossman
févr. 25 13:35:05 pacman-bois kernel: sdhci-pci 0000:00:1c.0: SDHCI controller found [8086:5acc] (rev b)
févr. 25 13:35:05 pacman-bois kernel: mmc0: SDHCI controller on PCI [0000:00:1c.0] using ADMA 64-bit
févr. 25 13:35:05 pacman-bois kernel: mmc0: new HS400 MMC card at address 0001
févr. 25 13:35:05 pacman-bois kernel: mmcblk0: mmc0:0001 BJNB4R 29.1 GiB 
févr. 25 13:35:05 pacman-bois kernel:  mmcblk0:
févr. 25 13:35:05 pacman-bois kernel: mmcblk0boot0: mmc0:0001 BJNB4R 4.00 MiB 
févr. 25 13:35:05 pacman-bois kernel: mmcblk0boot1: mmc0:0001 BJNB4R 4.00 MiB 
févr. 25 13:35:05 pacman-bois kernel: mmcblk0rpmb: mmc0:0001 BJNB4R 4.00 MiB, chardev (237:0)

This is the eMMc and common:
https://www.google.com/search?q=%22BJNB … k0boot1%22

cd187 · 2023-02-25 13:41:20

Si it was here feom the begining. Excuse me i was sure it s not. The most important is to know that it s not a mistake but normal. And now i know what they are.

Thank you for the time you spent to answer me ans to give me the answer.

Arch Linux

#1 2023-02-25 07:54:47

[SOLVED] delete (created ?) block devices

#2 2023-02-25 08:18:04

Re: [SOLVED] delete (created ?) block devices

#3 2023-02-25 08:57:56

Re: [SOLVED] delete (created ?) block devices

#4 2023-02-25 10:21:59

Re: [SOLVED] delete (created ?) block devices

#5 2023-02-25 10:40:14

Re: [SOLVED] delete (created ?) block devices

#6 2023-02-25 11:17:18

Re: [SOLVED] delete (created ?) block devices

#7 2023-02-25 11:17:49

Re: [SOLVED] delete (created ?) block devices

#8 2023-02-25 11:42:09

Re: [SOLVED] delete (created ?) block devices

#9 2023-02-25 11:51:27

Re: [SOLVED] delete (created ?) block devices

#10 2023-02-25 12:10:26

Re: [SOLVED] delete (created ?) block devices

#11 2023-02-25 12:17:36

Re: [SOLVED] delete (created ?) block devices

#12 2023-02-25 12:24:32

Re: [SOLVED] delete (created ?) block devices

#13 2023-02-25 12:26:26

Re: [SOLVED] delete (created ?) block devices

#14 2023-02-25 12:47:26

Re: [SOLVED] delete (created ?) block devices

#15 2023-02-25 12:50:00

Re: [SOLVED] delete (created ?) block devices

#16 2023-02-25 12:54:02

Re: [SOLVED] delete (created ?) block devices

#17 2023-02-25 13:29:26

Re: [SOLVED] delete (created ?) block devices

#18 2023-02-25 13:41:20

Re: [SOLVED] delete (created ?) block devices

Board footer