Hi Cindy, This image was build by myself, fetched on 24th Jan. It is working normally in my VM enviroment but failed on the bear metal server. My server is Huawei RH2288v3: E5-2630 v3@2.4GHz, 2*8cores, 16*8G DDR4 RAM, 2*900G SAS+2*240G SATA HD. Thanks Tim Xiong From: Xie, Cindy Date: 2019-02-02 13:00 To: xiongzhiwei@baicells.com; starlingx-discuss Subject: RE: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server HI, Tim, Can you please provide the following info: - Exact version of the StarlingX: if you downloaded it from Cengen, please provide the link; if you built it by yourself, please provide the date on master. - Your HW config for your bare metal server. Our recommended HW config can be found here: https://docs.starlingx.io/installation_guide/index.html Thanks. - cindy From: xiongzhiwei@baicells.com [mailto:xiongzhiwei@baicells.com] Sent: Saturday, February 2, 2019 12:38 PM To: starlingx-discuss <starlingx-discuss@lists.starlingx.io> Subject: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server Hi, I am trying to deploy starlingx on a bearmetal server, but failed, After execute "sudo config_controller" and some default configuration confirmed(all-in-one, simplex), exception printed as below: 01/08: Creating bootstrap configuration ... DONE 02/08: Applying bootstrap manifest ... [ 452.567312] EXT4-fs error (device drbd1): ext4_journal_check_start:56: Detected aborted journal [ 452.576753] EXT4-fs (drbd1): Remounting filesystem read-only [ 466.880792] EXT4-fs error (device drbd3): ext4_journal_check_start:56: Detected aborted journal [ 466.886032] EXT4-fs (drbd3): Remounting filesystem read-only [ 479.755269] EXT4-fs error (device drbd0): ext4_journal_check_start:56: Detected aborted journal [ 479.760818] EXT4-fs (drbd0): Remounting filesystem read-only [ 479.766425] EXT4-fs (drbd0): ext4_writepages: jbd2_start: 13312 pages, ino 28; err -30 Failed to execute bootstrap manifest Configuration failed: failed to apply bootstrap manifest. See /var/log/puppet/latest/puppet.log for details. I had deployed successfully on a qemu VM with same image, also all-in-one and simplex. Is there any configurations missed for the bear metal server? I had recovered all BIOS configurations to default for it. Could anyone help me to fix it? Thanks BR Tim Xiong