Beiträge von green

Ok i somehow managed to get it showing up agn in the filesystem list i mounted it and its there agn.

guess the trick was mount -t /dev/mapper/name

Ive got a problem with my file disk not being able to get mounted.

i had todo da clean install since upgrading bricked the system.

ive deatached the file disk and did the install , shutdown the system reattached it like in the Guide.

but now i cant mount it, under the webinterface i see it in Physical Disk /dev/sdb

but in filesystems i see only /dev/sda

the onyl thing i can click there is create if i do that and look on the
devices i see the HDD, but he wants to format what i ofc dont want so i
cancelled it

Tryd the suggested stuff here in this thread nothing worked.

omv-mkconf fstab - reboot - does not fix it

mount -a - does not fix it

blkid

/dev/sda1: UUID="f74f8db3-e7a4-4f1e-96c9-d46382dd84d6" TYPE="ext4"

/dev/sda5: UUID="a992585e-22eb-41c0-b095-88bbe36f57b5" TYPE="swap"

/dev/sdb1: UUID="6J2l3M-QKk5-xK3A-47Xe-Sl1d-oVcS-B04e4q" TYPE="LVM2_member" <------ that i want to mount

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=f74f8db3-e7a4-4f1e-96c9-d46382dd84d6 / ext4 errors=remount-ro 0 1

# swap was on /dev/sda5 during installation

UUID=a992585e-22eb-41c0-b095-88bbe36f57b5 none swap sw 0 0

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

tmpfs /tmp tmpfs defaults 0 0

# >>> [openmediavault]

# <<< [openmediavault]

media

/media# ls -al

insgesamt 12

drwxr-xr-x 3 root root 4096 Sep 10 19:18 .

drwxr-xr-x 24 root root 4096 Nov 1 01:44 ..

lrwxrwxrwx 1 root root 6 Nov 1 00:31 cdrom -> cdrom0

drwxr-xr-x 2 root root 4096 Nov 1 00:31 cdrom0

/dev/mapper# ls -al

insgesamt 0

drwxr-xr-x 2 root root 80 Nov 1 02:00 .

drwxr-xr-x 15 root root 3160 Nov 1 02:00 ..

crw------T 1 root root 10, 236 Nov 1 02:00 control

lrwxrwxrwx 1 root root 7 Nov 1 02:00 space1-space1 -> ../dm-0 <- space1-space1 is that HDD

Version 1.0.29

Ive got the feeling the bricked upgrade from 0.5x to 1.0x has killed the filesystem of that drive any chance to check that and fix it ?

Hi the OS drive is /dev/sda mount i want the /dev/sdb
this error happend after doing the omv-mkconf fstab and reboot
this is a clean install of 1.0

when i reboot agn its working but still the sdb is not mountable

so i redid the command omv-mkconf fstab and reboot
this time it boot up but still the drive is not under Storage - filesystems i can only choose it when i click on create
ive got the feeling the filesystem is broken on that drive...

i mean it does nothing that it still not working and ofc i did a reboot

so i redid the command and rebooted now i get a kernel panic on boot

http://www.suckmypic.net/5qNwaegA.png

ive got the feeling the upgrade killed something on that disk

Ive got alos problem with my file disk not being able to get mounted.

i had todo da clean install since upgrading bricked the system.

ive deatached the file disk and did the install , shutdown the system reattached it like in the Guide.
but now i cant mount it, under the webinterface i see it in Physical Disk /dev/sdb
but in filesystems i see only /dev/sda
the onyl thing i can click there is create if i do that and look on the devices i see the HDD, but he wants to format what i ofc dont want so i cancelled it

Tryd the suggested stuff here in this thread nothing worked.

omv-mkconf fstab - does nothing
mount -a -does nothing

blkid
/dev/sda1: UUID="f74f8db3-e7a4-4f1e-96c9-d46382dd84d6" TYPE="ext4"
/dev/sda5: UUID="a992585e-22eb-41c0-b095-88bbe36f57b5" TYPE="swap"
/dev/sdb1: UUID="6J2l3M-QKk5-xK3A-47Xe-Sl1d-oVcS-B04e4q" TYPE="LVM2_member" <------ that i want to mount

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=f74f8db3-e7a4-4f1e-96c9-d46382dd84d6 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=a992585e-22eb-41c0-b095-88bbe36f57b5 none swap sw 0 0
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
tmpfs /tmp tmpfs defaults 0 0
# >>> [openmediavault]
# <<< [openmediavault]

media
/media# ls -al
insgesamt 12
drwxr-xr-x 3 root root 4096 Sep 10 19:18 .
drwxr-xr-x 24 root root 4096 Nov 1 01:44 ..
lrwxrwxrwx 1 root root 6 Nov 1 00:31 cdrom -> cdrom0
drwxr-xr-x 2 root root 4096 Nov 1 00:31 cdrom0

/dev/mapper# ls -al
insgesamt 0
drwxr-xr-x 2 root root 80 Nov 1 02:00 .
drwxr-xr-x 15 root root 3160 Nov 1 02:00 ..
crw------T 1 root root 10, 236 Nov 1 02:00 control
lrwxrwxrwx 1 root root 7 Nov 1 02:00 space1-space1 -> ../dm-0 <- space1-space1 is that HDD

Version 1.0.29