On 9/19/18 9:27 AM, Rick Stevens wrote:
On 9/19/18 5:31 AM, Kevin Wilson wrote:
> Hello,
> I have a USB stick on which I had in the past an Ubunutu installatilon.
> When I run "e2label /dev/sdb" I get:
>
> e2label /dev/sdb
> e2label: Bad magic number in super-block while trying to open /dev/sdb
> /dev/sdb contains a iso9660 file system labelled 'Ubuntu-Server 17.04
amd64'
>
> Now, I did not need this installation anymore, so I created a single
> Linux partition on the USB stick (/dev/sdb1)
> with fdisk, and labeled it as sandiskUSB.
> When I run:
> e2label /dev/sdb1
> I get
> sandiskUSB
>
> Is there a way to change also the lablel of /dev/sdb to be sandiskUSB ?
>
> Tying
> e2label /dev/sdb sandiskUSB
> does not work, it gives:
> e2label: Bad magic number in super-block while trying to open /dev/sdb
> /dev/sdb contains a iso9660 file system labelled 'Ubuntu-Server 17.04
amd64'
You can only use e2label on ext2/3/4 filesystems, not on entire block
devices. Had you formatted /dev/sdb ENTIRELY as an ext2/3/4 filesystem,
you could label it. This is born out by you creating a filesystem
partition via fdisk and being able to label that partition.
I should also say that, since the subject is "...label of an iso9660
file system", the label for an ISO9660 filesystem is actually a volume
label, set during image creation via the "-V <text>" option of the
xorrisofs command.
Again, "e2label" inserts a label into the partition table and superblock
for ext2|3|4 filesystems, not on the host block device that holds them.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com -
- AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 -
- -
- Always remember you're unique, just like everyone else. -
----------------------------------------------------------------------