Posts by racelife

    What do you mean with this? maybe gdisk is not installed by default but the tool is still available


    apt install gdisk

    That article uses gdisk and boot-repair. When I try to install boot-repair it says unable to locate package, so I didn't continue on that page. I just went through it and did everything until it got to the boot-repair part. I keep getting Superblock invalid errors and have tried to backup from other superblocks but I haven't found any that work yet. I saw somewhere to try mke2fs -S but I'm not sure how to use that and it said it was a last ditch effort...

    Try and login via ssh. Does the partition now shows with blkid?

    # blkid

    /dev/sr0: UUID="2020-03-25-16-03-59-00" LABEL="openmediavault 20200325-17:17" TYPE="iso9660" PTUUID="c39bfd10" PTTYPE="dos"

    /dev/sdb1: LABEL="StorageOne" UUID="57137a30-3629-4d6b-bf9d-adfaf4ab710a" TYPE="ext4" PARTUUID="307a1357-2936-6b4d-bf9d-adfaf4ab710a"

    /dev/sda1: UUID="7461ee1d-77ea-4a5b-8162-1a76baf857c4" TYPE="ext4" PARTUUID="67851593-01"

    /dev/sda5: UUID="2252c085-0179-47bb-b8d5-7a81430d2b2f" TYPE="swap" PARTUUID="67851593-05"

    Looks like the partition rescue mentioned in that article isn't around anymore but I was able to use "testdisk" and got it kinda working... Now it hangs on boot with errors and if I "ctrl D" then it boots. In the web interface it shows as online now but I can't access the folder from another computer says no such directory.

    Now I'm trying to figure out how to fix it so it boots without errors and then how to access it again.


    When I try and mount it I get this error

    or how to fix the errors on boot?


    running :~# journalctl -xb shows these errors



    Jul 04 14:24:21 OMV5.local blkmapd[310]: open pipe file /run/rpc_pipefs/nfs/blocklayout failed: No such file or directory


    Jul 04 14:24:21 OMV5.local systemd-fsck[389]: StorageOne: One or more block group descriptor checksums are invalid. FIXED.

    Jul 04 14:24:21 OMV5.local systemd-fsck[389]: StorageOne: Group descriptor 448 checksum is 0x0000, should be 0x06a7.

    Jul 04 14:24:21 OMV5.local systemd-fsck[389]: StorageOne: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.

    Jul 04 14:24:21 OMV5.local systemd-fsck[389]: (i.e., without -a or -p options)

    Jul 04 14:24:21 OMV5.local systemd-fsck[389]: fsck failed with exit status 4.



    -- The unit systemd-fsck@dev-disk-by\x2dlabel-StorageOne.service has entered the 'failed' state with result 'exit-code'.

    Jul 04 14:24:21 OMV5.local systemd[1]: Failed to start File System Check on /dev/disk/by-label/StorageOne.

    -- Subject: A start job for unit systemd-fsck@dev-disk-by\x2dlabel-StorageOne.service has failed

    -- Defined-By: systemd

    -- Support: https://www.debian.org/support


    -- A start job for unit systemd-fsck@dev-disk-by\x2dlabel-StorageOne.service has finished with a failure.


    -- The job identifier is 350.

    Jul 04 14:26:30 OMV5.local cron[881]: (CRON) INFO (pidfile fd = 3)

    Jul 04 14:26:30 OMV5.local chronyd[890]: chronyd version 3.4 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +AS

    Jul 04 14:26:30 OMV5.local systemd-fsck[837]: StorageOne: One or more block group descriptor checksums are invalid. FIXED.

    Jul 04 14:26:30 OMV5.local systemd-fsck[837]: StorageOne: Group descriptor 448 checksum is 0x0000, should be 0x06a7.

    Jul 04 14:26:30 OMV5.local systemd-fsck[837]: StorageOne: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.

    Jul 04 14:26:30 OMV5.local systemd-fsck[837]: (i.e., without -a or -p options)

    Jul 04 14:26:30 OMV5.local systemd-fsck[837]: fsck failed with exit status 4.

    Jul 04 14:26:30 OMV5.local systemd-fsck[837]: Running request emergency.target/start/replace

    Jul 04 14:26:30 OMV5.local chronyd[890]: Frequency 6.187 +/- 0.090 ppm read from /var/lib/chrony/chrony.drift

    Jul 04 14:26:30 OMV5.local chronyd[890]: Loaded seccomp filter

    The 5tb disk is there. But the partition is missing and there is no fs signature. Do you have a backup ?

    Not sure how the partition could have dissapeared... maybe power blip? I don't have a backup because I was moving things there off of the machine that was going to be my backup... :(

    # lsblk

    NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT

    sda 8:0 0 10G 0 disk

    ├─sda1 8:1 0 6.1G 0 part /

    ├─sda2 8:2 0 1K 0 part

    └─sda5 8:5 0 3.9G 0 part [SWAP]

    sdb 8:16 0 4.9T 0 disk

    sr0 11:0 1 559M 0 rom



    # blkid

    /dev/sr0: UUID="2020-03-25-16-03-59-00" LABEL="openmediavault 20200325-17:17" TYPE="iso9660" PTUUID="c39bfd10" PTTYPE="dos"

    /dev/sda1: UUID="7461ee1d-77ea-4a5b-8162-1a76baf857c4" TYPE="ext4" PARTUUID="67851593-01"

    /dev/sda5: UUID="2252c085-0179-47bb-b8d5-7a81430d2b2f" TYPE="swap" PARTUUID="67851593-05"


    Looks like it doesn't show in the blkid...?

    I set up a OMV5 vm and Things went great a few days ago. today I was having trouble logging in to a share from my ubuntu. I think I forgot my password so I changed it in the omv web gui and still couldn't log in, so I ssh'd in and cleared out the failed attempts through omv-firstaid but that still didn't work. after looking around in the gui I noticed my storage disk is showing as "missing" not sure where to go from here... It is a virtual disk so it's not like it got unplugged afaik

    # fdisk -l | grep "Disk " | grep sd | sort

    Disk /dev/sda: 10 GiB, 10737418240 bytes, 20971520 sectors

    Disk /dev/sdb: 4.9 TiB, 5368709120000 bytes, 10485760000 sectors


    # cat /etc/fstab

    # /etc/fstab: static file system information.

    #

    # Use 'blkid' to print the universally unique identifier for a

    # device; this may be used with UUID= as a more robust way to name devices

    # that works even if disks are added and removed. See fstab(5).

    #

    # <file system> <mount point> <type> <options> <dump> <pass>

    # / was on /dev/sda1 during installation

    UUID=7461ee1d-77ea-4a5b-8162-1a76baf857c4 / ext4 errors=remount-ro 0 1

    # swap was on /dev/sda5 during installation

    UUID=2252c085-0179-47bb-b8d5-7a81430d2b2f none swap sw 0 0

    /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0

    # >>> [openmediavault]

    /dev/disk/by-label/StorageOne /srv/dev-disk-by-label-StorageOne ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2

    # <<< [openmediavault]

    I'm gonna start referring to this as an impatience error, rather than a boot/install error.

    I didn't have any other disks attached. I did a lot of trouble shooting for 6 or so hours. Trying multiple install usb drives, multiple other operating systems, clearing and resetting bios etc. before I even asked in here. I apologize if that was being too impatient.

    You can try to install and boot first time without data disks. If that works run update-grub. Then shutdown, connect the data disks and boot again.

    I only had the ssd that I was installing to connected. no data disks. I wanted to get it working before adding data disks.

    I used Balena etcher to make the install usb, installing onto a kingston m.2 sata ssd 16Gig. The computer is a HP t620 plus thin client with an AMD quad core processor. 4Gig Ram

    I am trying to install 5.3.9 via the amd64 iso but after the installation when it reboots is says no boot disk or drive has failed (or something close to that) I have had OMV4 running on the same hardware in the past and I can install Lubuntu before and after and it works just fine. I also tried 5.3.4 and have the same error

    Any Ideas?