mariadb fails to start Topic is solved

Having issues with your DietPi installation or found a bug? Post it here.
User avatar
Joulinar
Posts: 4783
Joined: Sat Nov 16, 2019 12:49 am

Re: mariadb fails to start

Post by Joulinar »

(sory for replying so late, but had some personal problems)
nothing to be sorry about. Hope you are healthy and ok
Now I must find a way to get a backup of the WordPress database.
Keep your SD card. Once you have setup the new system we could perform some file system check to see if there is a corruption and probably we are able to fix (without guarantee)
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
RollingDutch
Posts: 23
Joined: Thu Mar 18, 2021 9:08 am
Contact:

Re: mariadb fails to start

Post by RollingDutch »

Thanks. Will do so later this week.
RollingDutch
Posts: 23
Joined: Thu Mar 18, 2021 9:08 am
Contact:

Re: mariadb fails to start

Post by RollingDutch »

Took a little more longer, but finally having some time for this again.

I installed a new version of DietPi and WordPress on a fresh SD-card, and save the old one to investigate the old disk. If nothng works, no big problem.
User avatar
Joulinar
Posts: 4783
Joined: Sat Nov 16, 2019 12:49 am

Re: mariadb fails to start

Post by Joulinar »

If possible you can connect your old SD card via USB connector to your device and run a file system check

Code: Select all

fsck -a /dev/sdxx
You would need to replace sdxx with the correct device name. probably sda2
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
RollingDutch
Posts: 23
Joined: Thu Mar 18, 2021 9:08 am
Contact:

Re: mariadb fails to start

Post by RollingDutch »

fsck -a /dev/sda2
fsck from util-linux 2.33.1
fsck.ext2: No such file or directory while trying to open /dev/sda2
Possibly non-existent device?

Same with sda1 to sda4

when I tried to look at the card earlier, I got a 'RAW' error message.
User avatar
Joulinar
Posts: 4783
Joined: Sat Nov 16, 2019 12:49 am

Re: mariadb fails to start

Post by Joulinar »

let's check where the SD card is

Code: Select all

lsblk -o name,fstype,label,size,ro,type,mountpoint,partuuid,uuid
and kernel error messages

Code: Select all

dmesg -l err,crit,alert,emerg
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
RollingDutch
Posts: 23
Joined: Thu Mar 18, 2021 9:08 am
Contact:

Re: mariadb fails to start

Post by RollingDutch »

Then I get the following:

Code: Select all

root@DietPi:~# lsblk -o name,fstype,label,size,ro,type,mountpoint,partuuid,uuid
NAME     FSTYPE LABEL  SIZE RO TYPE MOUNTPOINT PARTUUID                             UUID
sda                   29.5G  0 disk
mmcblk0               29.8G  0 disk
├─mmcblk0p1
│        vfat   boot   256M  0 part /boot      8f4dbd00-01                          4ADC-240F
└─mmcblk0p2
         ext4   rootfs
                      29.6G  0 part /          8f4dbd00-02                          89cef7ba-d45a-47e7-8d42-aff18afcec80

Code: Select all

root@DietPi:~# dmesg -l err,crit,alert,emerg
[    5.100383] vc_sm_cma_vchi_init: failed to open VCHI service (-1)
[    5.100401] [vc_sm_connected_init]: failed to initialize shared memory service
[    5.127675] bcm2835_mmal_vchiq: Failed to open VCHI service connection (status=-1)
[    5.348096] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[    5.642702] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[    5.642788] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
[    5.644028] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Oct 22 2019 01:59:28 version 7.45.98.94 (r723000 CY) FWID 01-3b33decd
[49113.118316] sd 0:0:0:0: [sda] No Caching mode page found
[49113.118338] sd 0:0:0:0: [sda] Assuming drive cache: write through
[49113.147751] blk_update_request: critical medium error, dev sda, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[49113.147767] Buffer I/O error on dev sda, logical block 0, async page read
[49113.149215] blk_update_request: critical medium error, dev sda, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[49113.149229] Buffer I/O error on dev sda, logical block 0, async page read
[49113.293662] blk_update_request: critical medium error, dev sda, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[49113.293690] Buffer I/O error on dev sda, logical block 0, async page read
[49113.310761] blk_update_request: critical medium error, dev sda, sector 61931392 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[49113.312113] blk_update_request: critical medium error, dev sda, sector 61931392 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[49113.312127] Buffer I/O error on dev sda, logical block 7741424, async page read
[50169.487676] blk_update_request: critical medium error, dev sda, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[50169.487690] Buffer I/O error on dev sda, logical block 0, async page read
[50169.489028] blk_update_request: critical medium error, dev sda, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[50169.489045] Buffer I/O error on dev sda, logical block 0, async page read
[50169.494424] blk_update_request: critical medium error, dev sda, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[50169.494444] Buffer I/O error on dev sda, logical block 0, async page read
[50973.712374] sd 0:0:0:0: [sda] No Caching mode page found
[50973.712385] sd 0:0:0:0: [sda] Assuming drive cache: write through
[50973.732974] blk_update_request: critical medium error, dev sda, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[50973.733001] Buffer I/O error on dev sda, logical block 0, async page read
[50973.735051] blk_update_request: critical medium error, dev sda, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[50973.735074] Buffer I/O error on dev sda, logical block 0, async page read
[50973.736978] blk_update_request: critical medium error, dev sda, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[50973.737003] Buffer I/O error on dev sda, logical block 0, async page read
[50973.752188] blk_update_request: critical medium error, dev sda, sector 61931392 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[50973.753692] blk_update_request: critical medium error, dev sda, sector 61931392 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[50973.753706] Buffer I/O error on dev sda, logical block 7741424, async page read
root@DietPi:~#
User avatar
Joulinar
Posts: 4783
Joined: Sat Nov 16, 2019 12:49 am

Re: mariadb fails to start

Post by Joulinar »

looks like quite some damage on the old SD card

Code: Select all

critical medium error, dev sda
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
RollingDutch
Posts: 23
Joined: Thu Mar 18, 2021 9:08 am
Contact:

Re: mariadb fails to start

Post by RollingDutch »

Was afraid of that. Well, no big problem. just starting over again with everything, and maybe I can still import from the old,old source
User avatar
Joulinar
Posts: 4783
Joined: Sat Nov 16, 2019 12:49 am

Re: mariadb fails to start

Post by Joulinar »

as well a good time to remember to create backups on regular basis on another disk/stick ;)
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
Post Reply