Monthly Archives: November 2017

Disk sdd contains bios raid metadata

While trying to install OS on one of the servers, Was getting error

“Disk sdd contains bios raid metadata”

The issue was the drive present has RAID data as earlier it was used to create RAID in some other server.

So process was to delete all RAID data in it and get ready for the new OS install

[root@localhost ~]# dmraid -r
/dev/sdb: ddf1, “.ddf1_disks”, GROUP, ok, 1951170560 sectors, data@ 0

[root@localhost ~]# mdadm –zero-superblock /dev/sdb
mdadm: Couldn’t open /dev/sdb for write – not zeroing

[root@localhost ~]# dmraid -r
/dev/sdb: ddf1, “.ddf1_disks”, GROUP, ok, 1951170560 sectors, data@ 0

[root@localhost ~]# dd if=/dev/zero of=/dev/sdb bs=512 seek=1951170560
dd: writing `/dev/sdb’: No space left on device
2354609+0 records in
2354608+0 records out
1205559296 bytes (1.2 GB) copied, 16.0356 s, 75.2 MB/s

[root@localhost ~]# dmraid -r
no raid disks

Reboot Server

Once online can format the drive using mkfs

[root@localhost ~]# mkfs.ext4 /dev/sdb
mke2fs 1.41.12 (17-May-2010)
/dev/sdb is entire device, not just one partition!
Proceed anyway? (y,n) y
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
61054976 inodes, 244190646 blocks
12209532 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4294967296
7453 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848

Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 31 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.

Now I am able to install OS on it without any problem on it 🙂

 

Secure Connection Failed while accessing IPMI

Secure Connection Failed

An error occurred during a connection to 216.1x.1xx.xxx. You have received an invalid certificate. Please contact the server administrator or email correspondent and give them the following information: Your certificate contains the same serial number as another certificate issued by the certificate authority. Please get a new certificate containing a unique serial number. Error code: SEC_ERROR_REUSED_ISSUER_AND_SERIAL

The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Please contact the website owners to inform them of this problem.

 

 

Firefox stores certificates separately from the Operating System. Sometimes the certificate store can become corrupt and won’t let you delete certificates. To solve this, you’ll have to reset it manually.

Go to Start > Run

Type %appdata% and click Ok.
Result: A folder should open up.

 

Now go to Mozilla, then Firefox, then Profiles, and choose your profile folder (it probably is named a random string of letters, often followed by .default).

 

Delete the file called “cert8.db”.

This should fix the issue .