After KDE install, My server wont BOOT

asylum
Posts: 23
Joined: Mon Mar 28, 2011 2:37 pm

Re: After KDE install, My server wont BOOT

Postby asylum » Sat Nov 24, 2012 9:00 am

Okay,. well I'm completely lost. I'm trying to follow the examples in the links provided, but I'm not getting it. My Dashboard-Shares-Storage Pool shows, in order from top to bottom:

Pooled Location Total Space Free Space
Not Checked / (Red Triangle & Plus Sign) 108.1 GB 104.1 GB

Checked/var/hda/files/drives/drive5

asylum
Posts: 23
Joined: Mon Mar 28, 2011 2:37 pm

Re: After KDE install, My server wont BOOT

Postby asylum » Sat Nov 24, 2012 9:19 am

Ok. Well still not sure. Trying to follow the directions but not sure which direction to go.

Dashboard-Shares-Storage Pool shows the drives:

Pooled, Location, Total, Used,


Not Checked, /, 108.1, 104.1,
(This is the OS Drive: 120 GB) with a Red Triangle and Blue Plus

Checked, /var/hda/files/drives/drive5, 916.9, 721.2,

Checked, /var/hda/files/drives/drive3, Orange Circle with !,

Checked, /var/hda/files/drives/drive4, Orange Circle with !,

I don't have 3 1-TB drives ?

My "fstab" file:

# /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>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda1 during installation
UUID=0ef3931d-c413-4e1c-9359-c11f4bfd3fc2 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=10b4dcd6-455b-444a-b979-b3007f94f123 none swap sw 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0

The "gstreet@gstreet-MicroServer:~$ sudo blkid" file.

brian@brian-desktop:~$ gstreet@gstreet-MicroServer:~$ sudo blkid
gstreet@gstreet-MicroServer:~$: command not found
brian@brian-desktop:~$ ls -l /dev/disk/by-id/
total 0
lrwxrwxrwx 1 root root 9 Nov 24 04:02 ata-Memorex_DVD+-RAM_530L_v1 -> ../../sr0
lrwxrwxrwx 1 root root 9 Nov 24 04:02 ata-WDC_WD1200JB-00GVA0_WD-WCALA1003600 -> ../../sda
lrwxrwxrwx 1 root root 10 Nov 24 04:02 ata-WDC_WD1200JB-00GVA0_WD-WCALA1003600-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Nov 24 04:02 ata-WDC_WD1200JB-00GVA0_WD-WCALA1003600-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Nov 24 04:02 ata-WDC_WD1200JB-00GVA0_WD-WCALA1003600-part5 -> ../../sda5
lrwxrwxrwx 1 root root 9 Nov 24 04:02 ata-WL1000GSA1672_WOL240046078 -> ../../sdc
lrwxrwxrwx 1 root root 10 Nov 24 04:02 ata-WL1000GSA1672_WOL240046078-part1 -> ../../sdc1
lrwxrwxrwx 1 root root 9 Nov 24 04:02 ata-WL1000GSA1672_WOL240046164 -> ../../sdb
lrwxrwxrwx 1 root root 10 Nov 24 04:02 ata-WL1000GSA1672_WOL240046164-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 9 Nov 24 04:02 scsi-SATA_WDC_WD1200JB-00WD-WCALA1003600 -> ../../sda
lrwxrwxrwx 1 root root 10 Nov 24 04:02 scsi-SATA_WDC_WD1200JB-00WD-WCALA1003600-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Nov 24 04:02 scsi-SATA_WDC_WD1200JB-00WD-WCALA1003600-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Nov 24 04:02 scsi-SATA_WDC_WD1200JB-00WD-WCALA1003600-part5 -> ../../sda5
lrwxrwxrwx 1 root root 9 Nov 24 04:02 scsi-SATA_WL1000GSA1672_WOL240046078 -> ../../sdc
lrwxrwxrwx 1 root root 10 Nov 24 04:02 scsi-SATA_WL1000GSA1672_WOL240046078-part1 -> ../../sdc1
lrwxrwxrwx 1 root root 9 Nov 24 04:02 scsi-SATA_WL1000GSA1672_WOL240046164 -> ../../sdb
lrwxrwxrwx 1 root root 10 Nov 24 04:02 scsi-SATA_WL1000GSA1672_WOL240046164-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 9 Nov 24 04:02 wwn-0x50014ee000a26a0e -> ../../sdb
lrwxrwxrwx 1 root root 10 Nov 24 04:02 wwn-0x50014ee000a26a0e-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 9 Nov 24 04:02 wwn-0x50014ee0ab4d163f -> ../../sdc
lrwxrwxrwx 1 root root 10 Nov 24 04:02 wwn-0x50014ee0ab4d163f-part1 -> ../../sdc1

Disk Mount command

brian@brian-desktop:~$ hda-diskmount
You should run this program as root or using sudo
brian@brian-desktop:~$ sudo hda-diskmount
****************************************************************
Ignoring /dev/sda1 - already mounted
Ignoring /dev/sda1 - already in /etc/fstab as /dev/sda1
Ignoring /dev/sda1 - already in /etc/fstab as UUID=0ef3931d-c413-4e1c-9359-c11f4bfd3fc2
This device appears to be commented out of your /etc/fstab. You will need to remove it from there for hda-diskmount to be able to mount it.
****************************************************************
Ignoring /dev/sdc1 - already mounted
****************************************************************
No usable Linux, Windows or Mac partitions found on your disks.

User avatar
bigfoot65
Project Manager
Posts: 11924
Joined: Mon May 25, 2009 4:31 pm

Re: After KDE install, My server wont BOOT

Postby bigfoot65 » Sat Nov 24, 2012 2:22 pm

Looking at your /etc/fstab it appears none of the drives are mounted. Suggest you uncheck all drives from the storage pool and start over with hda-diskmount. Reboot so it's fresh and then run the script. If there are 3 drives, it should reflect in the script output.

Ensure you follow the instructions in the wiki for adding drives. It is important you add them to /etc/fstab or on reboot they will disappear.
ßîgƒσστ65
Applications Manager

My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2

Who is online

Users browsing this forum: Bing [Bot] and 63 guests