dd: error writing '/dev/sdc2': No space left on device - Page 4
FedoraForum.org - Fedora Support Forums and Community
Page 4 of 6 FirstFirst ... 2 3 4 5 6 LastLast
Results 46 to 60 of 82
  1. #46
    Join Date
    Aug 2007
    Posts
    354
    Linux (Fedora) Firefox 61.0

    Re: dd: error writing '/dev/sdc2': No space left on device

    [liveuser@localhost by-id]$ sudo dmraid -ay
    ERROR: device-mapper target type "raid45" is not in the kernel
    RAID set "isw_bihcjjbacf_Backup" was not activated
    ERROR: device "isw_bihcjjbacf_Backup" could not be found
    I did a quick search and this error message popped up in dozens of posts from 2007 to 2017. There appears to be no easy fix. dmraid support is poor and often out of date as dmraid is considered dead and replaced by mdadm. The kernel and modules in Centos 7 apparently doesn't match what was used to create the array.

    RAID set "isw_djbaagagjd_Volume1" was activated
    device "isw_djbaagagjd_Volume1" is now registered with dmeventd for monitoring
    This is good progress. This appears to be the RAID0 array for the OS. Unfortunately you executed the commands in the wrong order. You need to run ls -l /dev/mapper after running dmraid -ay to see what is created. There should be a /dev/mapper/isw_djbaagagjd_Volume1.

    If this array /dev/mapper/isw_djbaagagjd_Volume1 exists try mounting it. By being able to view and edit the OS partition means that you could fix the boot loader problem by chrooting into this RAID0 from Centos7 live. Your system knows how to assemble the RAID5 as it was running for years. By fixing the bootloader your system will boot up and assemble the RAID5 itself.

    You will also be able to backup your OS and CRM software to the external drive. If fixing the bootloader is not a simple task I recommend abandoning the RAID0 and re-formatting the SSDs as single drives. One drive would have the ESP and a 1 GiB ext4 /boot partition. You could then go one of two ways.

    1) Use regular partitions for / /usr /var and /opt and spread them between the two SSDs. Edit fstab so that everything is mounted correctly.

    2) Use LVM to merge the two SSDs so that a large / root filesystem can be spread between them. The first SSD would have the ESP and the 1 GiB ext4 /boot partition and a large LVM physical volume. The second SSD would just have a large PV. The two PVs would be placed in a Volume Group. A very large / root logical volume up to 950 GiB could be created. This all could be done in about 6-8 LVM commands. You would then simply copy all of the backup data from the external drive to this LV. You would need to modify the existing fstab so that it mounts / from this new LV. The one tricky part would be generating a new initramfs with dracut that loads lvm modules and mounts the new root lv from Centos7 live.

    To get this to boot from EFI you would have to change the EFI boot variable so that it points to grub2 on the new ESP.

    I see your note here mount --label _____ /mnt/____
    I tried to mount
    [liveuser@localhost by-id]$ sudo mount --label ata-ST2000DM006-2DM164_Z4ZC735M /mnt/RAID5_A
    mount: can't find LABEL="ata-ST2000DM006-2DM164_Z4ZC735M"
    This isn't a label at all. It is a symlink to a device node. In this case it is the whole drive sdc.

    lrwxrwxrwx. 1 root root 9 Feb 9 18:42 ata-ST2000DM006-2DM164_Z4ZC735M -> ../../sdc

    In any event you couldn't mount this drive anyway as it is only one of the three in your RAID5.
    Last edited by amiga; 12th February 2019 at 11:14 AM.

  2. #47
    Join Date
    Dec 2018
    Location
    Port CoQuitlam, BC
    Posts
    78
    Linux (Fedora) Firefox 65.0

    Re: dd: error writing '/dev/sdc2': No space left on device

    Amiga, thank you for not leaving me hanging. I am in deep waters. I am pretty scared to be honest bro. I like where this is going though. So many people have told me to quit.

    here is the output of;

    [orcacomputers@orcainbox ~]$ dmraid -ay
    ERROR: mkdir /var/lock/dmraid


    [orcacomputers@orcainbox ~]$ cat /proc/mdstat
    Personalities :
    unused devices: <none>
    [orcacomputers@orcainbox ~]$

    So there is no raid as per this usb os, which we can modify as you say (very c00|).
    What do you suggest next ERROR: mkdir /var/lock/dmraid is the bottleneck.

    also, are you certain we need to rebuild the raid? Haydenh mentioned we just need to move the file system, I am wondering if that is an easier approach. However, keep helping me please and I will proceed step by step inch by inch.

    Good raid kernal article

    Namaste
    Last edited by themepenguin; 12th February 2019 at 08:54 PM.

  3. #48
    Join Date
    Aug 2007
    Posts
    354
    Linux (Fedora) Firefox 61.0

    Re: dd: error writing '/dev/sdc2': No space left on device

    [orcacomputers@orcainbox ~]$ dmraid -ay
    ERROR: mkdir /var/lock/dmraid
    You already solved this problem in a previous message ! You need to run this as sudo as you already did in your post 43 ! Please re-read your own previous posts.

    This is from your own post #43 on Feb 10, two days ago. Please re-read it yourself.

    [liveuser@localhost by-id]$ sudo dmraid -ay
    ERROR: device-mapper target type "raid45" is not in the kernel
    RAID set "isw_bihcjjbacf_Backup" was not activated
    ERROR: device "isw_bihcjjbacf_Backup" could not be found
    RAID set "isw_djbaagagjd_Volume1" was activated
    device "isw_djbaagagjd_Volume1" is now registered with dmeventd for monitoring
    So there is no raid as per this usb os, which we can modify as you say (very c00|).
    The RAID0 for your OS was found and activated !

    What do you suggest next ERROR: mkdir /var/lock/dmraid is the bottleneck.
    It wasn't a bottleneck for you two days ago when you used sudo.

    [orcacomputers@orcainbox ~]$ cat /proc/mdstat
    Personalities :
    unused devices: <none>
    Why are you doing this ? This is not relevant to your system. If your system was set up with dmraid then there will be no md arrays. I didn't ask you to run this command. I did ask you to run ls -l /dev/mapper.

    Please post the output of:

    Code:
    $ sudo dmraid -ay
    $ ls -l /dev/mapper/isw*
    If this exists try mounting it. Please post the output of:

    Code:
    $ sudo mkdir /mnt/os
    $ sudo mount /dev/mapper/isw_djbaagagjd_Volume1 /mnt/os
    $ df -hT
    $ ls  /mnt/os

  4. #49
    Join Date
    Dec 2018
    Location
    Port CoQuitlam, BC
    Posts
    78
    Linux Firefox 52.0

    Re: dd: error writing '/dev/sdc2': No space left on device

    10-4
    I hear you loud and clear.

    Says Volume1, missing codepage or helper program
    mount failed.

    [liveuser@localhost ~]$ sudo dmraid -ay
    ERROR: device-mapper target type "raid45" is not in the kernel
    RAID set "isw_bihcjjbacf_Backup" was not activated
    ERROR: device "isw_bihcjjbacf_Backup" could not be found
    RAID set "isw_djbaagagjd_Volume1" already active
    device "isw_djbaagagjd_Volume1" is now registered with dmeventd for monitoring
    [liveuser@localhost ~]$ ls -l /dev/mapper/isw*
    brw-rw----. 1 root disk 253, 3 Feb 12 23:51 /dev/mapper/isw_djbaagagjd_Volume1
    [liveuser@localhost ~]$ sudo mkdir /mnt/os
    [liveuser@localhost ~]$ sudo mount /dev/mapper/isw_djbaagagjd_Volume1 /mnt/os
    mount: /dev/mapper/isw_djbaagagjd_Volume1 is write-protected, mounting read-only
    mount: wrong fs type, bad option, bad superblock on /dev/mapper/isw_djbaagagjd_Volume1,
    missing codepage or helper program, or other error

    In some cases useful info is found in syslog - try
    dmesg | tail or so.
    [liveuser@localhost ~]$ df -hT
    Filesystem Type Size Used Avail Use% Mounted on
    /dev/mapper/live-rw ext4 7.8G 4.1G 3.6G 54% /
    devtmpfs devtmpfs 32G 0 32G 0% /dev
    tmpfs tmpfs 32G 16M 32G 1% /dev/shm
    tmpfs tmpfs 32G 19M 32G 1% /run
    tmpfs tmpfs 32G 0 32G 0% /sys/fs/cgroup
    /dev/sdf1 iso9660 1.3G 1.3G 0 100% /run/initramfs/live
    tmpfs tmpfs 32G 24K 32G 1% /tmp
    varcacheyum tmpfs 32G 53M 32G 1% /var/cache/yum
    vartmp tmpfs 32G 0 32G 0% /var/tmp
    tmpfs tmpfs 6.3G 52K 6.3G 1% /run/user/1000
    /dev/sdg2 ext3 7.3T 15G 6.9T 1% /run/media/liveuser/DataCabinet
    [liveuser@localhost ~]$ ls /mnt/os
    [liveuser@localhost ~]$
    Last edited by themepenguin; 13th February 2019 at 01:27 AM.

  5. #50
    Join Date
    Aug 2007
    Posts
    354
    Linux (Fedora) Firefox 61.0

    Re: dd: error writing '/dev/sdc2': No space left on device

    Perhaps it is better to mount by UUID or file system label if it exists. Please run and post the output of

    $ sudo blkid /dev/mapper/isw_djbaagagjd_Volume1

  6. #51
    Join Date
    Dec 2012
    Location
    santa barbara, CA
    Posts
    1,051
    Linux (Fedora) Firefox 65.0

    Re: dd: error writing '/dev/sdc2': No space left on device

    adding my $0.02:
    One thing I have seen before when moving a linux raid is that somehow you need to "recreate it", and it does not overwrite it, it just "finds" it and reassembles it. I seem to remember something like this, and it worked or me.
    "monsters John ... monsters from the ID..."
    "ma vule teva maar gul nol naya"

  7. #52
    Join Date
    Dec 2018
    Location
    Port CoQuitlam, BC
    Posts
    78
    Linux Firefox 52.0

    Arrow Re: dd: error writing '/dev/sdc2': No space left on device

    Quote Originally Posted by amiga
    Perhaps it is better to mount by UUID or file system label if it exists. Please run and post the output of

    $ sudo blkid /dev/mapper/isw_djbaagagjd_Volume1
    [liveuser@localhost ~]$ $ sudo blkid /dev/mapper/isw_djbaagagjd_Volume1
    bash: $: command not found...
    [liveuser@localhost ~]$ $ sudo lsblk /dev/mapper/isw_djbaagagjd_Volume1
    bash: $: command not found...
    [liveuser@localhost ~]$ $ sudo uuid /dev/mapper/isw_djbaagagjd_Volume1
    bash: $: command not found...
    [liveuser@localhost ~]$ sudo lsblk -o name,mountpoint,label,size,uuid,type
    NAME MOUNTPOINT LABEL SIZE UUID TYPE
    sda 447.1G disk
    ├─sda1 500M part
    ├─sda2 446.7G part
    └─isw_djbaagagjd_Volume1
    894.3G dmraid
    sdb 447.1G disk
    ├─sdb1 300M part
    ├─sdb2 100M part
    ├─sdb3 128M part
    ├─sdb4 446.6G part
    └─isw_djbaagagjd_Volume1
    894.3G dmraid
    sdc 1.8T disk
    sdd 1.8T disk
    sde 1.8T disk
    sdf CentOS-7-x86_64-LiveGNOME-1804
    7.2G 2018-05-02-19-13-11-00 disk
    └─sdf1 /run/initr CentOS-7-x86_64-LiveGNOME-1804
    1.3G 2018-05-02-19-13-11-00 part
    sdg 7.3T disk
    ├─sdg1 128M part
    └─sdg2 /run/media DataCabinet 7.3T 17512a3f-d617-4a65-ae98-9ddb31340705 part
    loop0 20K loop
    loop1 4.3M loop
    └─live-osimg-min
    _CentOS-7-x86_64
    8G e187f81a-5e60-48f3-973d-677a39ff39ea dm
    loop2 1.2G loop
    loop3 _CentOS-7-x86_64
    8G e187f81a-5e60-48f3-973d-677a39ff39ea loop
    ├─live-rw / _CentOS-7-x86_64
    8G e187f81a-5e60-48f3-973d-677a39ff39ea dm
    ├─live-base _CentOS-7-x86_64
    8G e187f81a-5e60-48f3-973d-677a39ff39ea dm
    └─live-osimg-min
    _CentOS-7-x86_64
    8G e187f81a-5e60-48f3-973d-677a39ff39ea dm
    loop4 512M loop
    └─live-rw / _CentOS-7-x86_64
    8G e187f81a-5e60-48f3-973d-677a39ff39ea dm

  8. #53
    Join Date
    Aug 2007
    Posts
    354
    Linux (Fedora) Firefox 61.0

    Re: dd: error writing '/dev/sdc2': No space left on device

    adding my $0.02:
    One thing I have seen before when moving a linux raid is that somehow you need to "recreate it", and it does not overwrite it, it just "finds" it and reassembles it. I seem to remember something like this, and it worked or me.
    This is for the newer mdadm Linux RAID. The RAID sets on this MB were created with the older dmraid tools. Assembling the arrays with mdadm was already tried in an earlier post #36. Using dmraid does manage to assemble one of the RAID sets, the RAID0. For the other RAID5 array it complains about a missing kernel module.

    However this could explain what is wrong with the boot loader. The initramfs generated by dracut may be trying to assemble this RAID as an mdadm array which won't work as it is a dmraid array. One of the screenshots posted earlier seems to suggest this.

    https://www.dropbox.com/s/nbdj64ytv9...27053.jpg?dl=0

  9. #54
    Join Date
    Aug 2007
    Posts
    354
    Linux (Fedora) Firefox 61.0

    Re: dd: error writing '/dev/sdc2': No space left on device

    [liveuser@localhost ~]$ $ sudo blkid /dev/mapper/isw_djbaagagjd_Volume1
    bash: $: command not found...
    [liveuser@localhost ~]$ $ sudo lsblk /dev/mapper/isw_djbaagagjd_Volume1
    bash: $: command not found...
    There is something wrong with your live environment as both of these commands should exist. lsblk works later unexplicably so it could be a timing issue. By the way uuid is not a command.

    Please show the output of:

    Code:
    $ which blkid
    $ which lsblk
    $ which sudo

  10. #55
    Join Date
    Dec 2018
    Location
    Port CoQuitlam, BC
    Posts
    78
    Linux Firefox 52.0

    Re: dd: error writing '/dev/sdc2': No space left on device

    [liveuser@localhost ~]$ which blkid
    /usr/sbin/blkid
    [liveuser@localhost ~]$ which lsblk
    /usr/bin/lsblk
    [liveuser@localhost ~]$ which sudo
    /usr/bin/sudo

  11. #56
    Join Date
    Feb 2005
    Location
    London, UK
    Posts
    808
    Linux (Fedora) Chrome 71.0.3578.98

    Re: dd: error writing '/dev/sdc2': No space left on device

    [liveuser@localhost by-id]$ sudo dmraid -ay
    ERROR: device-mapper target type "raid45" is not in the kernel
    RAID set "isw_bihcjjbacf_Backup" was not activated
    Is this a new or old array? RAID45 seems like an odd choice, I can't even find a raid45 kernel option in the kernel.

  12. #57
    Join Date
    Aug 2007
    Posts
    354
    Linux (Fedora) Firefox 61.0

    Re: dd: error writing '/dev/sdc2': No space left on device

    [liveuser@localhost ~]$ which blkid
    /usr/sbin/blkid
    [liveuser@localhost ~]$ which lsblk
    /usr/bin/lsblk
    [liveuser@localhost ~]$ which sudo
    /usr/bin/sudo
    This is very good and expected. I don't know what went wrong before. Please try this again. If it fails repeat it. lsblk didn't work the first time you tried it.

    Code:
    $ sudo blkid /dev/mapper/isw_djbaagagjd_Volume1
    It it still fails try
    Code:
    $ sudo blkid
    This will output everything for all block devices which hopefully will include /dev/mapper.

  13. #58
    Join Date
    Aug 2007
    Posts
    354
    Linux (Fedora) Firefox 61.0

    Re: dd: error writing '/dev/sdc2': No space left on device

    Is this a new or old array? RAID45 seems like an odd choice, I can't even find a raid45 kernel option in the kernel.
    It is a very old array and that is the problem. dmraid is considered obsolete and dead and replaced by mdadm even for fakeRAID arrays. Intel has a paper from 2011 on how to use mdadm with their RST controllers which is what the OP has.

    The RAID45 module no longer appears in newer kernels which is why Centos 7 can't assemble this array. However older versions of Centos 6 could. I came across a blog post from Feb 2009 exactly 10 years ago where someone had to recompile their kernel with a Mandriva patch for the RAID45 module as it didn't exist in their kernel 10 years ago. The blog post explains all of the poor support for dmraid even back then. It explains most of the problems the OP is having in this thread in 2019.

    http://nil-techno.blogspot.com/2009/...-fakeraid.html

    This is from 2008:
    https://bugs.archlinux.org/task/11669

  14. #59
    Join Date
    Dec 2018
    Location
    Port CoQuitlam, BC
    Posts
    78
    Linux Firefox 52.0

    Re: dd: error writing '/dev/sdc2': No space left on device

    [liveuser@localhost ~]$ blkid /dev/mapper/isw_djbaagagjd_Volume1
    [liveuser@localhost ~]$ sudo blkid /dev/mapper/isw_djbaagagjd_Volume1
    /dev/mapper/isw_djbaagagjd_Volume1: PTTYPE="dos"
    [liveuser@localhost ~]$

  15. #60
    Join Date
    Aug 2007
    Posts
    354
    Linux (Fedora) Firefox 61.0

    Re: dd: error writing '/dev/sdc2': No space left on device

    [liveuser@localhost ~]$ sudo blkid /dev/mapper/isw_djbaagagjd_Volume1
    /dev/mapper/isw_djbaagagjd_Volume1: PTTYPE="dos"
    This device appears to just be the container. One or more partitions where the actual file systems are stored are inside. To activate the partitions use kpartx. Please post the output of:

    Code:
    $ sudo kpartx -av /dev/mapper/isw_djbaagagjd_Volume1
    $ sudo blkid /dev/mapper/isw_djbaagagjd_Volume1*
    $ ls -l /dev/mapper/isw*

Page 4 of 6 FirstFirst ... 2 3 4 5 6 LastLast

Similar Threads

  1. No Space Left on Device
    By errigour in forum Hardware & Laptops
    Replies: 1
    Last Post: 21st January 2014, 07:22 PM
  2. Systemctl error no space left on device
    By willc0de4food in forum Using Fedora
    Replies: 6
    Last Post: 9th November 2012, 09:02 PM
  3. No Space Left on Device
    By metatron in forum Hardware & Laptops
    Replies: 16
    Last Post: 30th March 2009, 08:17 PM
  4. Replies: 5
    Last Post: 27th October 2008, 06:46 AM
  5. ERROR "No space left on device" using 2 web cams
    By ReneVanLent in forum Using Fedora
    Replies: 0
    Last Post: 11th August 2005, 04:15 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •