There is only one drive connected (except the USB-Stick) and on this drive there are only three small partitions.
What do you expect to be there?
If you have plugged your HBA and the other drives the HBA is not recognized by the OS.
There is only one drive connected (except the USB-Stick) and on this drive there are only three small partitions.
What do you expect to be there?
If you have plugged your HBA and the other drives the HBA is not recognized by the OS.
Correct,
I realized with the issue I had before I reset the BIOS during all this and it disabled the HBA.
I’ve now turned it back on and now get:
After installing parted and printing the output for my OS drive I get:
Number
1
Start
End
Size
File system Name Flags
1049kB
8002GB 8002GB ext4
user@debian:"% sudo parted /dev/sdi
"print'
Model: ATA WDC WD30EFRX-68E (scsi)
Disk /dev/sdi: 3001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:
Number
1
2
3
Start
End
Size
File system
1049kB
2097kB
1049kB
2097kB
21.0GB
21.0GB
ext4
21.0GB
89.6GB
68.7GB
linux-swap(v1)
Name
Flags
bios grub
Alles anzeigen
So in live Debian and typing ‘sudo sfdisk -l’
I get a list of all the drive I expect (10 drives).
After doing a fsck on each of the drives I get this:
user@debian:"S sudo fsck
-n /dev/sdj2
fsck from util-linux 2.33.1
e2fsck 1.44.5 (15-Dec-2018)
/dev/sdj2: clean, 351942/1286144 files, 3925650/5120000 blocks
user@debian:"S sudo fsck
-n /dev/sdf1
fsck from util-linux 2.33.1
e2fsck 1.44.5. (15-Dec-2018)
pathede6 Len?: 3106243291292, de veSäe1091913024/1953506385 blocks
user@debian:"
-n /dev/sdg1
fsck from util-linux 2.33.1
e2fsck 1.44.5 (15-Dec-2018)
DATA5: clean, 5375/244191232 files, 1091569728/1953506385 blocks
user@debian:"§ sudo fsck
-n /dev/sdh1
fsck from util-linux 2.33.1
e2fsck 1.44.5 (15-Dec-2018)
uaThedeSlean:-362,245051292,fleVeSd14030586057/1952506385 blocks
/dev/sdi1
fsck from util-linux 2.33.1
e2fsck 1.44.5 (15-Dec-2018)
(SINades lean: 3 0500 732191283 a el) fda; 1091798519/1953506305 blocks
fsck from util-linux 2.33.1
e2fsck 1.44.5 (15-Dec-2018)
ustradef enh. g' 36980 45678067 28e v/Sap; 3136538589/3906469627 blocks
-n /dev/sdb1
fsck from util-linux 2.33.1
e2fsck 1.44.5 (15-Dec-2018)
DATA1: clean, 1247196/408308736 files, 3128260063/3906469627 blocks
user@debian:~$ sudo fsck -n /dev/sdc1
fsck from util-linux 2.33.1
e2fsck 1.44.5 (15-Dec-2018)
paTARieflaan-g1585; °49683067 =8e$/568: 3400420589/3906469627 blocks
fsck from util-linux 2.33.1
e2fsck 1.44.5 (15-Dec-2018)
PARITY1: clean, 14/488308736 f1les, 3227829414/3906469627 blocks
user@debian:"$ sudo fsck
-n /dev/sde1
fsck from util-linux 2.33.1
e2fsck 1.44.5 (15-Dec-2018)
PARITY2: clean, 14/488300736 files, 3227829431/3906469627 blocks
Alles anzeigen
now I am unsure what to do..
Any more ideas?
Do you have a kernel on the live disk, which is also on the OMV boot disk? If yes try booting with this one.
Do you have a kernel on the live disk, which is also on the OMV boot disk? If yes try booting with this one.
I have kernel version 4.19.0-17 on the live disk.
How do I check which version the boot disk has?
In the boot menu, you can choos a kernel. Be fast hiting the space key (if i remember corctly), otherwise it will bot the standard kernel.
In the boot menu, you can choos a kernel. Be fast hiting the space key (if i remember corctly), otherwise it will bot the standard kernel.
Do you mean on this screen?
yes
But you do have a 4.19 image on the live disk, your OMV is already an 5.x. Do you still know which was the one you habe bevor switching kernels?
But you do have a 4.19 image on the live disk, your OMV is already an 5.x. Do you still know which was the one you habe bevor switching kernels?
No idea sorry..
If you can not get it to boot with one of the installed kernels, there are two options
If you can not get it to boot with one of the installed kernels, there are two options
- install a working kernel with the live cd or
- re-install OMV on top of a debian netinstall
I guess re-install is the way to go then?
I’m using docker for all my software
Will I lose any of this? What about my MergerFS settings / data?
Did you follow the guide to put the docker directory off the boot drive? If nothing is sored on the os-drive, you are save.
The mergerfs settings (and all other OMV-settings) need to be re-done.
Do you happen to have a backup of a working boot drive?
No I didn’t. I remember a guide I used told me to put it off of the MergerFS pool of which the only drive available was the boot drive..
I do not have a backup of a working boot drive.
It was unfortunately on my list of things to try and figure out (I was planning on moving it to a 500GB SSD)
OK, so you should not install before doing a backup.
Unplug all data drives and have USB-Drive ready
With the live cd (If it is mot comfortable for you, use a graphical UI)
- mount the boot drive
- plug a USB drive
- copy the contents of the mounted boot drive to the USB-Drive
Or get a copy of clonezilla, boot and make a 1:1 copy of your boot drive.
When this is done, we can take care for the rest.
Alles anzeigenOK, so you should not install before doing a backup.
Unplug all data drives and have USB-Drive ready
With the live cd (If it is mot comfortable for you, use a graphical UI)
- mount the boot drive
- plug a USB drive
- copy the contents of the mounted boot drive to the USB-Drive
Or get a copy of clonezilla, boot and make a 1:1 copy of your boot drive.
When this is done, we can take care for the rest.
OK, I am currently booting into Clonezilla Live and will copy the OS drive to another HDD the exact same size.
I will post again when it's all complete
Alright, I have made a clone of the OS HDD and verified the cloned one by having all the same GRUB boot options as the source HDD.
Now what?
As an aside I would actually like to move the OS to a 500GB ssd which I have on hand. If this makes things any different..
OK, before we start, I would like to share my assumptions:
- Initially you installed OMV with an older kernel
- At some time, you installed a new kernel but did not do a reboot
- During the hardware upgrade you had to reboot and use the new kernel (which hangs)
It is strange that your hardware is not apt for the new kernel.
If you like, you can use the new 500 GB SSD as you os-drive and install a fresh copy of OMV and o all updates make sure it still works.
Iy you do not mind to reconfigure OMV, we can start from that install and just copy the docker stuff to the new disk.
Alles anzeigenOK, before we start, I would like to share my assumptions:
- Initially you installed OMV with an older kernel
- At some time, you installed a new kernel but did not do a reboot
- During the hardware upgrade you had to reboot and use the new kernel (which hangs)
It is strange that your hardware is not apt for the new kernel.
If you like, you can use the new 500 GB SSD as you os-drive and install a fresh copy of OMV and o all updates make sure it still works.
Iy you do not mind to reconfigure OMV, we can start from that install and just copy the docker stuff to the new disk.
Yeah, I’m not entirely sure as it has been running for 18 months and continuously online for about 35 days since the last reboot.
Great, I had a feeling you may have asked me to do that which I’ve gone ahead and done.
Latest version downloaded and installed and have checked and installed all the latest updates as well as OMV-extras and SnapRAID and UnionFileSystems which I know I was using before.
I have all my data and parity drives still disconnected
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!